- From: <bugzilla@jessica.w3.org>
- Date: Thu, 06 Jan 2011 22:57:54 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11099
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
--- Comment #16 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-01-06 22:57:54 UTC ---
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the tracker issue; or you may create a tracker issue
yourself, if you are able to do so. For more details, see this document:
http://dev.w3.org/html5/decision-policy/decision-policy.html
Status: Partially Accepted
Change Description: see diff given below
Rationale:
I ended up doing a mixture of the proposals above.
If it's an element in the HTML, SVG, or MathML namespaces, then there's no
prefix, regardless of the DOM. Otherwise, I just let the qualified name through
and round-tripping will break.
If it's an attribute in the XML, XMLNS, or XLink namespaces, then there's the
canonical prefix (with an exception for xmlns:xmlns=""). If there's no
namespace, there's no prefix. Otherwise, I just let the qualified name through
and round-tripping will break.
I didn't do anything to stop duplicate attributes from being output, or to stop
namespace prefixes bound to non-canonical namespaces from stomping over the
canonical mapping's namespace, etc.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 6 January 2011 22:57:56 UTC