- From: Adam Argyle via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Nov 2023 22:23:57 +0000
- To: public-css-archive@w3.org
> on every keypress would be very disruptive for users but it still does this, just after the initial await for blur. should it stop doing that then, and always be blur? https://github.com/w3c/csswg-drafts/assets/1134620/e6668285-9175-4eff-be2b-205c83132b96 i expect :user-* to be tied to users interacting with it, not "completing" their edits or "leaving" the field. for a [while now javascript libraries](https://medium.com/@vamsikurimeti92/understanding-angular-forms-validators-dirty-touched-pristine-value-and-more-fa322d462451#:~:text=Section%205%3A%20Dirty,control%20or%20not.) have offered even more queues (dirty, touched, pristine) for authors to use, css is barely catching up and doing mixed things -- GitHub Notification of comment by argyleink Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9583#issuecomment-1804777950 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 9 November 2023 22:23:59 UTC