@@ -2313,13 +2313,28 @@ The User-interaction Pseudo-class: '':user-error''</h4>
23132313 </pre>
23142314 </div>
23152315
2316- <!--
2317- <p class="issue">
2318- If it's necessary to distinguish between omitted and invalid values,
2316+ <div class="issue">
2317+ This pseudo-class, which was taken from the
2318+ <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/%3A-moz-ui-invalid">'':-moz-ui-invalid''</a> selector,
2319+ is named '':user-error'' rather than '':user-invalid''
2320+ because it combines checks for validity as well as omission.
2321+ We thought if it became necessary to distinguish between omitted and invalid values,
23192322 '':user-invalid'' and '':user-omitted'' could be used.
2320- -->
23212323
2322- Issue: Look into :-moz-ui-valid as well.
2324+ Alternatively, it might make more sense to rename this to '':user-invalid''
2325+ and add a '':blank'' pseudo-class that meant the field was blank.
2326+ This would allow authors to combine '':user-invalid:blank'' to select omitted required values,
2327+ and to combine '':user-invalid:not(:blank)'' to select filled out invalid values,
2328+ if necessary.
2329+
2330+ Both options are reasonable;
2331+ however since I can't think of a name for the '':-moz-ui-valid''
2332+ that would reasonably parallel '':user-error'' ,
2333+ I'm leaning somewhat to the second option.
2334+ (Other opinions welcome.)
2335+ </div>
2336+
2337+ Issue: Look into standardizing <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/%3A-moz-ui-valid">:-moz-ui-valid</a> as well.
23232338
23242339 Issue: Evaluate proposed <a href="https://lists.w3.org/Archives/Public/www-style/2014Feb/0511.html">:dirty pseudo-class</a>
23252340
0 commit comments