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
In a 2022 PR to html-aria (w3c/html-aria#396) it appears the the button element was updated to accept a role="combobox", and the same change was made to the validator (#1301). However, I am still seeing parsing errors throw when role="combobox" is added to a button using type="button".
Was this an oversight in the previous change? I don't believe it makes sense for role="combobox" to only be valid on a button using the implicit type="submit", since I would think that in a combobox pattern you would explicitly not want a button to submit its parent form, since the job of a button role="combobox" is to control its associated popup element.
Am I overlooking something? Or is this an additional improvement that could be made to the aria spec and the validator to support valid use cases of a combobox button?
The text was updated successfully, but these errors were encountered:
In a 2022 PR to
html-aria
(w3c/html-aria#396) it appears the thebutton
element was updated to accept arole="combobox"
, and the same change was made to the validator (#1301). However, I am still seeing parsing errors throw whenrole="combobox"
is added to abutton
usingtype="button"
.For example, this is invalid:
Throwing this error:
However, this is valid:
Was this an oversight in the previous change? I don't believe it makes sense for
role="combobox"
to only be valid on a button using the implicittype="submit"
, since I would think that in a combobox pattern you would explicitly not want a button to submit its parentform
, since the job of abutton role="combobox"
is to control its associated popup element.Am I overlooking something? Or is this an additional improvement that could be made to the aria spec and the validator to support valid use cases of a combobox button?
The text was updated successfully, but these errors were encountered: