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

Unable to close combo boxes in Google Chrome #8664

Closed
michaelDCurran opened this issue Aug 22, 2018 · 0 comments · Fixed by #8687
Closed

Unable to close combo boxes in Google Chrome #8664

michaelDCurran opened this issue Aug 22, 2018 · 0 comments · Fixed by #8687
Assignees
Labels
p4 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority
Milestone

Comments

@michaelDCurran
Copy link
Member

Steps to reproduce:

  1. Open a page in Google Chrome containing a combo box (select of size 1).
  2. In browse mode, arrow to the combo box.
  3. Press alt+downArrow to expand the combo box
    Note that the combo box opens and NVDA switches to focus mode.
  4. Press either escape or alt+upArrow to close the combo box.

Actual behavior:

NVDA switches to browse mode and the combo box does not close.

Expected behavior:

NVDA should switch to browse mode and the combo box should close.

Technical info:
NVDA thinks the list and list items inside the combo box are a part of the browseMode treeInterceptor.

System configuration:

NVDA Installed/portable/running from source:

Installed

NVDA version:

2018.3beta3

Windows version:

10.0.17744

Name and version of other software in use when reproducing the issue:

Google Chrome 70.0.3530.0 (Official Build) canary (64-bit) (cohort: Clang-64)

Other information about your system:

Other questions:

Does the issue still occur after restarting your PC?

yes

Have you tried any other versions of NVDA?

2018.2.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p4 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants