W3C home > Mailing lists > Public > public-css-archive@w3.org > October 2016

[csswg-drafts] [css-scoping-1] should shadow-piercing descendant combinator (>>>) still be in specification

From: L. David Baron via GitHub <sysbot+gh@w3.org>
Date: Mon, 24 Oct 2016 21:29:42 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-184959923-1477344580-sysbot+gh@w3.org>
dbaron has just created a new issue for 

== [css-scoping-1] should shadow-piercing descendant combinator (>>>) 
still be in specification ==
css-scoping-1 currently [specifies the shadow-piercing descendant 

However, the [minutes of the April 2015 Web Components 
 have, in their summary of discussion of contentious bits, say:

> Contention point: E. Shadow boundary-piercing combinators
> Apple: Must not work in closed mode; think named parts is better 
> Mozilla: Would like to postpone piercing to v2
> Microsoft: Would like a named parts model
> Google: Think piercing was a mistake, should be removed
> Resolution: Remove

This suggests that perhaps the feature should not still be in 

Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/640 using your GitHub 
Received on Monday, 24 October 2016 21:29:49 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:04 UTC