Skip to content

MS Word object model browse mode: ensure native selection mode toggle message reflects that it cannot be turned off#16151

Merged
seanbudd merged 1 commit into
betafrom
pr16129_withWordObjectModelSupport
Feb 9, 2024
Merged

MS Word object model browse mode: ensure native selection mode toggle message reflects that it cannot be turned off#16151
seanbudd merged 1 commit into
betafrom
pr16129_withWordObjectModelSupport

Conversation

@michaelDCurran

Copy link
Copy Markdown
Member

Link to issue number:

Follow up from #16129
Fixes #16097

Summary of the issue:

Selecting text in Browse mode in Microsoft Word moves the physical selection. Thus it is the equivalent to native selection mode. Pr #16129 ensured that Browse mode in MS word with UI Automation took this into account and made the toggle message report that native selection mode could not be turned off. However this has not been done for MS Word object model, and NVDA states that native selection mode is unsupported.

Description of user facing changes

  • When trying to toggle native selection mode in Browse mode in MS Word when not using UI Automation, NvDA will correctly state that native selection mode cannot be turned off.
  • When copying text with control+c in browse mode in MS Word when not using UI Automation, formatting is now also copied.

Description of development approach

Set browse mode for MS Word object model's _nativeAppSelectionMode to True.

Testing strategy:

  • Ensure NVDA's advanced setting for using UIA to access MS Word documents is set to only when necessary.
    *Open a document in MS Word.
  • Switch on NVDA's browse mode with NvDA+space.
  • Try to toggle native selection mode with NVDA+shift+f10.
  • confirm that NvDA reports that native selection mode cannot be turned off.

Known issues with pull request:

None known.

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.

…ult a and cannot be turned off, so ensure the toggle message reflects this.
@michaelDCurran michaelDCurran requested a review from a team as a code owner February 8, 2024 23:34
@michaelDCurran michaelDCurran requested review from SaschaCowley and removed request for a team February 8, 2024 23:34
@seanbudd seanbudd merged commit 9f5ceb1 into beta Feb 9, 2024
@seanbudd seanbudd deleted the pr16129_withWordObjectModelSupport branch February 9, 2024 00:20
@nvaccessAuto nvaccessAuto added this to the 2024.2 milestone Feb 9, 2024
@seanbudd seanbudd modified the milestones: 2024.2, 2024.1 Feb 12, 2024
Adriani90 pushed a commit to Adriani90/nvda that referenced this pull request Mar 13, 2024
…ult a and cannot be turned off, so ensure the toggle message reflects this. (nvaccess#16151)

Follow up from nvaccess#16129
Fixes nvaccess#16097

Summary of the issue:
Selecting text in Browse mode in Microsoft Word moves the physical selection. Thus it is the equivalent to native selection mode. Pr nvaccess#16129 ensured that Browse mode in MS word with UI Automation took this into account and made the toggle message report that native selection mode could not be turned off. However this has not been done for MS Word object model, and NVDA states that native selection mode is unsupported.

Description of user facing changes
When trying to toggle native selection mode in Browse mode in MS Word when not using UI Automation, NvDA will correctly state that native selection mode cannot be turned off.
When copying text with control+c in browse mode in MS Word when not using UI Automation, formatting is now also copied.
Description of development approach
Set browse mode for MS Word object model's _nativeAppSelectionMode to True.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants