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
TagUI's select step helps users select options. The default design assuming best web design practices is to select using the value attribute. This is because value is the 'source-of-truth' that gets submitted when someone submits a form.
However, using value is non-intuitive for a non-developer user because 'value' is not something that is visible on the screen. Only text is visible. Furthermore, sometimes 'value' is some unique number that has nothing to do with the text of the option being selected. A TagUI workflow would be hard to understand in such situation what is being selected.
After thinking through, the best approach should be matching by value but should that fail, then match by text. It is not advisable to match by text first because 'value' is still the unique source-of-truth when submitting a form. But having this fallback should open up new use cases without causing problems for existing users use cases.
The text was updated successfully, but these errors were encountered:
kensoh
changed the title
select() to select by option text in addition option value - sync upstream change
select() to select by option text in addition option value - sync upstream [done]
May 12, 2021
aisingapore/TagUI#1001 - aisingapore/TagUI@c7b62db
TagUI's select step helps users select options. The default design assuming best web design practices is to select using the
value
attribute. This is becausevalue
is the 'source-of-truth' that gets submitted when someone submits a form.See this page from W3Schools on option value - https://www.w3schools.com/tags/att_option_value.asp
However, using value is non-intuitive for a non-developer user because 'value' is not something that is visible on the screen. Only text is visible. Furthermore, sometimes 'value' is some unique number that has nothing to do with the text of the option being selected. A TagUI workflow would be hard to understand in such situation what is being selected.
After thinking through, the best approach should be matching by value but should that fail, then match by text. It is not advisable to match by text first because 'value' is still the unique source-of-truth when submitting a form. But having this fallback should open up new use cases without causing problems for existing users use cases.
The text was updated successfully, but these errors were encountered: