You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today some initial styling and documentation were added for single select elements, using the required attribute and :invalid CSS.
The styling defaults the invalid Select element to appear red on page load. This should be better handled to only change state after use initiated invalid state, and not rely on color alone
The text was updated successfully, but these errors were encountered:
Scott, a question regarding the error messaging, currently styled as a tooltip. I've noticed that the tooltips themselves are not anchored to the offending select element, and if one were to inadvertently scroll it might appear as if the error message was part of another field. This might be something you wish to look at.
those are browser tooltips that firefox/chrome (not safari, didn't test ie) show if the required attribute is on a select. the scroll behavior is just how native tooltips work.
Looks like if you add a title="" to the select it will negate the native tooltip that the browser injects in there. It's interesting because VoiceOver doesn't announce it anyway, so from just a VO+Chrome test, seems there'd be no downside to doing that, other than removing the visual cue for sighted mouse users
Today some initial styling and documentation were added for single
select
elements, using therequired
attribute and:invalid
CSS.The styling defaults the invalid Select element to appear red on page load. This should be better handled to only change state after use initiated invalid state, and not rely on color alone
The text was updated successfully, but these errors were encountered: