DesignMode persists between different sites in this particular instance

RESOLVED FIXED

Status

()

Core
Editor
RESOLVED FIXED
12 years ago
11 years ago

People

(Reporter: Martijn Wargers (zombie), Unassigned)

Tracking

({testcase})

Trunk
x86
Windows XP
testcase
Points:
---
Bug Flags:
in-testsuite ?

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

12 years ago
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).
(Reporter)

Comment 1

12 years ago
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
(Reporter)

Comment 2

11 years ago
This works now in current trunk build.
I'm pretty sure bug 237964 has fixed this.
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Depends on: 237964
Resolution: --- → FIXED
(Reporter)

Comment 3

11 years ago
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.

Updated

11 years ago
Flags: in-testsuite?
You need to log in before you can comment on or make changes to this bug.