W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2012

Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML

From: Charles McCathieNevile <chaals@opera.com>
Date: Fri, 11 May 2012 20:21:40 +0200
To: "Tab Atkins Jr." <jackalmage@gmail.com>, "Henri Sivonen" <hsivonen@iki.fi>
Cc: "Rafael Weinstein" <rafaelw@google.com>, "Webapps WG" <public-webapps@w3.org>, "Yehuda Katz" <wycats@gmail.com>
Message-ID: <op.wd5paeqjwxe0ny@widsith-3.local>
On Fri, 11 May 2012 13:13:09 +0200, Henri Sivonen <hsivonen@iki.fi> wrote:
> On Fri, May 11, 2012 at 1:09 PM, Tab Atkins Jr. <jackalmage@gmail.com>

>> Henri wrote:

>>> Open question: Should it be possible to use a magic attribute on the
>>> first tag token to disambiguate it as MathML or SVG? xmlns="..." would
>>> be an obvious disambiguator, but the values are unwieldy.  Should
>>> xlink:href be used as a disambiguator for <a>? If the use case is
>>> putting tree literals in code, it probably doesn't make sense to use
>>> <script> or <style> (either HTML or SVG) in that kind of context
>>> anyway. And SVG <font> has been rejected by Mozilla and Microsoft
>>> anyway.
>> SVG is chucking xlink, so that won't work.  In SVG2, <a> will just use
>> @href.
> Surely SVG2 has to support xlink:href in order to support existing  
> content.

It only has to recognise it, and it can prefer/recommend <a href ... which  
I believe is the plan.


Charles 'chaals' McCathieNevile  Opera Software, Standards Group
     je parle français -- hablo español -- jeg kan noen norsk
http://my.opera.com/chaals       Try Opera: http://www.opera.com
Received on Friday, 11 May 2012 18:22:33 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:34 UTC