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

@tkent-google thanks, that answer the first part of my question, yet the "_least surprise_" would be having that working for built-in extends too.

The fact we think new features only for non built-in extends, since these has shipped and work great already in Chrome, Firefox, and the new Edge, is a bit concerning, imho.

Built-in extends should be first citizens of the Web, not something to eventually think about later. Since states use a specific pseudo selector to be accessed, there's not even a possible conflict between `:checked` and `:state(checked)`, and people using built-ins with CEs would benefit from a consistent API in case they need/want/use state.

Best Regards.

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