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

Re: Custom Elements: is=""

From: Anne van Kesteren <annevk@annevk.nl>
Date: Tue, 9 Jun 2015 17:06:28 +0200
Message-ID: <CADnb78ghwVY30PO1tZk2j1OhaYZ3FJH1zWbzpPjqVbKUHX3VTQ@mail.gmail.com>
To: Justin Fagnani <justinfagnani@google.com>
Cc: Alice Boxhall <aboxhall@google.com>, LĂ©onie Watson <lwatson@paciellogroup.com>, WebApps WG <public-webapps@w3.org>
On Mon, Jun 8, 2015 at 11:48 PM, Justin Fagnani
<justinfagnani@google.com> wrote:
> And I'm still concerned that removing is= would severely harm the cases
> where you need access to special parsing behavior like <template> and
> <style>.

With synchronous constructors you could imagine setting the parsing
policy in the constructor (as `this[Element.parsingPolicy] = x` or
some such). I wouldn't want to do that for v1, but it opens up that
possibility of making the HTML parser hackable.

Received on Tuesday, 9 June 2015 15:06:53 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:56 UTC