bzbarsky at MIT.EDU
Thu Sep 23 17:50:42 PDT 2010
On 9/23/10 6:12 PM, Mounir Lamouri wrote:
> So, to improve the user experience while using web forms we would like
> to fix that. However, we are wondering if :invalid (and :valid?)
> specifications should be updated to take UX considerations or if a new
> pseudo-classe should be created. Does anyone has an opinion about that?
I was actually thinking about this the other day... We could add a new
pseudo-class for matching form controls that have their default value
(or that don't, depending on how we expect this to be used). then you
could style :invalid:not(:has-default-value) specially, say....
Or I suppose we could just add a new pseudo-class that means the above.
Are there cases when pages would set invalid default values and want
them flagged as such in UI?
More information about the whatwg