W3C home > Mailing lists > Public > www-svg@w3.org > April 2010

Re: xlink:href test case

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Fri, 16 Apr 2010 22:14:57 -0400
Message-ID: <4BC919A1.1080308@mit.edu>
To: Robin Berjon <robin@berjon.com>
CC: Anne van Kesteren <annevk@opera.com>, www-svg WG <www-svg@w3.org>
On 4/16/10 4:32 AM, Robin Berjon wrote:
> I'm okay with the first, but the second is a problem because if the prefix is unbound the document cannot then be serialised to XML.

Why is this an issue?  It's trivial to construct DOMs using 
setAttributeNS that can't be serialized as XML without fixup.  Actual 
serializers in browsers munge namespace prefixes as needed to produce 
well-formed XML that will at least end up with the same localNames and 
namespaces; prefixes are not considered something that has to round-trip 
(though it's nice when they do, and serializers try to preserve them 
when possible).

> The following might work:
> Given setAttribute("foo:bar", "unidahut"),
>    - if there is an attribute the qualified name of which is "foo:bar", its value gets updated
>    - if there is no such attribute, but there is a namespace in scope for prefix "foo", then a foo:bar attribute is created with that prefix and that namespace

This isn't compatible with what UAs do now, last I checked.  Are we sure 
this won't break sites?

>    - if there is no such attribute and no matching namespace in scope, a "bar" attribute is created, with no prefix and in no namespace

This will _definitely_ break sites if applied to HTML.

Received on Saturday, 17 April 2010 02:15:34 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:47:20 UTC