Open amirsol81 opened 2 months ago
Please note that the "Spelling error" check box in the Document Formatting pane of NVDA's Settings window should be checked to duplicate this.
cc: @josephsl
I can replicate this on Windows 11 (64-bit) Version: 23H2, Build: 22631.3737 (slightly earlier build) with NVDA 2024.3 Beta 1.
Two things I noted:
1) Visually, the correct word (KOCRUtil) is underlined.
2) Narrator reads the correct word as misspelt
@josephsl @seanbudd @Qchristensen Would you please take a look at this? NVDA has issues With Notepad's spell-checking capability which has been recently introduced. Moreover, with many languages other than English - Persian for instance, NVDA has become rather slow to respond in Notepad unless one disables spell-checking.
@Qchristensen @josephsl @seanbudd Just tested this with JAWS 2024, and it's not affected. So JAWS reads misspelled words where they are placed not at the beginning of lines.
@seanbudd @Qchristensen @Adriani90 @gerald-hartig I just updated to Windows 11 24H2, using Microsoft WindowsNotepad version 11.2406.9.0, and the issue persists.
Hi @amirsol81 thanks for updating the issue with more information. It has already been triaged and prioritised appropriately. If you feel it has been incorrectly prioritised please let us know by commenting on this issue. There is no need to further escalate the issue with NV Access staff or the volunteer developer community. Please refer to NV Access policy on triage: https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority
@gerald-hartig Thanks for the clarification. But the issue at hand isn't triaging per se. Rather, the issue is what happens to all of these labels and triages as time goes by - take issue #141 for instance: almost all screen readers other than NVDA provide this.
Hi,
I think it would be best to update the issue to state that this happens in Windows 11 Notepad in general.
Also, I think there was an issue that was related to this where I think I mya have stated that this requires changes to UIA text info implementation for Notepad (I think someone was investigating this a few weeks ago).
Thanks.
@josephsl The point is that the issue affects newer Notepad releases in Win 11 23H2 and, of course, in 24H2. As older releases aren't affected, I tried to make it more specific.
Hi,
It can also affect 22H2 as well - so it is not tied to Windows 11 release, but rather to Notepad versions (remember that Notepad is updated from the Microsoft Store in Windows 11).
Thanks.
Ah thanks, I wasn't taking into account 22H2. So I'll update it.
Steps to reproduce:
Actual behavior:
As the first line gains focus, NVDA incorrectly says: "spelling error Attempts to use KOCRUtil were sometimes failing 30 days after that program was first used. This was because it was incorrectly behaving as " So, upon pressing Up/Down, NVDA incorrectly announces the phrase, "spelling error," before reading the line as if the first word were misspelled. As such, misspelled words aren't properly identified, unlike what happens in Microsoft Word and edit boxes in browsers.
Expected behavior:
NVDA should properly say: "Attempts to use spelling error KOCRUtil were sometimes failing 30 days after that program was first used. This was because it was incorrectly behaving as " So the phrase "spelling error" should be announced right before the misspelled word.
NVDA logs, crash dumps and other attachments:
System configuration
NVDA installed/portable/running from source:
Installed.
NVDA version:
alpha-32767, and many recent alphas.
Windows version:
Windows 11, Version 23H2 (OS Build 22631.3810)
Name and version of other software in use when reproducing the issue:
Microsoft Windows Notepad 11.2405.13.0
Other information about your system:
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've tried many older alphas over the past couple of months, but all exhibit the same issue.
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?
Haven't tried.