W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2014

Status of the Shadow DOM Specification

From: Ryosuke Niwa <rniwa@apple.com>
Date: Tue, 04 Feb 2014 21:00:01 -0800
Message-id: <00586DC9-7A3A-4422-B67C-6A4CE2B35446@apple.com>
Cc: Edward O'Connor <eoconnor@apple.com>
To: public-webapps <public-webapps@w3.org>
Hi,

Apparently there has been discussions about hats and cats selector combinators in www-style:
http://lists.w3.org/Archives/Public/www-style/2014Feb/0032.html

In that Tab (Atkins) from Google made a comment saying that Chrome will be shipping Shadow DOM in the very near future:
http://lists.w3.org/Archives/Public/www-style/2014Feb/0036.html

My understanding is that shadow DOM specification is still being chartered by this very WebApps working group, and unless I’m missing something, the specification was not considered stable enough for any browser vendor to ship without prefixes or behind a flag at least in the last TPAC.  In fact, the current working draft has many outstanding issues including issue 6 that says “Hats, ^, and Cats, ^^, selector combinators should be defined in this section.”

Also, the latest working draft doesn’t reflect recent discussions on the various mailing lists.  For example, section 7.1 Ranges and Selections still mentions that selections are to be entirely within a single root: http://w3c.github.io/webcomponents/spec/shadow/#ranges-and-selection but Jonas (Sicking) from Mozilla has made a pretty strong argument for allowing selection to be extended across shadow boundaries following http://lists.w3.org/Archives/Public/public-webapps/2013OctDec/0106.html

Am I completely misunderstanding the status of the specification or missing something?

- R. Niwa
Received on Wednesday, 5 February 2014 05:00:18 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:21 UTC