- 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
dbaron has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-scoping-1] should shadow-piercing descendant combinator (>>>) still be in specification == css-scoping-1 currently [specifies the shadow-piercing descendant combinator (>>>)](https://drafts.csswg.org/css-scoping/#deep-combinator). However, the [minutes of the April 2015 Web Components meeting](https://www.w3.org/wiki/Webapps/WebComponentsApril2015Meeting) 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 model > 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 css-scoping. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/640 using your GitHub account
Received on Monday, 24 October 2016 21:29:49 UTC