Skip to content
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

Jump to bottom

NVDA Reporting Contents of Combo Boxes with High Verbosity #2685

Closed
nvaccessAuto opened this issue Sep 21, 2012 · 8 comments
Closed

NVDA Reporting Contents of Combo Boxes with High Verbosity #2685

nvaccessAuto opened this issue Sep 21, 2012 · 8 comments
Labels
blocked/needs-external-fix bug

Comments

@nvaccessAuto
Copy link

Reported by ateu on 2012-09-21 15:48
Steps to reproduce:

  1. Open Google Chrome Canary or a newer version of Chrome;
  2. Go to the NVDA ticket editor;
  3. Access any combo box and use the arrow keys to hear the items.

Expected result: When arrowing through the items, NVDA should announce just the current item.
Actual result: NVDA announces the previous item, list item editable and the current item. (I.g. in the combo box where we choose the type, when arrowing from the first to the second item, NVDA says "defect list item editable enhancement" instead of just enhancement.
@nvaccessAuto
Copy link
Author

Comment 2 by ateu on 2012-10-09 10:32
Mesar, can you please add a cc?

@nvaccessAuto
Copy link
Author

Comment 3 by MHameed on 2012-10-09 11:23
Sorry I dont have time to debug/provide technical info, so will wait for Jamie/Mick to locate the problem, then we can add Dominic if needed.
Thanks.

@nvaccessAuto
Copy link
Author

Comment 4 by leonarddr on 2013-09-25 09:38
This problem doesn't occur in browse mode, but in focus mode.

@nvaccessAuto
Copy link
Author

Comment 5 by ateu on 2013-12-25 13:38
Hi,

Focus mode is part of browse mode, since we are talking about Browsers

@nvaccessAuto
Copy link
Author

Comment 6 by ateu on 2013-12-25 13:38
Jamie, do you think this can be fixed by NVDA?

@nvaccessAuto
Copy link
Author

Comment 7 by jteh on 2014-02-13 09:07
GoogleIssue:chromium:323462

@ehollig
Copy link
Collaborator

ehollig commented Jul 25, 2017

This appears to be fixed in May 2015 from Google Issue Chromium:323462

@ehollig
Copy link
Collaborator

ehollig commented Aug 20, 2017

Closing, as the Google Issue Chromium:323462 has been fixed.

@ehollig ehollig closed this as completed Aug 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
blocked/needs-external-fix bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nvaccessAuto @ehollig