- From: <bugzilla@jessica.w3.org>
- Date: Wed, 19 Mar 2014 14:20:33 +0000
- To: www-dom@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25098 Bug ID: 25098 Summary: Clarifications on "legacy reasons" for namespace URI Product: WebAppsWG Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P2 Component: DOM Assignee: annevk@annevk.nl Reporter: sebp.muell.er@gmail.com QA Contact: public-webapps-bugzilla@w3.org CC: mike@w3.org, www-dom@w3.org In the DOM 4 Spec it says here: http://dom.spec.whatwg.org/#interface-attr [[ For legacy reasons, attributes also have an associated name, namespace, and namespace prefix. ]] I understand that "name" and maybe even "namespace prefix" exist for legacy reasons and might not need to be there if not for backwards compatibility. However I do not understand why "namespace" - (the URI) is mentioned in this sentence, unless you do not want to support namespaced attributes anymore. Without the namespace property I don't see any way of iterating over all attributes of an element and finding out which namespace they belong to. Please clarify whether "namespaces" will not be supported anymore other than for legacy reasons (which would mean that a number of XML documents (e.g. most SVG documents) could not be parsed anymore), or that only the "name" property is there for legacy reasons, because it can be deduced from the other properties. My suggested alternative wording would be: "Attributes can have an associated namespace and namespace prefix. For legacy reasons they also have an associated name." -- You are receiving this mail because: You are on the CC list for the bug.
Received on Wednesday, 19 March 2014 14:20:34 UTC