- From: Scott Miles <sjmiles@google.com>
- Date: Wed, 20 Feb 2013 16:14:22 -0800
- To: Dimitri Glazkov <dglazkov@chromium.org>
- Cc: public-webapps <public-webapps@w3.org>, Jan Miksovsky <jan@quickui.org>
Received on Thursday, 21 February 2013 00:14:50 UTC
+1 S On Wed, Feb 20, 2013 at 4:04 PM, Dimitri Glazkov <dglazkov@chromium.org>wrote: > Folks, > > As of https://dvcs.w3.org/hg/webcomponents/rev/505225bb4a7b, the > custom elements spec no longer has the extra plumbing for > automatically creating all shadow trees along its inheritance chain. > This responsibility now falls to the developer of the custom element > to do this correctly (for example, by calling the callback of the > super-class). > > It's a trade-off between convenience and flexibility. When I spoke > with developers of the frameworks that are experimenting with shadow > DOM and custom elements, I found that there were already two different > ways (both slightly incompatible with what was currently spec'd) of > initializing the shadow trees. This told me that the spec had too much > opinion and it needed to get out of the way. > > :DG< >
Received on Thursday, 21 February 2013 00:14:50 UTC