Steps to reproduce:
- Open a Word document and create a table (e.g. 4x4) with some content in each cell
- Use the native Word commands to jump to the start or the end of row or column, i.e. Alt+Home, Alt+End, Alt+PgUp and Alt+PgDown
Actual behavior:
The content of the cell before the move is reported instead of the content of the landing cell.
Expected behavior:
The content of the landing cell should be reported instead.
NVDA logs, crash dumps and other attachments:
N/A
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
2023.3
Windows version:
Windows 10 22H2 (AMD64) build 19045.3570
Name and version of other software in use when reproducing the issue:
Microsoft® Word 2016 (16.0.5413.1000) MSO (16.0.5413.1000) 32 bits
and
Microsoft® Word 2016 MSO (Version 2310 Build 16.0.16924.20054) 32 bits
Other information about your system:
N/A
Other questions
Does the issue still occur after restarting your computer?
Not tested
Have you tried any other versions of NVDA? If so, please report their behaviors.
NVDA 2023.2 NOK.
NVDA 2023.1 OK.
Thus it may be a regression of 2023.2 dev cycle.
From the change log, I imagine that #14708 or #14928 may have caused this regression, or just modified the timings so that a hidden bug has been uncovered. I have not bissected all the commits between 2023.1 and 2023.2 however.
Cc @jcsteh, any idea?
If NVDA add-ons are disabled, is your problem still occurring?
Yes
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Not tested
Steps to reproduce:
Actual behavior:
The content of the cell before the move is reported instead of the content of the landing cell.
Expected behavior:
The content of the landing cell should be reported instead.
NVDA logs, crash dumps and other attachments:
N/A
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
2023.3
Windows version:
Windows 10 22H2 (AMD64) build 19045.3570
Name and version of other software in use when reproducing the issue:
Microsoft® Word 2016 (16.0.5413.1000) MSO (16.0.5413.1000) 32 bits
and
Microsoft® Word 2016 MSO (Version 2310 Build 16.0.16924.20054) 32 bits
Other information about your system:
N/A
Other questions
Does the issue still occur after restarting your computer?
Not tested
Have you tried any other versions of NVDA? If so, please report their behaviors.
NVDA 2023.2 NOK.
NVDA 2023.1 OK.
Thus it may be a regression of 2023.2 dev cycle.
From the change log, I imagine that #14708 or #14928 may have caused this regression, or just modified the timings so that a hidden bug has been uncovered. I have not bissected all the commits between 2023.1 and 2023.2 however.
Cc @jcsteh, any idea?
If NVDA add-ons are disabled, is your problem still occurring?
Yes
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Not tested