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

UpArrow and downArrow not working in browseMode #18

Open
dennischenfeng opened this issue May 30, 2023 · 2 comments
Open

UpArrow and downArrow not working in browseMode #18

dennischenfeng opened this issue May 30, 2023 · 2 comments

Comments

@dennischenfeng
Copy link

dennischenfeng commented May 30, 2023

Steps to reproduce

  1. I have a fresh new install of latest versions of NVDA and Browser nav. See below for all my software info.
  2. Open browser (firefox or chrome) to any site, like https://www.nvaccess.org/download/
  3. In browse mode, try pressing the arrow keys upArrow or downArrow. For me, they don't seem to do anything (no movement nor speech). The leftArrow and rightArrow seem to work properly, speaking the characters.
  4. Also try starting "say all" (NVDA+a). I have the skim reading feature enabled, so pressing upArrow/downArrow moves lines while continuing the sayAll. Interestingly, when in sayAll, the upArrow and downArrow seem to work fine.
  5. I also tried changing between laptop keyboard layout and desktop keyboard laptop, but still fails on both.
  6. Once I disable browserNav and restart NVDA, the up/downArrow regain their normal functionality. So I presume something's wrong with browserNav.

My current workaround is to go back to NVDA 2022.4 and install all the older versions of add-ons.

Software info:

  • NVDA version 2023.1
  • BrowserNav v2.5. Downloaded from NVAccess site (https://addons.nvda-project.org/addons/browsernav.en.html). Used first link because second link is broken.
  • Windows 11 Home
  • NVDA add-ons: only Browser Nav is enabled.
  • In NVDA advanced settings, ensured that custom scripts in scratchpad directory are not enabled.
@amirsol81
Copy link

@dennischenfeng Quite interestingly, I've seen this on Win 7 with Chrome not on Windows 11. Even with Windows 7 it happens only if Skip clutter for line and paragraph navigation, Slash and Control+Slash, are enabled.

@dennischenfeng
Copy link
Author

I'm not completely sure what fixed it, but I now no longer have this issue.
I'm on the same computer, and it doesn't look like the NVDA version or Browser Nav versions have changed.
The only thing I seem to be able to chalk it up to is that I had a Windows update earlier today.

I'm happy with having the issue closed now, unless others say otherwise.

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

No branches or pull requests

2 participants