Open Qchristensen opened 2 years ago
Confirmed in Office 2019, Win 10, NVDA 2022.2 alpha.
I can reproduce this issue. The time that I bring up this issue on the mailing list is not acknowledging that this is a bug, I am just wondering why spelling errors are not reported when navigating by paragraph.
This has been introduced by PR #9217 to improve performance. I'm not sure how necessary it is for builds of MS Word where UIA is good enough to be used by default. It is worth pointing out that this is not NVDA specific - JAWS also does not report spelling errors during paragraph navigation last time i checked. cc @michaelDCurran
Is there any use case where spelling error reporting while navigating by paragraph brings a certain benefit to the users? The drawback would be worse performance. In general, when proofreading a text, skim reading is not usual. We read line by line or word by word, or we do say all and stop where the spelling error is.
So if there is no specific use case for this, I vote for closing.
Personally I don't have any preference. But could nvda make a statement in the user guide stating out that even if the erporting of error is enabled, under certain condition, the reporting of error will not be triggered? When I was just learnt about nvda, I was using navigate by paragraph to do proof read, in that way I don't hear any error being reported, so I assumed that I have no error in the document. However, later someone told me that my document has errors but at that time, I didn't know the problem is I should not review the document using paragraph navigation.
Steps to reproduce:
Actual behavior:
When reading with say all or by line (or by word), NVDA reports "spelling error" for any word it encounters where Word flags it as a spelling error.
When reading by paragraph, the text is read without any indication of the spelling error.
Expected behavior:
NVDA should report the spelling error when navigating by paragraph as it does when reading by line and during say all.
System configuration
NVDA installed/portable/running from source:
NVDA version:
NVDA 2022.1rc1 installed
Windows version:
Windows 10 (64-bit) Version: 21H2 (2009), Build: 19044.1706
Name and version of other software in use when reproducing the issue:
Office 365 (64-bit) Version: 16.0.15128.20140
Other information about your system:
I found that whether I had NVDA's advanced "Use UI Automation to access Microsoft Word" option set to "Default" or "Always" didn't make any difference.
Other questions
Does the issue still occur after restarting your computer?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
I didn't, although it was reported on the NVDA user group before the RC came out. I suspect it is not a new change.
If NVDA add-ons are disabled, is your problem still occurring?
Yes
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?