RE: Shadow DOM background reading

The recent controversy thread on encapsulation of shadow DOM started in www-style:


http://lists.w3.org/Archives/Public/www-style/2014Feb/0221.html


it continued for a long while there before transitioning to public-webapps:


http://lists.w3.org/Archives/Public/public-webapps/2014JanMar/0217.html


Other recent threads that I have found interesting, on shadow DOM or on webcomponents, include:


- Trying to figure out an imperative API for insertion points, to explain/improve on <content select="">: http://lists.w3.org/Archives/Public/public-webapps/2014JanMar/0376.html


- A summary on the state of web components in general: http://lists.w3.org/Archives/Public/public-webapps/2014JanMar/0338.html


- "Why can't we just use constructor" instead of createdCallback for custom elements: http://lists.w3.org/Archives/Public/public-webapps/2014JanMar/0033.html



________________________________
From: Domenic Denicola <domenic@domenicdenicola.com>
Sent: Thursday, February 13, 2014 13:26
To: www-tag@w3.org
Subject: Shadow DOM background reading

Let's all try to get some reading done before next week's call, so we can have a good discussion on the relevant complexities.

Here's an introductory article that is, I have been told, up to date with the latest spec:

http://www.html5rocks.com/en/tutorials/webcomponents/shadowdom/

Here's the actual spec:

http://w3c.github.io/webcomponents/spec/shadow/

I'm going to make an attempt to at least skim, and perhaps deep-dive, into the spec text.

I'll let Alex take it from here, giving us pointers on recent controversy threads. Happy reading!