Opened 9 years ago
Closed 9 years ago
#9918 closed bug (patcheswelcome)
Autocomplete above focusable list moves focus from autocomplete results to list (JAWS)
Reported by: | norabora | Owned by: | dylanb |
---|---|---|---|
Priority: | minor | Milestone: | none |
Component: | ui.autocomplete | Version: | 1.10.4 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
My application has an autocomplete input right above a list with focusable list items. When running JAWS 15 and testing in FF 26 on Windows 7, if I perform a search and start using the down arrow to navigate the results, after correctly going through 2-3 items in the autocomplete list, focus will move to the other list with no indication to JAWS that focus has moved. This issue is not seen when running NVDA or without JAWS so there could be something JAWS is doing wrong but there should be some indication from the autocomplete list that focus has moved out of it.
Change History (9)
comment:1 follow-up: 2 Changed 9 years ago by
Owner: | set to norabora |
---|---|
Status: | new → pending |
comment:2 Changed 9 years ago by
Status: | pending → new |
---|
Replying to tj.vantoll:
Hi norabora,
Can you confirm that this behavior still occurs with the latest build of the library and this reduced test case: http://jsfiddle.net/tj_vantoll/PwuB5/.
No, the issue happens only when there's a focusable list below the autocomplete input box in the DOM. With the list added back and simplified, http://jsfiddle.net/PwuB5/2/, yes I still see the issue.
comment:3 Changed 9 years ago by
Owner: | changed from norabora to dylanb |
---|---|
Status: | new → assigned |
comment:4 Changed 9 years ago by
This is a JAWS 15 specific problem. It does not occur in JAWS 14. I will report the problem to Freedom Scientific.
comment:5 Changed 9 years ago by
If you file a bug with them, can you put the ticket number/link here so that I can track it?
comment:6 Changed 9 years ago by
Norabora - Can you tell me whether you were using IE or Firefox when you produced this problem? We are able to reproduce this problem only in FF with JAWS 15.
comment:8 Changed 9 years ago by
Yeah, JAWS does not work well with Firefox, please use JAWS with IE and NVDA with Firefox.
comment:9 Changed 9 years ago by
Resolution: | → patcheswelcome |
---|---|
Status: | assigned → closed |
Yeah, those are the combinations we try to support, along with VoiceOver for Safari/iOS. If there's a workaround that isn't really hacky or large, we can consider it.
Hi norabora,
Can you confirm that this behavior still occurs with the latest build of the library and this reduced test case: http://jsfiddle.net/tj_vantoll/PwuB5/.