On 12/20/11 4:49 PM, Edward O'Connor wrote:
     #player::controls

I'm worried that users may stomp all over the CSS WG's ability to mint
future pseudo-element names. I'd rather use a functional syntax to
distinguish between custom, user-defined pseudo-elements and
engine-supplied, CSS WG-blessed ones. Something like

     #player::shadow(controls)
or
     #player::custom(controls)

could do the trick. The latter (or some other, non-shadow-DOM-specific
name) is potentially more exciting because there may be more use cases
for author-supplied pseudo-elements than just the shadow DOM. For
instance, I could imagine an extension to DOM Range which would allow a
user to name a range for selector matching.

Would you expand more on that non-shadow-DOM-specific idea?
In the meantime, I'm happy with the ::shadow(controls) selector.


Reply via email to