Closed Bug 2512 Opened 26 years ago Closed 26 years ago

Default Namespaces don't work in XML

Categories

(Core :: DOM: HTML Parser, defect, P1)

defect

Tracking

()

VERIFIED FIXED

People

(Reporter: hyatt, Assigned: rickg)

Details

Default namespaces don't work in XML, i.e., if you specify a namespace in an enclosing tag, the child tags don't inherit the namespace. <xul xmlns:xul="http://www.mozilla.org/xul"> <tree> <===== Should belong to the XUL namespace by default <treeitem> <===== Should belong to the XUL namespace by default </treeitem> </tree> </xul> See section 5.2 of the namespace recommendation for complete details on how default namespaces should work.
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
I believe that this was fixed by Vidur on Friday.
Status: RESOLVED → REOPENED
Reopening. Attributes aren't properly defaulting to the appropriate namespace, e.g., if I say: <window xmlns:xul="http://blahblahblha"> <tree open="true"> </window> The open attribute above isn't part of the XUL namespace (as it should be), and so a GetAttribute using the XUL namespace fails. This isn't a big deal, since we can always explicitly qualify all attributes and tags, but it should be fixed eventually.
Status: REOPENED → RESOLVED
Closed: 26 years ago26 years ago
Fixed by latest update to parser.
QA Contact: 3849
david -- can you please verify this -- we do not have the ability to do at this time.
I should also have added - "or provide a test case for us to use"
It's fixed.
Status: RESOLVED → VERIFIED
per David's remark, marking as verifeid
You need to log in before you can comment on or make changes to this bug.