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

From: Brian Di Palma [] 

> From your email it seems you can still achieve everything you can with custom elements when not using them, it would just involve more code/boilerplate.

I don't see how you can draw that conclusion from my email, except perhaps the trivial "everything can be implemented in terms of everything else in a Turing complete platform" sense.

Indeed, you could say that shadow DOM gives you nothing but syntactic sugar for a DOM access library that doesn't allow you to access things marked with a ".shadowed" class, and templates give you nothing more than <script type="text/x-template">.

Everything is syntactic sugar at one level. But custom elements (by themselves) seem to add significant power by giving you parser hooks and allowing you to create, well, custom elements, which can be returned from standard browser methods like querySelector.

> Splitting it up into separate specs is good, but it's clear they combine with each other.
> Making it easy and painless to combine them seems like common sense.

I think that there are many ways to combine the specs, and most of them are pretty darn easy already. Making one of them even easier by introducing the proposed coupling doesn't seem like a win.

Received on Saturday, 7 December 2013 23:07:49 UTC