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 12:14:34 +0200
To: "Henri Sivonen" <hsivonen@iki.fi>, "Ryosuke Niwa" <rniwa@webkit.org>
Cc: "Rafael Weinstein" <rafaelw@google.com>, "Webapps WG" <public-webapps@w3.org>, "Yehuda Katz" <wycats@gmail.com>
Message-ID: <op.wd42qkutwxe0ny@widsith-3.local>
On Fri, 11 May 2012 11:59:58 +0200, Ryosuke Niwa <rniwa@webkit.org> wrote:

> On Fri, May 11, 2012 at 1:55 AM, Henri Sivonen <hsivonen@iki.fi> 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.

True. Although they are widely known, and the "did you mean..." variants  
are probably not too difficult to pick up...

>> 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.
> That sounds rather complicated

Having a set of individual triggers as big as the overlaps seems and more  
fragile than, and quite possibly as complicated as, using xmlns. And what  
happens if SVG moves from using xl:href to just href?


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 10:15:21 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:40 UTC