Closed
Bug 215686
Opened 22 years ago
Closed 21 years ago
Can't disable designmode
Categories
(SeaMonkey :: Composer, defect)
SeaMonkey
Composer
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 198155
People
(Reporter: pop2.bugzilla, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030808
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030808
document.designMode='on';
document.designMode='off';
leaves the design mode on.
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Comment 1•22 years ago
|
||
Updated•22 years ago
|
Severity: blocker → major
Confirming bug. Should this be changed to an enhancement (I have no idea if the
original plan was for designMode to be impossible to disable or not)? This
causes major problems at, for example, www.inreview.com.
I think the line of code referenced by bz has moved to
http://lxr.mozilla.org/seamonkey/source/content/html/document/src/nsHTMLDocument.cpp#3924
for the moment.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Hardware: PC → All
Updated•21 years ago
|
Comment 3•21 years ago
|
||
dff/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040626 Firefox/0.9.1, also
recent CVS from Aviary.
This leads to a minor but irritating bug with Blogger's new rich post editing
feature. To make the posting dialog, um, rich, designMode is turned on while
the user is working on their post. After posting, the user is sent to a page
that uses a META refresh to dynamically display the current publishing status.
However, because designMode never gets turned off and nsEditingSession disables
the use of META refresh, the status page needs to be manually reloaded for the
user to see if their post got published. If the user doesn't figure out that
the status page is updated through reloads, it appears that publishing posts
always stalls and they get the impression that the site's broken.
I sent Blogger a suggestion that they use Javascript to reload the page instead,
but it'd be nice if they didn't have to work around Mozilla.
Comment 4•21 years ago
|
||
*** This bug has been marked as a duplicate of 198155 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•