Closed
Bug 713002
Opened 12 years ago
Closed 12 years ago
document.open() cause uncaught exception, after reading navigator property
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
DUPLICATE
of bug 707749
People
(Reporter: chado_moz, Unassigned)
Details
(Keywords: regression)
Attachments
(1 file, 1 obsolete file)
784 bytes,
text/html
|
Details |
using javascript: read any property for navigator (e.g. appName, userAgent, or even length), then call document.open(), script stops and Error Console says: Error: uncaught exception: [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIDOMHTMLDocument.open]" nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)" location: "JS frame :: (document location) :: run :: line 14" data: no] steps to reproduce: 0. open Error Console or Web Console. 1. open testcase (test1). 2. click the "broken case" link. script reads navigator.userAgent and tries to do document.open() expected result: content turns into just "Done.", with no error. actual result: script stops and Error Console shows uncaught exception like above. I'm seeing this on Windows7 with Firefox Nightly (12.0a1) and SeaMonkey Nightly (2.9a1). also on Linux (Ubuntu 11.10 on VirtualBox Guest). Firefox Aurora (10.0a2) looks not affected so far. last build works fine: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0a1) Gecko/20111203 Firefox/11.0a1 ID:20111203031109 Built from http://hg.mozilla.org/mozilla-central/rev/9740118b9dcc first build do not work: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0a1) Gecko/20111204 Firefox/11.0a1 ID:20111204031102 Built from http://hg.mozilla.org/mozilla-central/rev/c2102c45c8da so, regressed range may be: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=9740118b9dcc&tochange=c2102c45c8da
Keywords: regression
Updated•12 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Attachment #583833 -
Attachment is obsolete: true
Attachment #583842 -
Attachment mime type: text/plain → text/html
now Firefox Aurora builds are also affected since that's come to version 11.0a2.
You need to log in
before you can comment on or make changes to this bug.
Description
•