Re: Custom Elements: is=""

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.


-- 
https://annevankesteren.nl/

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