Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML from Tab Atkins Jr. on 2012-05-09 (public-webapps@w3.org from April to June 2012)

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 9 May 2012 18:11:52 +0200
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: public-webapps@w3.org
Message-ID: <CAAWBYDAc+F1cwAkc8hGVgRwV78vP=tk=ewofNEV8_12t9TZH_A@mail.gmail.com>

On Wed, May 9, 2012 at 5:27 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> On 5/9/12 5:24 AM, Tab Atkins Jr. wrote:
>> (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.)
>
> HTML has <image>, during parsing.  So it conflicts with both SVG and MathML
> there...  Though I suppose we could turn off that HTML feature inside
> templates; there's unlikely to be legacy content depending on it.  ;)

Yeah, I was going to mention that, but decided to leave it out for the
reason you just gave.  I should know better than to leave out
technical clarifications.  ^_^

(Related - the two conflicts between SVG and MathML are both "Content
MathML", which I don't think any browser renders.  Is this important?
Could we just let SVG always win on those two?)

~TJ

~TJ

Received on Wednesday, 9 May 2012 16:18:13 UTC