Skip to content

NVDA+Up fails to read or spell many controls and lines in Google Chrome #11285

@amirsol81

Description

@amirsol81

Insert+Up (NVDA+Up) is used in NVDA to report the current line under the application cursor. Pressing it twice will spell the current line. Pressing three times will spell the line using character descriptions. However, pressing it on many controls in Google Chrome 127 forces NVDA to remain silent instead of reporting the current line or spelling the current line. This happens in various places like the menu (ALT+F), the list of bookmarks (ALT+F+B), etc.
Note: the issue was originally reported with Chrome 83, but it's duplicable with Chrome 127.

Steps to reproduce:

  1. Open Google Chrome and press Control+D to create a bookmark.
  2. Press Tab or SHIFT+Tab to move around various controls in the Bookmark creation dialog and press Insert+Up (NVDA+Up) on each control, once or twice.
  3. Alternatively, you can simply press ALT+F in Google Chrome and try pressing Insert+Up on items such as History submenu, Bookmarks submenu, Make text smaller, Make text larger, Full screen, Find, More tools, etc.
  4. You may also try pressing Insert+Up on your Bookmarks in the Bookmarks submenu.

Actual behavior:

For most controls and items above, using Insert+Up forces NVDA to remain silent.

Expected behavior:

For these controls and items, NVDA should report the current line under the application cursor or spell it.

System configuration

NVDA installed/portable/running from source:

Installed

NVDA version:

Alpha 20381, but also duplicable with alphas going back to many months. Duplicable with Alpha 33355. Also duplicable with 2020.1 to 2024.3 RC1.

Windows version:

Windows 10 Pro 64-Bit, version 2004, and Windows 11 24H2 (26100.1457)

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

Google Chrome 83 Official to Chrome 127.

Other information about your system:

Other questions

Does the issue still occur after restarting your computer?

Yes

Have you tried any other versions of NVDA? If so, please report their behaviors.

Various releases over the past 3 years.

If addons are disabled, is your problem still occuring?

Yes

Did you try to run the COM registry fixing tool in NVDA menu / tools?

Yes

Metadata

Metadata

Assignees

No one assigned

    Labels

    app/chromep4https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions