- From: Arno Gourdol <agourdol@adobe.com>
- Date: Fri, 25 Mar 2011 15:25:27 -0700
- To: Brady Duga <duga@ljug.com>
- CC: "www-style@w3.org" <www-style@w3.org>
Hi Brady,
> "If the CSS selector has no matching element, the rule will be ignored until a matching element becomes available."
>
> is really just saying "if the selector doesn't match anything then the selector doesn't match anything until the selector matches something." Isn't this just standard selector behavior?
This is probably not as clear as it could be. I think the intent here is to highlight the fact that the document tree could be modified subsequently (i.e. perhaps using a scripting language) and as a result a previously inapplicable rule would become applicable.
> Then this sentence really confuses me:
>
> "If no CSS selector is specified in the ::slot() rule, the element will be created as a root element."
>
> How can you have a pseudo-element without a selector? Do you mean if you just have this:
>
> ::slot() { ... }
>
> If so, isn't that redefining the basic selector mechanism? I would think that is just shorthand for:
>
> *::slot() { ... }
>
> since the '*' is optional when the universal selector is immediately followed by a pseudo-element.
That's a good point. The fact that it could be interpreted ambiguously is bothersome. One possible way of resolving would be to not allow the creation of root elements using ::slot().
– Arno ❉ @arnog ❉ Director of Engineering, Runtime Foundation
Received on Friday, 25 March 2011 22:30:30 UTC