NVDA and Windows 10 Start Menu: reporting typed text after closing the menu #7370
Labels
p4
https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority
Milestone
Comments
|
CC @michaelDCurran, looks like something odd is going on with our suggestions list item handler.
From: fisher729 [mailto:notifications@github.com]
Sent: Monday, July 10, 2017 9:13 AM
To: nvaccess/nvda <nvda@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: [nvaccess/nvda] NVDA and Windows 10 Start Menu: reporting typed text after closing the menu (#7370)
This is a long standing issue with NVDA.
1. Open the Windows 10 Start menu.
2. Type in the name of an app/program like' Notepad'. If you type 'Note' for example, that should be sufficient, and I recommend that because the issue would become easier to spot.
3. Press Enter. The menu will close and something happens before Notepad starts.
Expected: NVDA just keeps quiet and Notepad starts.
Actual: NVDA says Note, Notepad etc. (whatever you typed) then starts the program as expected.
I have noticed this with:
NVDA as far back as 2015.3 to the latest Next snapshot.
Windows 10 as far back as 15240 to 15063.413 and still going.
Speak typed characters and words both on and off. It doesn't matter.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#7370> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AHgLkCiVGD-b9bYSHduVK9rC92NpSnz2ks5sMk2SgaJpZM4OTEqJ> .
|
|
Actually, this is due to the enter key handler used to read automatically inserted text on the next line; e.g. automatic numbering in Word. It can be fixed by setting announceNewLineText to False for the search field. P3 because it's superfluous but otherwise harmless, but should be fairly easy to fix. |
jcsteh
added
the
p4
|
Hi Andre, do you know other places where this should be handled? Let me know so a PR can be submitted tomorrow. Thanks.
From: James Teh [mailto:notifications@github.com]
Sent: Monday, July 10, 2017 5:20 PM
To: nvaccess/nvda <nvda@noreply.github.com>
Cc: Joseph Lee <joseph.lee22590@gmail.com>; Comment <comment@noreply.github.com>
Subject: Re: [nvaccess/nvda] NVDA and Windows 10 Start Menu: reporting typed text after closing the menu (#7370)
Actually, this is due to the enter key handler used to read automatically inserted text on the next line; e.g. automatic numbering in Word. It can be fixed by setting announceNewLineText to False for the search field.
P3 because it's superfluous but otherwise harmless, but should be fairly easy to fix.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#7370 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AHgLkOeRJ7sqimfVjF5dUeMPM5JhPyulks5sMr-fgaJpZM4OTEqJ> .
|
|
No. not at this time. The start menu is the only one that stands out now.
…On 7/10/17, Joseph Lee ***@***.***> wrote:
Hi Andre, do you know other places where this should be handled? Let me know
so a PR can be submitted tomorrow. Thanks.
From: James Teh ***@***.***
Sent: Monday, July 10, 2017 5:20 PM
To: nvaccess/nvda ***@***.***>
Cc: Joseph Lee ***@***.***>; Comment
***@***.***>
Subject: Re: [nvaccess/nvda] NVDA and Windows 10 Start Menu: reporting typed
text after closing the menu (#7370)
Actually, this is due to the enter key handler used to read automatically
inserted text on the next line; e.g. automatic numbering in Word. It can be
fixed by setting announceNewLineText to False for the search field.
P3 because it's superfluous but otherwise harmless, but should be fairly
easy to fix.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#7370 (comment)> , or
mute the thread
<https://github.com/notifications/unsubscribe-auth/AHgLkOeRJ7sqimfVjF5dUeMPM5JhPyulks5sMr-fgaJpZM4OTEqJ>
.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#7370 (comment)
|
josephsl
added a commit
to josephsl/nvda
that referenced
this issue
Jul 11, 2017
…tart menu) is closing. re nvaccess#7370. due to use of announceNewlineText, when start menu closes and when Enter is pressed, search field value will be announced, which sometimes leads to side effects such as core freeze. Address this through initOverClass in UIA.SearchField that turns this flag off if and only if we're in start menu in Windows 10.
josephsl
added a commit
to josephsl/nvda
that referenced
this issue
Jul 11, 2017
…at disables announcement of newline text. re nvaccess#7370. Reviewed by Mick Curran (NV Access): better to create an overlay class for this just for searchui. This also allows easy modifications in the future if the need arises.
michaelDCurran
pushed a commit
that referenced
this issue
Jul 25, 2017
… NVDA announcing search field text. re #7370. (#7375) * UIA/Search field: do not announce search field entry when searchui (start menu) is closing. re #7370. due to use of announceNewlineText, when start menu closes and when Enter is pressed, search field value will be announced, which sometimes leads to side effects such as core freeze. Address this through initOverClass in UIA.SearchField that turns this flag off if and only if we're in start menu in Windows 10. * SearchField/searchui: an overlay class just for Start menu version that disables announcement of newline text. re #7370. Reviewed by Mick Curran (NV Access): better to create an overlay class for this just for searchui. This also allows easy modifications in the future if the need arises.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a long standing issue with NVDA.
Expected: NVDA just keeps quiet and Notepad starts.
Actual: NVDA says Note, Notepad etc. (whatever you typed) then starts the program as expected.
I have noticed this with:
NVDA as far back as 2015.3 to the latest Next snapshot.
Windows 10 as far back as 15240 to 15063.413 and still going.
Speak typed characters and words both on and off. It doesn't matter.
The text was updated successfully, but these errors were encountered: