Closed
Bug 320567
Opened 19 years ago
Closed 19 years ago
document.domain disables DOMParser
Categories
(Core :: XML, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 301678
People
(Reporter: tomn, Assigned: peterv)
References
Details
Attachments
(1 file, 2 obsolete files)
1.33 KB,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; da; rv:1.8) Gecko/20051111 Firefox/1.5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; da; rv:1.8) Gecko/20051111 Firefox/1.5 When calling DOMParser with a string after setting document.domain I get a permission denied. Reproducible: Always Steps to Reproduce: 1. Set domain "www.foo.com" to "foo.com" with document.domain 2. Parse a string with DOMParser DOMParser.parseFromString("<test>content</test>", "text/xml"); 3. Cannot access parsed XML document anymore Actual Results: Cannot access parsed XML document - access denied Expected Results: documentElement should return the element that is a direct child of document, which in this case would be the <test> element. This bug disables any use of DOMParser and XMLHttpRequest if in a frameset with different subdomains. In my case we have a frameset with multible subsites, forcing me to use document.domain. Now we need to parse a local string without calling an external document - so why the access denied? My testcase example is working in IE, Opera and Safari.
Reporter | ||
Comment 1•19 years ago
|
||
Reporter | ||
Comment 2•19 years ago
|
||
Attachment #206121 -
Attachment is obsolete: true
Assignee | ||
Comment 3•19 years ago
|
||
Assignee: xml → peterv
Attachment #206123 -
Attachment is obsolete: true
Status: UNCONFIRMED → ASSIGNED
Assignee | ||
Comment 4•19 years ago
|
||
This is fixed on the trunk, we should find which patch fixed this.
Version: Trunk → 1.8 Branch
Assignee | ||
Comment 5•19 years ago
|
||
*** This bug has been marked as a duplicate of 301678 ***
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Comment 6•18 years ago
|
||
*** Bug 324046 has been marked as a duplicate of this bug. ***
You need to log in
before you can comment on or make changes to this bug.
Description
•