Re: [csswg-drafts] [selectors-4] Issue 11: Introduce pseudo-class matching when user changed the value of an input (#1533)

> Having native CSS selectors for controls states would allow better flexibility though, as you can see Chromium guy who implemented it argues that current behavior is correct and in accordance with the specs.

That is true. But the html spec could be changed with agreement from vendors and tests.

> Current behavior is unacceptable per our design guidelines, which is the same as how Angular does it — show invalid controls after user visited them, not edited them.

That's how Firefox used to do it iirc, before I changed it to follow the current spec.

-- 
GitHub Notification of comment by emilio
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1533#issuecomment-2367045439 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 23 September 2024 00:33:01 UTC