126044 - "this type of page cant be edited" is vague

Status: RESOLVED EXPIRED

(SeaMonkey :: Composer, defect)

Description

[Henrik Gemal]

go to http://dilbert.gemal.dk/ and do File -> Edit page you get a error saying:
"this type of page cant be edited"

the error is not perfect.

I'd like to see something like this
"This type of page (image/gif) cannot be edited"

most alerts use "cannot" and not "can't"

Comment 1

[Boris Zbarsky [:bzbarsky]]

Composer. 

Comment 2

[Kathleen :Brade]

-->robinf for wording changes
Robin--please assign to [e-mail] for actual changes

Comment 3

[robinf]

Agree with Henrik: "This type of page (image/gif) cannot be edited."

Reassigning to Charley ([e-mail]) for implementation.

Comment 4

[Charles Manske]

We'd have to look at whatever mimetype is and show different error messages for
each. A good idea that will have to wait 'till next release.

Comment 5

[Charles Manske]

This will have to be implemented in new code that will be written as part of 
removing editorShell (bug 121648.) The mimetype detection will be in a new 
location in the code.

Comment 6

[Charles Manske]

This will be easy to fix now.

Comment 7

[Gérard Talbot]

Is this bugfile still active?
If I load an image file in a Mozilla window, then the Edit Page Ctrl+E menuitem
becomes dimmed, disabled, inoperant. So this bug appears to be FIXED.

Mozilla 1.8a3 build 2004082007 under XP Pro SP1a here.

Comment 8

[Gérard Talbot]

*** Bug 254048 has been marked as a duplicate of this bug. ***

Comment 9

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 10

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420