Steps to reproduce:
- Load https://en.wikipedia.org/wiki/List_of_largest_cities
- Move to the second table (with 84 rows and 14 columns containing the list of largest cities)
- Use table navigation commands to move around the table:
- control+alt+arrows to move by one column
- control+alt+page up / down to move to top or bottom row
- control+alt+home to move to first column
- control+alt+end to move to end column
- Try the same on a table in the NVDA user guide
Actual behavior:
Everything works fine when testing with Chrome, and everything works fine testing with NVDA 2022.3.2.
Everything works as expected in the user guide, and everything works in the wikipedia table except the move to first column command, control+alt+home.
This command generates the following in the log:
IO - inputCore.InputManager.executeGesture (09:22:34.837) - winInputHook (21668):
Input: kb(desktop):alt+control+home
ERROR - scriptHandler.executeScript (09:22:34.872) - MainThread (2800):
error executing script: <bound method DocumentWithTableNavigation.script_firstColumn of <virtualBuffers.gecko_ia2.Gecko_ia2 object at 0x00BF9E70>> with gesture 'alt+ctrl+home'
Traceback (most recent call last):
File "virtualBuffers\gecko_ia2.pyc", line 540, in getTableCellAt
File "comtypes_init.pyc", line 856, in call
File "monkeyPatches\comtypesMonkeyPatches.pyc", line 32, in call
_ctypes.COMError: (-2147024809, 'The parameter is incorrect.', (None, None, None, 0, None))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "documentBase.pyc", line 321, in _getFirstOrLastTableCell
File "virtualBuffers\gecko_ia2.pyc", line 548, in _getTableCellAt
LookupError
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "scriptHandler.pyc", line 289, in executeScript
File "documentBase.pyc", line 500, in script_firstColumn
File "documentBase.pyc", line 417, in _tableMovementScriptHelper
File "documentBase.pyc", line 369, in _tableFindNewCell
File "documentBase.pyc", line 327, in _getFirstOrLastTableCell
AttributeError: '_TableCell' object has no attribute 'TableID'
Expected behavior:
NVDA logs, crash dumps and other attachments:
System configuration
NVDA installed/portable/running from source:
NVDA version:
NVDA 2022.4 installed exhibits this error.
Windows version:
Windows 11 (64-bit) Version: 22H2, Build: 22621.1105
Name and version of other software in use when reproducing the issue:
Firefox version: 108.0.2
Chrome Version: 108.0.5359.126
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.
NVDA 2022.3.2 works correctly with all table commands.
If NVDA add-ons are disabled, is your problem still occurring?
Yes - no add-ons installed.
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Yes. Also reported by users in the NVDA user group: https://nvda.groups.io/g/nvda/message/102618
Steps to reproduce:
Actual behavior:
Everything works fine when testing with Chrome, and everything works fine testing with NVDA 2022.3.2.
Everything works as expected in the user guide, and everything works in the wikipedia table except the move to first column command, control+alt+home.
This command generates the following in the log:
Expected behavior:
NVDA logs, crash dumps and other attachments:
System configuration
NVDA installed/portable/running from source:
NVDA version:
NVDA 2022.4 installed exhibits this error.
Windows version:
Windows 11 (64-bit) Version: 22H2, Build: 22621.1105
Name and version of other software in use when reproducing the issue:
Firefox version: 108.0.2
Chrome Version: 108.0.5359.126
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.
NVDA 2022.3.2 works correctly with all table commands.
If NVDA add-ons are disabled, is your problem still occurring?
Yes - no add-ons installed.
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Yes. Also reported by users in the NVDA user group: https://nvda.groups.io/g/nvda/message/102618