Fix-up of #10973: Fallback to POSITION_FIRST when reporting formatting info at caret to report in MS Excel #11914
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… report in Excel cells
This was referenced Dec 7, 2020
michaelDCurran
approved these changes
Dec 8, 2020
|
Is it important that this is in 2020.4? As it currently stands it will not be, and the changelog needs adjustment. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Link to issue number:
Discussion in #6479
Summary of the issue:
It is currently impossible to request formatting info for an Excel cell with NVDA+F.
Description of how this pull request fixes the issue:
NVDA+F now falls back to POSITION_FIRST if there is no caret.
Testing performed:
Known issues with pull request:
None known
Change log entry:
Section: Bug fixes
It is now possible to report formatting information for the focused Excel cell using NVDA+F.