Link to issue number:

None

Summary of the issue:

In word, native extended table navigation commands alt+home, alt+end, alt+pageUp and alt+pageDown are report their result (i.e. the content of the landing cell) when using legacy document access, but not when using UIA.

Description of user facing changes

In Word with UIA, when using the native extended table navigation commands alt+home, alt+end, alt+pageUp and alt+pageDown, the landing cell will now be reported.

Description of development approach

• Factorize the script for this commands to use it for legacy as well as for UIA.
• Create separate _inTable methods for UIA and for legacy.
• For UIA text info's expand method, implement the support for cell unit.

Testing strategy:

Manual testing for both UIA and legacy.

Known issues with pull request:

None

Code Review Checklist:

• Documentation:
  • Change log entry
  • User Documentation
  • Developer / Technical Documentation
  • Context sensitive help for GUI changes
• Testing:
  • Unit tests
  • System (end to end) tests
  • Manual testing
• UX of all users considered:
  • Speech
  • Braille
  • Low Vision
  • Different web browsers
  • Localization in other languages / culture than English
• API is compatible with existing add-ons.
• Security precautions taken.

@coderabbitai summary