Closed
Bug 946119
Opened 11 years ago
Closed 10 years ago
XML fragment parsing algorithm doesn't use the context element's default namespace URI
Categories
(Core :: DOM: HTML Parser, defect)
Core
DOM: HTML Parser
Tracking
()
RESOLVED
INVALID
People
(Reporter: rniwa, Unassigned)
Details
Attachments
(1 file)
1.16 KB,
text/html
|
Details |
Right now, Gecko doesn't use the context element's namespace as the default namespace in the XHTML fragment parsing algorithm when xmlns is not set as specified in http://www.whatwg.org/specs/web-apps/current-work/multipage/the-xhtml-syntax.html#parsing-xhtml-fragments See the attached test case. Also see https://bugs.webkit.org/show_bug.cgi?id=125132.
Comment 1•10 years ago
|
||
The attached test looks broken. It gives me the error: "contextElement.body is undefined". contextElement is a HTMLBodyElement. It looks like you were trying to get the element created by innerHTML. After fixing this up the test passes for me. A quick glance at the code looks like we are doing the right thing with namespaces. It also looks like the test FAIL was committed as an expected result in webkit. rniwa: Was the test fail intentional?
Flags: needinfo?(rniwa)
Reporter | ||
Comment 2•10 years ago
|
||
Oops, you're right. There is a bug in the code.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(rniwa)
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•