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
Wrong cell read in Excel #12200
Comments
I can not replicate this in latest alpha for Excel 2019.
|
I can reproduce this with NVDA 2021.3.4, it is very finicky and seems to be related to the timing of the arrow key presses. It seems like occasionally the second navigation isn't observed by NVDA, resulting in no speech. The first speech would be cancelled by the second key press. It only seems to happen if I am first editing a cell (as per the steps to reproduce). A log snippet, note that speech for the cell coords
|
I'm using NVDA2022.1beta4 and disabled the UIA for Excel option in the NVDA advanced settings panel and I have the following findings: steps
|
I can replicate @cary-rowen's STR in the above comment. |
Could you please test with last alpha of NVDA? This might have improved after #14701. At least I can notice a significant improvement in performance whle navigating in Excel tables with the last alpha version. |
@Adriani90 Thanks |
Steps to reproduce:
Actual behavior:
If I press down and left too fast, I hear either B2 or nothing.
Expected behavior:
I should hear A2.
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
2020.4
Windows version:
Version 2004 (OS Build 19041.867)
Name and version of other software in use when reproducing the issue:
Microsoft® Excel® 2019 MSO (16.0.13801.20240) 32-bit
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.
2020.3, same result
If add-ons are disabled, is your problem still occurring?
Yes
Did you try to run the COM registry fixing tool in NVDA menu / tools?
No
The text was updated successfully, but these errors were encountered: