-
-
Notifications
You must be signed in to change notification settings - Fork 783
Incorrect table end markers in Word 365 #15828
Copy link
Copy link
Closed
Labels
component/UIA-ms-officeSpecific to UIA used in MS office applications.Specific to UIA used in MS office applications.component/braillep3https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Milestone
Metadata
Metadata
Assignees
Labels
component/UIA-ms-officeSpecific to UIA used in MS office applications.Specific to UIA used in MS office applications.component/braillep3https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Steps to reproduce:
Actual behavior:
At step 2:
At step 3:
At step 4:
Expected behavior:
The correct braille markers (e.g. tbl and tbl end) should be shown in the correct places (e.g. at the start and end of the entire table). Note that I did not provide details for every table cell. They show up similarly in braille. It seems that the last column/row has special behavior compared to the other cells.
NVDA logs, crash dumps and other attachments:
N/A
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
2023.3rc2
Windows version:
Windows 10 22H2 (10.0.19045) workstation AMD64
Name and version of other software in use when reproducing the issue:
Microsoft® Word for Microsoft 365 MSO (Version 2310 Build 16.0.16924.20054) 32-bit
Other information about your system:
N/A
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.
Yes: 2023.2 has the same behavior. 2023.1 works as expected. Also reproduced on another computer and other OS/Office language.
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?
Yes.