Closed Bug 288747 Opened 20 years ago Closed 19 years ago

designMode='on' doesn't work with current SVG binary builds

Categories

(Firefox :: General, defect)

defect
Not set
major

Tracking

()

RESOLVED DUPLICATE of bug 302885

People

(Reporter: pop2.bugzilla, Assigned: tor)

Details

Attachments

(1 file)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050319 Firefox/1.0+ setting document.designMode='on' results in Error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMNSHTMLDocument.designMode]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: javascript:document.designMode='on';void(0); :: <TOP_LEVEL> :: line 1" data: no] Reproducible: Always Steps to Reproduce:
this happens also with the latest nightlies but only when svg.enabled=true
Works for me... Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050601 Firefox/1.0+
I could be doing something wrong, but this doesn't work for me: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050621 I've tried this with and without ./configure --disable-svg ... and then with and without svg.enabled Under no combinations have I witnessed designMode or svg working. I need designMode for work, so I fire up an old build for that... but I have to admit this bug is making me nervous. I'm picturing millions of firefoxes without a working designMode. :\
(In reply to comment #3) > I could be doing something wrong, but this doesn't work for me: I was doing something wrong - I'm not sure exactly what combination of ~/.mozconfig options I had that was spoiling things for me, but I've found a better config, based on the nightly builds. So, now, I have SVG /and/ designMode, and I feel like a giddy little futuristic cyborg that just got a semifirmware updage. Thanks to the Team
This is affecting Linux nightly snapshots (downloaded - 4 Aug 2005).
With Deer Park Alpha 2, no designmode (Rich-Text-Editor) is possible. see: http://www.kevinroth.com/rte/demo.htm even when svg is turned off or on, by using svg.enable (true/false) no effect.
Attached file simple testcase
Here's a test case, a simple HTML file with a designMode-enabled iframe that works fine in Firefox 1.0.x but fails with the following JS console error on today's nightly: Error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMNSHTMLDocument.designMode]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: file:///home/myk/testcase-288747.html :: onload :: line 1" data: no]
I should note that I tested the testcase using a fresh profile. designMode is important functionality, and we shouldn't ship the beta with it broken.
Severity: normal → major
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: blocking1.8b4?
OS: Windows XP → All
Hardware: PC → All
Version: unspecified → Trunk
Possibly related to bug 263392, bug 302885, and bug 256562.
Tor, Can you help us figure out who the right assignee is for this? Mike
Assignee: firefox → tor
Flags: blocking1.8b4? → blocking1.8b4+
just checked with last Firefox build 20050816 (Dear park), and it works fine again. SVG is also still working....
Confirmed. It now works for me again. This is probably a duplicate of bug 302885. Marking as such, but if anyone disagrees, then feel free to reopen and resolve worksforme instead. *** This bug has been marked as a duplicate of 302885 ***
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Flags: blocking1.8b4+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: