Re: [w3c/webcomponents] Add a CSS subtype selector. (#719)

@js-choi you're probably just not looking hard enough :) I know for sure it is on the [wiki](https://wiki.csswg.org/spec/selectors) and I'm nearly certain that at some point(s) in time it was even in drafts (you'd have to look through them but, for example, there were things in 'css 3' initial drafts in 1998/99 that we still don't have - this is one reason jQuery supported more selectors than browsers)... and I recall @wycats and I both pushed to close that gap.  Yes, one way that was discussed is ultimately reflected in @tabatkins' draft you linked above.

I don't really think that there is significant division on custom built-ins - you can extend your own components and there is a whitelist in the spec of 'simple' non-interactive elements.

In any case, in response to both this and @jasmith79's comments, my feelings are currently still expressed in my original reply: If you want to chase this, it seems like this is the wrong place.  If this is a need, I feel like the same magic should apply to native elements that extend. Seems bad if custom elements invents/has its own special magic for that to me.  Just my 2 cents.

-- 
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/719#issuecomment-354522719