Re: [webcomponents] Auto-creating shadow DOM for custom elements

The issue is that being an element and having shadow DOM -- or any display
DOM, for that matter -- are orthogonal concerns.

There are lots of c++ HTML elements that have no display DOM. Polymer
already has an even larger number.


On Sat, Dec 7, 2013 at 1:24 PM, Brendan Eich <brendan@secure.meer.net>wrote:

> (I'm an extensiblewebmanifesto.org signer.)
>
> Separate specs that compose well are great, and all.
>
> Requiring this kind of boilerplate out of the gave is not:
>
> this.createShadowRoot().appendChild(document.
> importNode(template.contents));
>
> Wanting to avoid this kind of boilerplate is not a "stab in the dark". Why
> can't we avoid it, even with separate specs that compose well? Part of
> composing well is not requiring excessive boilerplate.
>
> /be
>
>