Re: [w3ctag/design-reviews] [WebComponents] Custom state pseudo class (#428)

@plinss Thank you for the comment.

Currently I agree with [Tab's comment](https://github.com/w3c/webcomponents/issues/738#issuecomment-539704504) about non-boolean states.  If we want to add more complex values, we can add something like `addValue(token, value)` to `states` object, and extend `:state(<ident>)` to `:state(<ident>=value)`.

If we want really-flexible state matching, we should apply Houdini-like extensibility to selector matching.  e.g.  `my-element:func(myMatching) { ...}` and `function myMatching(element) { return element.state == 42; }`.



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/428#issuecomment-540346404