Closed Bug 136968 Opened 22 years ago Closed 14 years ago

Better error dialog saying that editing MathML page is impossible

Categories

(SeaMonkey :: Composer, defect)

defect
Not set
minor

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: david, Unassigned)

References

()

Details

I tried to edit page http://mozilla.org/projects/mathml/demo/basics.xhtml
(MathML example) and the error dialog saying "This type of page can't be edited"
popped-up.

I think the wording in this dialog should be more accurate, the dialog should
say *what* is the type of page it can't edit ("Pages containing mathematical
expessions (MathML) can't be edited" or something similar).
--> Editor:Composer
Assignee: kin → syd
Component: Editor: Core → Editor: Composer
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Target Milestone: --- → Future
Robin--we could probably use your help on this issue.
The problem is that we are told what mimetype the file is (from the server or
OS) but this problem isn't specific to MathML, it's for every type of file that
we don't handle.
Target Milestone: Future → mozilla1.1beta
Suggested text for general error message: "Pages of this type (<insert mimetype
here>) cannot be edited."
reassign to new placeholder
Assignee: syd → composer
Status: ASSIGNED → NEW
Product: Browser → Seamonkey
Assignee: composer → nobody
QA Contact: sujay → composer
Target Milestone: mozilla1.1beta → ---
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
Status: NEW → UNCONFIRMED
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
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.