Re: [w3c/webcomponents] Interface/class-based selector (#719)

I guess there are two approaches to consider:

1. Add CSS the ability to introspect the JS state. 
2. Add a mechanism to define selector matching mechanism to custom element.

(1) is probably a non-starter because we can't define when to evaluate JS states. And observing changes to JS states is extremely expensive.

-- 
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-366816927