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
Dimitar-Goshev
changed the title
Access key attribute should not be present on MultiSelect, when it has no value
Unexpected empty accesskey attribute set to MultiSelect by default
Feb 17, 2021
Bug report
MultiSelect renders an empty
accesskey
attribute on its input, when no access key is passed to its<select>
element.Reproduction of the problem
Run the MultiSelect demo and review the markup of the widget. You will notice its
<input>
has anaccesskey
attribute.Expected/desired behavior
accesskey
attribute should not be presentEnvironment
The text was updated successfully, but these errors were encountered: