Unable to use Visual Studio with NVDA: NVDA continuously keeps on reading whole window content #14086
Comments
This comment was marked as outdated.
This comment was marked as outdated.
|
No, I may have to retract my comment because I had a problem with this in the WPF form designer, NVDA kept reporting "default". Below is the log: |
|
Have you checked "Selective UIA" checkbox from advance settings?
…On 8/30/2022 6:30 PM, Rowen wrote:
I did not reproduce this.
*
NVDA Version: alpha-26412,28b47560 (2022.4.0.26412)
*
Microsoft Visual Studio Community 2022 Version 17.3.2
—
Reply to this email directly, view it on GitHub
<#14086 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABQWBMZOOQ326OXA7EARXUTV3YAWDANCNFSM6AAAAAAQACCDWM>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Yup
…On 8/30/2022 7:06 PM, Rowen wrote:
No, I may have to retract my comment because I had a problem with this
in the WPF form designer, NVDA kept reporting "default".
and the issue appeared in alpha-26387,
Check the following configurations in the NVDA Advanced Settings
panel: Registration for UI Automation events and property changes:
Automatic (prefer selectively)
Below is the log:
nvda-alpha-26387.txt
<https://github.com/nvaccess/nvda/files/9453253/nvda-alpha-26387.txt>
—
Reply to this email directly, view it on GitHub
<#14086 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABQWBM253ZAQUEOK4IRPKMDV3YE5PANCNFSM6AAAAAAQACCDWM>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Hi, Looks like an event flood to me. Can you try:
Note that I cannot reproduce this from VS startup screen (the one described in the original comment (I'm using alpha.26412 myself). Since my UIA item status event handler could be involved, I'll keep an eye on this issue. Thanks. |
|
@josephsl sure, I'll come back with the results |
|
I suspect that it only happens if we choose "global" from UI Automation Registration combobox |
|
Yes, it is an event flud. |
|
When i choose "automatically" it will happen |
|
Hi, note that selective registration is the default in Windows 11 Version 22H2 (build 22621) and later. It may not be enough to create an app module level variable to control this behavior as UIA handler thread must be restarted for changes to take effect. Thanks.
|
|
@josephsl |
|
@cary-rowen yes, with me too, if I choose automatically, it starts happening. |
Yes. CC @rperez030. |
|
@codeofdusk Thanks for CCIng @rperez030 |
|
@feerrenrut As of now, the only workaround to bypass this issue is to select "Selectively" from "Registration for UI Automation events and property changes" |
This is default on SV2+, see #14018. If #14080 is indeed the cause, maybe it could be restricted to SV2+ as well? |
|
@feerrenrut in my opinion we should approach Microsoft and make then understand that how severe event fludding is. they should take it on priority |
|
@codeofdusk Actually with me it happens if I choose "Automatic (Selective preferred" option. I think that it still prefers global registration |
|
@akash07k What do the following lines in the NVDA Python console return on your system? import UIAHandler
UIAHandler.utils._shouldSelectivelyRegister() |
|
Has this been reported to Microsoft yet? |
michaelDCurran
added
the
blocked/needs-technical-investigation
Not to my knowledge (unless @akash07k filed), but I'll see if I can flag it internally. |
|
Thanks for looping me in. @codeofdusk have you been able to reproduce the issue. I cannot. I'm running the latest build from the preview channel and manually set selective registration to global. @akash07k would you mind sharing the log showing that flood of events? You can send it to robertoperez@microsoft.com if you don't want to post it here. We are currently investigating what may be a related issue, and that would be very helpful in resolving this. |
|
Definitely, Can we connect on teams for more in depth discussion on this?
If you agree, then I'll connect with you on Monday in your timezone.
…On 9/10/2022 12:56 AM, Roberto Perez wrote:
Thanks for looping me in. @codeofdusk <https://github.com/codeofdusk>
have you been able to reproduce the issue. I cannot. I'm running the
latest build from the preview channel and manually set selective
registration to global. @akash07k <https://github.com/akash07k> would
you mind sharing the log showing that flood of events? You can send it
to ***@***.*** if you don't want to post it here. We
are currently investigating what may be a related issue, and that
would be very helpful in resolving this.
—
Reply to this email directly, view it on GitHub
<#14086 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABQWBM2TMWEM2Q4CYJFFZILV5OFM3ANCNFSM6AAAAAAQACCDWM>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Ok, let's connect on Monday. I am in US eastern time. |
|
Hi,
|
|
Hi, @josephsl
Below is the log attachment, it has no privacy and I don't care: |
|
I think that @akash07k and @cary-rowen might be talking about different things. |
|
Hi, preferably with Event Tracker add-on installed as it can track and record UIA item status event (perhaps limiting item status handling to current focus may solve parts of what’s happening. Thanks.
|
|
Hi @josephsl |
|
Hi, based on Event Tracker log, it appears UIA item status events are accompanied by name change events. The reason NVDA says “default” is because that is item status text UIA reports (ultimately, coming from what Visual Studio (UIA server) tells UIA to report to clients such as NVDA). If item status variant issue is not resolved by switching to selective UIA event registration, then it would be better to restrict item status to focused element unless there are cases where item status should be handled from places other than focused control. At the same time, since it is really up to UIA server (Visual Studio) to communicate things about item status to NVDA and other clients, I think it would be best to keep the communication channel going between users, NV Access and contributors, and Visual Studio team inside Microsoft (of course keep in mind that Narrator can give us a good set of data points to compare event handling and such). Thanks.
|
|
@michaelDCurran I'll generate the logs, |
|
@akash07k @cary-rowen does this PR build from #14136, fix your respective issues? @cary-rowen - I expect this PR to resolve the problem you describe |
|
看上去，您提供的构建并没有解决我提到的问题。 |
|
@cary-rowen Is this extra info being spoken only happening in alphas, or has this always occurred? Right now we are only concerned with a regression in alpha which could be holding back 2022.4. |
|
Hi, @michaelDCurran |
|
That's... quite odd. Maybe we should add VS to the |
…atus property event (#14080)" (#14136) This reverts commit a4644ef. This reverts commit a4644ef. Link to issue number: reverts #14080 re-opens #13973 Summary of the issue: Based on discussion in #14086 (comment), it appears that #14080 makes the behaviour worse when using WPF projects in VS. Description of user facing changes #13973 is now an issue again Description of development approach reverts #14080
|
After making the following settings in the NVDA Advanced Settings panel: "Global" or "Automatic (prefer selective)" NVDA's speech lag more than five seconds in WPF project in VS2022. |
@cary-rowen Is this lag also observed in NVDA 2022.3? |
|
@codeofdusk |
This is expected behaviour (see #11002). Selective UIA registration is now enabled by default as of NVDA 2022.4+ on Windows SV2+. Given that the original issue reported here was fixed in PR #14136 and there are no further regressions, I recommend closing this issue. |
|
Hi, to clarify: Windows SV2 = Windows 11 Version 22H2 (build 22621). Thanks,
|
|
But another thing I've observed is that I can also reproduce this huge speech lag by checking "Automatic (prefer selective" in the advanced settings panel. |
Yes if running on a Windows version below SV2.
The "automatic" option is global on Win10 due to bugs with task manager and emoji panel. |
|
But to clarify, NVDA 2022.2also would show this lag in VS right? I.e.
this lag has not been introduced into NVDA knowingly but then only
mitigated on Windows 11 22h2 with selective registration?
If I understand correctly, we've known about this lag for a long time.
We want to switch to UIA selective registration by default everywhere,
but we simply cannot on versions less Windows 11 22h2 as it would cause
missing information.
If on the other hand we've introduced something after 2022.2 which makes
this lag worse (where we can't do selective registration) then this is a
much more serious issue.
Is this your understanding @@codeofdusk and @josephsl?
Do we still think changes to UIA textChange event may play into this
at all?
|
Yes, I'd think so.
To my knowledge.
Correct. |
|
@akash07k - We're closing this as we believe this is resolved, please correct us if this is not the case and we will reopen the issue |
|
Sure,
I'll let you know once I test again
…On 9/15/2022 10:49 AM, Sean Budd wrote:
@akash07k <https://github.com/akash07k> - We're closing this as we
believe this is resolved, please correct us if this is not the case
and we will reopen the issue
—
Reply to this email directly, view it on GitHub
<#14086 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABQWBMYM3E7UZSL7RF3GSELV6KWVZANCNFSM6AAAAAAQACCDWM>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
I've chosen "Selectively" from the drop down and hence it returns: "true"
…On 9/4/2022 8:19 AM, Bill Dengler wrote:
@akash07k <https://github.com/akash07k> What do the following lines in
the NVDA Python console return on your system?
import UIAHandler
UIAHandler.utils._shouldSelectivelyRegister()
—
Reply to this email directly, view it on GitHub
<#14086 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABQWBM2YSRAVVZAQBMYHIBDV4QE3HANCNFSM6AAAAAAQACCDWM>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@akash07k - to be clear, is this still an issue with NVDA alpha? |
Steps to reproduce:
Actual behavior:
NVDA continuously keeps on announcing whole window content inside Visual Studio and we are unable to use it since the announcement doesn't get interrupt even if we manually navigate.
seems that this issue is started appearing after merging these PRs:
#14067
#14080
Speech output below:
Expected behavior:
NVDA shouldn't read whole window content automatically
NVDA logs, crash dumps and other attachments:
Please check attached recording too
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
NVDA version alpha-26412,28b47560
Windows version:
Windows 11 (10.0.25188.0)
Name and version of other software in use when reproducing the issue:
Visual Studio 2022
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.
It was fine with previous versions
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?
Yes
2022-08-30.11-37-47.mp4
The text was updated successfully, but these errors were encountered: