Closed
Bug 21820
Opened 25 years ago
Closed 25 years ago
[DOGFOOD]'Edit Page' results in non-editable page
Categories
(Core :: DOM: Editor, defect, P3)
Tracking
()
VERIFIED
FIXED
People
(Reporter: sfraser_bugs, Assigned: sfraser_bugs)
References
Details
If you do 'Edit Page', the resulting page in editor has a number of problems:
1. Sometimes, content is duplicated
2. Part of all of the page is not editable.
Assignee | ||
Comment 1•25 years ago
|
||
These problems go away if you turn off the timer-based content notifications with
the pref
user_pref("content.notify.ontimer", false);
Assignee | ||
Comment 2•25 years ago
|
||
cc: vidur
Assignee | ||
Updated•25 years ago
|
Summary: 'Edit Page' results in non-editable page → [DOGFOOD]'Edit Page' results in non-editable page
Assignee | ||
Comment 3•25 years ago
|
||
Adding dogfood, pls consider for PDT+ status
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 4•25 years ago
|
||
Mmm, this problem does not seem to occur when loading the page through a file:
(or chrome:) URL, only http. Even the simplest page with at least one tag in the
body will show the problem.
Assignee | ||
Comment 5•25 years ago
|
||
More info: the content model looks good, so the problem is in content -> frame
construction.
Assignee | ||
Comment 6•25 years ago
|
||
This looks very much like it's caused by bug 21459. What's happening is that the
OnEndDocumentLoad is being called too early, so the editor gets instantiated
before the document is fully reflowed. Because of this, the editor is making the
bogus <BR> node, which confuses the content sink and causes teh doubled content.
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 7•25 years ago
|
||
Good, rick's fix for 21459 fixed this too.
You need to log in
before you can comment on or make changes to this bug.
Description
•