| 12:51 | <keithamus> | To clarify, the conclusion is that CustomStateSet shouldnt validate, and should allow setting states that are not valid productions within the CSS? annevk smaug |
| 13:19 | <annevk> | keithamus: As I tried to explain, it's not that straightforward. The API doesn't take a CSS identifier. It just takes a string. So the API accepts "1", but you can only match that in CSS writing "\31". And so yeah, no validation would be the same as getElementById() and seems like reasonable behavior. |
| 13:21 | <keithamus> | Thanks for the clarification annevk. Your explanation has been sufficient, I just wanted to double check so I can remove the checks in the PRs I'm making 😄 |
| 13:24 | <annevk> | keithamus: ooh, you're implementing this? Cool cool cool. |
| 13:26 | <keithamus> | I should have clarified my motivation for querying, it may have helped. But yes https://phabricator.services.mozilla.com/D191988#inline-1067489 and a very much WIP https://github.com/WebKit/WebKit/compare/main...keithamus:WebKit:custom-state-set |