- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Fri, 16 Jun 2017 10:26:43 +0000
- To: public-css-archive@w3.org
SebastianZ has just created a new issue for https://github.com/w3c/csswg-drafts: == [selectors-4] Issue 11: Introduce pseudo-class matching when user changed the value of an input == Back in 2014 it was [suggested to add a pseudo-class matching when a user changed the value of an element](https://lists.w3.org/Archives/Public/www-style/2014Feb/0511.html). This topic was also already [discussed earlier by the CSSWG](https://lists.w3.org/Archives/Public/www-style/2012Aug/0749.html). I want to pick up that discussion again. The idea previously was to check whether the current value differs from the default value, expressed in JavaScript syntax, where `el.value !== el.defaultValue`, `el.checked !== el.defaultChecked`, currently selected options different from default selected options, etc., depending on the type of input. Suggested names so far are `:changed`, `:edited`, `:dirty`, `:user-dirtied` and `:user-interacted`. This would make `:user-invalid` redundant, as it could be expressed by `:changed:invalid`. Sebastian Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1533 using your GitHub account
Received on Friday, 16 June 2017 10:26:50 UTC