-
Notifications
You must be signed in to change notification settings - Fork 350
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aria1.0 combobox autocomplete both example: When edit not empty and matches appear, Up Arrow does not set activedescendant to last match in list #821
Comments
Interesting ... The value changes to Arkansas, but activedescendant is not set to point to Arkansas. Unlike down arrow, I also see that the keyboard table entry for up arrow only describes what happens when the text box is empty, it does not say anything about what will happen when it is not empty. That implies nothing would happen. However, the current behavior of moving to the last value in the popup seems reasonable. |
Just so I understand the aria-activedescendant should point to any exact match of an option in the list with the textbox value? Jon |
No ... there are times where there is a match but focus is in the textbox. We don't want to change that. This is only about whether up arrow sets activedescendant if it was not previously set. It is happening when the textbox is empty, but not when the textbox contains a matching substring. The question is whether we think up arrow should do that. It seems logical to me; it would be the inverse of down arrow, which seems appropriate given that up/down mirror each other when the textbox is empty. So, why not mirror each other when the textbox contains a string that matches a set of one or more options. |
I will look into adding up arrow |
Fixed in pull request #857 |
…w documentation for the textbox Commit 18eacf8 for issue #821 fixes the behavior of the up arrow when the combobox is not empty and the listbox is open and displays suggested values. This commit corrects the documentation so that it accurately describes the adjusted behavior. modified: examples/combobox/aria1.0pattern/combobox-autocomplete-both.html modified: examples/combobox/aria1.0pattern/combobox-autocomplete-list.html
aria1.0 combobox autocomplete list and both examples: Correct up arrow documentation for the textbox Commit 18eacf8 for issue #821 fixes the behavior of the up arrow when the combobox is not empty and the listbox is open and displays suggested values. This commit corrects the documentation so that it accurately describes the adjusted behavior. modified: examples/combobox/aria1.0pattern/combobox-autocomplete-both.html modified: examples/combobox/aria1.0pattern/combobox-autocomplete-list.html
@jongund, thank you for your help with this. |
…w documentation for the textbox Commit 18eacf8 for issue w3c#821 fixes the behavior of the up arrow when the combobox is not empty and the listbox is open and displays suggested values. This commit corrects the documentation so that it accurately describes the adjusted behavior. modified: examples/combobox/aria1.0pattern/combobox-autocomplete-both.html modified: examples/combobox/aria1.0pattern/combobox-autocomplete-list.html
…w documentation for the textbox Commit 18eacf8 for issue w3c#821 fixes the behavior of the up arrow when the combobox is not empty and the listbox is open and displays suggested values. This commit corrects the documentation so that it accurately describes the adjusted behavior. modified: examples/combobox/aria1.0pattern/combobox-autocomplete-both.html modified: examples/combobox/aria1.0pattern/combobox-autocomplete-list.html
Hey all, there is a bug with aria-activedescendent in the aria 1.0 combobox-autocomplete-both example.
To replicate:
a. Notice that aria-activedescendent is not set on the textbox although the first entry is highlighted and autocompleted in the textbox. It looks as if visual focus is on the textbox still as well
Note that "down arrow" works if you use it instead of up arrow in step 3 above.
This bug was caught by writing tests! :)
The text was updated successfully, but these errors were encountered: