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: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 9 May 2012 11:24:56 +0200
Message-ID: <CAAWBYDBNOSdufaWwtDNDD9S5i+tYchgPhv3qn3m8MWju5H4FCA@mail.gmail.com>
To: Henri Sivonen <hsivonen@iki.fi>
Cc: public-webapps@w3.org
On Wed, May 9, 2012 at 11:10 AM, Henri Sivonen <hsivonen@iki.fi> wrote:
> If we end up doing (flawed) list-based magic, we need to make sure the
> SVG working group is on board and henceforth avoids local name
> collisions with HTML and MathML.

Yes, we (SVGWG) is on board with this.  We won't introduce new
elements that conflict.

(Currently, SVG and HTML conflict with <style>, <script>, <a>, and
<font>.  SVG and MathML conflict in <set> and <image>.  HTML and
MathML don't conflict at all.)

> If the API required the caller to request SVG explicitly, would it be
> a sure thing that jQuery would build magic heuristics on the library
> side?

I just pinged Yehuda to check, but I'd wager that jQuery will add SVG
detection to their current context detection if SVG continues its
climb into relevance for webdevs.

Received on Wednesday, 9 May 2012 09:25:47 UTC

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