Add ability to report the document layout in Microsoft Word #17324
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:
Fixes issue #15088
Summary of the issue:
Knowing the document layout in Microsoft Word may be important, for example, to figure outwhy a table is not read properly when navigating with NVDA, and in other situations.
Description of user facing changes
When using the report title command in Microsoft Word, if the document layout can be determined, it Will be added to the title.
When Microsoft Word is active, in the input gestures dialog, the description of this command will be presented indicating that it works in Word, in contrast to the global commands title.
Description of development approach
In the WinWord app module, a script has been created, using
api.getStatusBar()
to search for the status bar. If it can be found, and one of the bar status children has the PRESSED state, its name Will be added to the title, assuming that it correspond to the document layout.Testing strategy:
Tested manually, in Word documents, with the ribbon active and inactive, and with a dialog opened to check that the title without the document layout is reported when the status bar is not found.
Known issues with pull request:
None.
Code Review Checklist:
@coderabbitai summary