- From: Domenic Denicola <notifications@github.com>
- Date: Mon, 14 Mar 2016 18:24:18 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
Received on Tuesday, 15 March 2016 01:24:46 UTC
@TabAtkins, could use your help here. Here is what I have currently: https://w3c.github.io/webcomponents/spec/custom/#the-defined-element-pseudo-class-defined It's pretty simple, but that's fine. What I'm confused about is how pseudo-classes get split between Selectors and HTML. E.g. compare: - https://drafts.csswg.org/selectors-4/#enableddisabled - https://html.spec.whatwg.org/#selector-enabled Is the idea that we should have Selectors (or some other CSS spec) say something like > The :defined pseudo-class represents elements that are defined as having behavior by the host language. For example, in [HTML], ... and then in HTML we should say > The :defined pseudo-class must match any element that is [defined](https://w3c.github.io/webcomponents/spec/custom/#dfn-defined-element) ? Is Selectors the right place for this? What heading would it go under? Maybe "Tree-Structural pseudo-classes"? --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/439
Received on Tuesday, 15 March 2016 01:24:46 UTC