Steps to reproduce:
- Open a document in MS Word
- Enable browse mode with NVDA+space
- Press NVDA+shift+F10
Actual behavior:
NVDA says "Application native selection mode not supported in this document"
Expected behavior:
NVDA should say "Application native selection mode cannot be disabled in this document" or "Application native selection mode cannot be disabled in this application".
Indeed, the native selection is always made in Word when selecting in Browse mode.
Same for Outlook of course.
NVDA logs, crash dumps and other attachments:
N/A
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
2024.1beta5
Windows version:
Windows 10 22H2 (AMD64) build 19045.3930
Name and version of other software in use when reproducing the issue:
Office 2016
Other information about your system:
N/A
Other questions
Does the issue still occur after restarting your computer?
Have you tried any other versions of NVDA? If so, please report their behaviors.
No
If NVDA add-ons are disabled, is your problem still occurring?
Not tested but should be the same
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Not tested
Steps to reproduce:
Actual behavior:
NVDA says "Application native selection mode not supported in this document"
Expected behavior:
NVDA should say "Application native selection mode cannot be disabled in this document" or "Application native selection mode cannot be disabled in this application".
Indeed, the native selection is always made in Word when selecting in Browse mode.
Same for Outlook of course.
NVDA logs, crash dumps and other attachments:
N/A
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
2024.1beta5
Windows version:
Windows 10 22H2 (AMD64) build 19045.3930
Name and version of other software in use when reproducing the issue:
Office 2016
Other information about your system:
N/A
Other questions
Does the issue still occur after restarting your computer?
Have you tried any other versions of NVDA? If so, please report their behaviors.
No
If NVDA add-ons are disabled, is your problem still occurring?
Not tested but should be the same
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Not tested