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

Mouse movement in chrome context menu reads every item #9442

Closed
Qchristensen opened this issue Apr 3, 2019 · 5 comments
Closed

Mouse movement in chrome context menu reads every item #9442

Qchristensen opened this issue Apr 3, 2019 · 5 comments

Comments

@Qchristensen
Copy link
Member

Initially reported by a user (DM on twitter) and reproduced by me.

Steps to reproduce:

  1. Press the context menu key or right click the mouse in a web page in Chrome
  2. move the mouse down through the items quickly enough that it should skip some.

Actual behavior:

NVDA reads every menu item completely that the mouse moves over (if the mouse is moved sideways out of the menu, down, and then back onto a lower item, only the item which now has the mouse over it is read).

Expected behavior:

NVDA's reading of each item should be interrupted as the mouse moves over the next item, as happens in other places.

System configuration

NVDA installed/portable/running from source:

NVDA version:

NVDA 2019.1 installed

Windows version:

Windows 10, insider build 18362.1

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

Chrome 73.0.3683.86 (official build, 64 bit)

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?

The same issue happens with NVDA 2018.4.1, but NOP with NVDA 2018.3.2

@Adriani90
Copy link
Collaborator

@Qchristensen can you still reproduce this in Chrome 116 with NVDA 2023.2 RC? Also try to enable cancelable speech in the NVDA advanced settings and see if it makes a difference.

@Qchristensen
Copy link
Member Author

"Attempt to cancel speech for expired focus events" is set to "Yes (Default)".

I am using:
Chrome Version: 116.0.5845.112
with NVDA 2023.2 RC
on Windows 11 (64-bit) Version: 22H2, Build: 22621.2134

In this setup, this is no longer reproduceable. If I go into advanced settings and set "Attempt to cancel speech for expired focus events" to "No", then this is still reproduceable. Aside from testing, is there much use case for someone to set this to "No"? (if not, then this issue can be closed - and even if there is, maybe this could simply be recorded as a known side effect of setting that to No?

@Adriani90
Copy link
Collaborator

I suggest not to close this issue until cancelable speech for focus events is enabled by default. Currently no is the default behavior.
I vote for enabling cancelable speech by default.
cc: @seanbudd the PR #11266 enabled cancellable speech by default only until 2021.1, so maybe this should be re-enabled by default in the beta at least. The issues raised in that PR are now solved according to my tests.

@Adriani90
Copy link
Collaborator

by the way cancellable speech is not experimental anymore, as per #12454, so it should be moved from advanced category to speech settings category.

@Adriani90
Copy link
Collaborator

Ok it seems cancellable speech is already enabled by default, I am closing this as works for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants