Re: :required validation in CSS3
"Jukka K. Korpela" <[email protected]> Wed, 15 Jun 2016 23:06:06 +0300
| Newsgroups | gmane.org.w3c.validator.css |
|---|---|
| Message-ID | <[email protected]> |
15.6.2016, 1:38, Benedicte Roussel wrote: > I have used :required in a HTLM5 form<label for=3D"mail">Votre mail : > </label><input type=3D"email" name=3D"mail" id=3D"mail" required/>. It = was > understood by the navigators but in the validator instead of writing th= e > following in my CSS3: > > *:required* =E2=80=93 =E2=80=93 > *I had to write the following in order that my CSS (level3) be validate= d.* > > > *[required]* I=E2=80=99m afraid there isn=E2=80=99t any definite published description= of exactly=20 what the CSS Validator is checking against. But it seems that (possibly=20 with some exceptions) it recognizes W3C CSS specifications with maturity=20 level CR (Candidate Recommendation) or higher. And as far as I can see, :required is not defined in such documents. =E2=80=9CSelectors Level 4=E2=80=9D mentions it, but it=E2=80=99s just a = Working Draft and has=20 not made much progress (the newest Working Draft is dated 2 May 2013). > *Could we expect that :required be validated by CSS3 validator in a ver= y > near future ? Or am I dreaming about it ?* I wouldn=E2=80=99t expect so. But why would that matter? There is the simple workaround you mention, using the attribute selector=20 [required]. (I wonder whether :required offers any particular benefit=20 over it.) Yucca