254048 - This page can't be edited for an unknown reason.

Status: RESOLVED DUPLICATE of bug 126044

(SeaMonkey :: Composer, defect)

Description

[Ken Rohrer]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a2) Gecko/20040714
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a2) Gecko/20040714

When I open pages in Composer, I get the error, "This page can't be edited for
an unknown reason." I have tried to resave the file using "save as" to no avail.
I have also uninstalled and reinstalled Mozilla.

Reproducible: Always
Steps to Reproduce:
1. Open existing document previously edited with Composer.
2. The error "This page can't be edited for an unknown reason" appears
3. The page can not be edited.



Expected Results:  
Open the file in an edit mode.

Comment 1

[Gérard Talbot]

If you're trying to load an image file for instance, then you'll get such error
message. Composer is an HTML editor; it can not edit other types of file format
(except maybe .txt files).
So the question is what kind of files were/are you trying to edit.
When you "Save" or "Save as..." a document, there is a drop-down list with "Save
as type"; you can not choose any kind of file extension in Composer.

Also, you may be editing a real html file but the format you choose to save the
file is not .html nor .htm. If the file extension is not .html nor .htm, then
Composer won't be able to process the loading of the file. I tested that. I
think Composer could be made more robust, preventing such error from the user.

There is a bugfile on making such error message more explanatory for the user of
the error: see bug 126044

Comment 2

[Gérard Talbot]

Ken, I have not heard any feedback from you about the explanations I submitted.
The message "This page can't be edited for an unknown reason." is there for a
reason. 
Can you please get back into this bugfile if you believe (and why) this bug
should still be active, opened or confirmed? Unless I don't hear from you, I'll
resolve this bug as invalid or I'll resolve this bug as a duplicate of bug 126044.

Comment 3

[Gérard Talbot]

*** This bug has been marked as a duplicate of 126044 ***