Closed Bug 335854 Opened 18 years ago Closed 17 years ago

DesignMode persists between different sites in this particular instance

Categories

(Core :: DOM: Editor, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: martijn.martijn, Unassigned)

References

()

Details

(Keywords: testcase)

To reproduce:
- Visit a bogus address like file:///C:/stuff to get a xul error page (it has to point to a bogus local address)
- Visit http://google.com
- Enable designMode on that page by using: javascript:document.designMode='on'; void 0
- Go back in history
- Visit another site, like http://mozilla.org for instance.

Actual result:
The mozilla.org site is in designMode

Expected result:
The mozilla.org site should not be in designMode

Note that in the 4th step, when going back in history, the xul error page looks funny, eg, it doesn't show any text anymore (only the button has text left).
Btw, this isn't a recent regression (like in the last couple of days).
But I haven't tested in a browser older than a week.
QA Contact: editor
Assignee: mozeditor → nobody
This works now in current trunk build.
I'm pretty sure bug 237964 has fixed this.
Status: NEW → RESOLVED
Closed: 17 years ago
Depends on: contenteditable
Resolution: --- → FIXED
From comment 0:
"
Note that in the 4th step, when going back in history, the xul error page looks funny, eg, it doesn't show any text anymore (only the button has text left).
"
I can still see that, though, I've filed bug 388160 for it.
Flags: in-testsuite?
You need to log in before you can comment on or make changes to this bug.