Closed
Bug 264302
Opened 20 years ago
Closed 20 years ago
uncaught exception - Object cannot be created in this context - NS_ERROR_DOM_NOT_SUPPORTED_ERR
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
People
(Reporter: aha, Unassigned)
References
()
Details
Attachments
(1 file, 1 obsolete file)
513 bytes,
application/xhtml+xml
|
Details |
2004101006/trunk/W2K
While visiting this page, this error appears in JS console:
Error: uncaught exception: [Exception... "Object cannot be created in this
context" code: "9" nsresult: "0x80530009 (NS_ERROR_DOM_NOT_SUPPORTED_ERR)"
location: "http://c1.navrcholu.cz/code?site=69287;t=lb14 Line: 34"]
Page is rendered in Standards compliance mode, contains div with inline style
display:none and external javascript is trying to create img element inside it.
Maybe related to bryner's bug 60212, because bug 194648 with similar error was
duped against it.
Reporter | ||
Comment 1•20 years ago
|
||
![]() |
||
Comment 2•20 years ago
|
||
"Simplified" would mean the JS is simplified too. As it is, it's not clear
which part of the JS is responsible. Is the <noscript> part needed, for that
matter?
Keywords: testcase
Reporter | ||
Comment 3•20 years ago
|
||
Boris, is this better?
Attachment #162044 -
Attachment is obsolete: true
Comment 4•20 years ago
|
||
Document.write is not supported in XHTML.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Reporter | ||
Comment 5•20 years ago
|
||
So uncaught exceptions in Mozilla are okay? (just asking, because I think about
it as about errors).
![]() |
||
Comment 6•20 years ago
|
||
The exception is uncaught by the page, not by Mozilla.
Yes, Mozilla's behavior here is correct. There is indeed an error, and it's an
error in the page -- it's trying to use document.write in an XHTML document.
Status: RESOLVED → VERIFIED
![]() |
||
Comment 8•20 years ago
|
||
*** This bug has been marked as a duplicate of 68193 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago → 20 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Updated•20 years ago
|
Status: RESOLVED → VERIFIED
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•