- From: Joey Arhar via GitHub <sysbot+gh@w3.org>
- Date: Thu, 15 Aug 2024 22:42:26 +0000
- To: public-css-archive@w3.org
> Hopefully we're ok with dropping the bit about no longer matching when the user returns to the control, given that HTML doesn't say that. (Or do any engines implement that?) Yeah I don't think this is a thing. I think that the only case we start matching these and then stop matching them is when the form is reset. > other pseudo-classes (:invalid, :out-of-range, :required) that should perhaps be defined in the sections for those pseudo-classes but probably shouldn't be defined here. > making the parallel with :valid and :invalid more explicit again (but hopefully dropping the muddled bit about the other pseudos) Ok, I added a paragraph to the :valid and :invalid sections. How does it look? > explicitly mentioning submitting the form as a type of (or alternative to) significant user interaction with the control I added a paragraph for this. How does it look? -- GitHub Notification of comment by josepharhar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/9308#issuecomment-2292411010 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 15 August 2024 22:42:27 UTC