-
-
Notifications
You must be signed in to change notification settings - Fork 784
In Excel, cell format is reported on each move #15091
Copy link
Copy link
Closed
Labels
bug/regressionp3https://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
bug/regressionp3https://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:
On each move, NVDA reports: '"align default vertical align default cell".
Expected behavior:
The alignment should be reported only if it changes with respect to the previously selected cell.
NVDA logs, crash dumps and other attachments:
N/A
System configuration
NVDA installed/portable/running from source:
From source
NVDA version:
Alpha, commit 8accbfa
Windows version:
Windows 10 21H2 (AMD64) build 19044.3086
Name and version of other software in use when reproducing the issue:
N/A
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.
2023.1 installed is OK
If NVDA add-ons are disabled, is your problem still occurring?
Not tested
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Not tested
Investigation
I have tested various versions (commits) of NVDA and found that the regression has been introduced in a5931dd by PR #14984.
In
NVDAObjects/window/excel.py,, in functionscript_changeSelection, changing back:oldSelection = self._getSelection()to:
oldSelection = api.getFocusObject()allows to fix the issue.
However, this probably defeats the purpose of #14984.
@LeonarddeR any idea?