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
Should wa-visually-hidden-label and wa-visually-hidden-hint (#1454) really by properties on the wa- form components rather than new utility classes?
My concern is that they really don't seem general enough to be considered utility classes. These class only have support for specific components and would not work on native elements. (I assume someone will eventually try to place that class on the native label) And let's say the classes would be changed to properties on the supporting components, wouldn't those components just add the wa-visually-hidden class to the label and hint.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Should
wa-visually-hidden-labelandwa-visually-hidden-hint(#1454) really by properties on thewa-form components rather than new utility classes?My concern is that they really don't seem general enough to be considered utility classes. These class only have support for specific components and would not work on native elements. (I assume someone will eventually try to place that class on the native
label) And let's say the classes would be changed to properties on the supporting components, wouldn't those components just add thewa-visually-hiddenclass to the label and hint.Beta Was this translation helpful? Give feedback.
All reactions