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

NVDA does not route the mouse correctly when using object navigation in MS Edge #7916

Closed
Adriani90 opened this issue Jan 17, 2018 · 4 comments · Fixed by #8572
Closed

NVDA does not route the mouse correctly when using object navigation in MS Edge #7916

Adriani90 opened this issue Jan 17, 2018 · 4 comments · Fixed by #8572

Comments

@Adriani90
Copy link
Collaborator

Adriani90 commented Jan 17, 2018

Steps to reproduce:

  1. Using Edge, Go to
    https://www.nvaccess.org/post/in-process-17th-march-2017/
  2. Navigate in browse mode to an image from the article
  3. Use object navigation to focus the image with the NVDA cursor
  4. In laptop layout, press NVDA+Shift+m to route the mouse to the NVDA cursor

Expected behavior:

NVDA should move the mouse onto the image like in firefox or Internet Explorer.

Actual behavior:

Sometimes NVDA moves the mouse elsewhere but not on the image, sometimes the mouse is not being moved at all.

System configuration:

NVDA version:
2017.4

NVDA Installed or portable:
Both

Other information:

Windows version:
Windows 10 Build 16.299.64

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

Other questions:

Does the issue still occur after restarting your PC?
Yes

Have you tried any other versions of NVDA?
No

@feerrenrut
Copy link
Contributor

Possibly related to #7915.
As with #7915, check if the position reported by Edge matches the actual position of the element, if not then we need to raise a bug against Edge.

@Adriani90
Copy link
Collaborator Author

#5602

@Adriani90
Copy link
Collaborator Author

#7083

@Adriani90
Copy link
Collaborator Author

Adriani90 commented Mar 12, 2018

#8076 is related, however the discussion could be continued there.

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

Successfully merging a pull request may close this issue.

4 participants