Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NVDA and notification text repeating multiple times #7128

Closed
fisher729 opened this issue May 2, 2017 · 15 comments
Closed

NVDA and notification text repeating multiple times #7128

fisher729 opened this issue May 2, 2017 · 15 comments
Assignees
Labels

Comments

@fisher729
Copy link

@fisher729 fisher729 commented May 2, 2017

Hello.

I am running the Creator's Update with NVDA 2017.1. Sometimes, the text of a Windows Notification, such as Autoplay etc. repeats more than once. This happens sometimes when I am in and out of the start menu.

@josephsl
Copy link
Collaborator

@josephsl josephsl commented May 2, 2017

@k-kolev1985
Copy link

@k-kolev1985 k-kolev1985 commented May 2, 2017

Yes, I've noticed this as well, specially if I'm in an UWP app (e.g. Edge). I'm running NVDA version next-14006,9031bf7a and Windows 10 Creators Update.

@feerrenrut
Copy link
Contributor

@feerrenrut feerrenrut commented May 2, 2017

Can you please outline the steps you use to reproduce this?

@feerrenrut feerrenrut added the bug label May 2, 2017
@fisher729
Copy link
Author

@fisher729 fisher729 commented May 2, 2017

@derekriemer
Copy link
Collaborator

@derekriemer derekriemer commented May 2, 2017

@tayarndt
Copy link

@tayarndt tayarndt commented May 2, 2017

Hello, i notice this issue also it does it with many different types of things like dropbox and outlook just to name a few.

@josephsl
Copy link
Collaborator

@josephsl josephsl commented Jun 6, 2017

Hi,

Tracking events (with a modified WinTenApps add-on) shows that, somehow, UIA window opened event is fired multiple times when viewed from NVDA side of things but accevent says it was fired only once.

To those affected by this: can we try with NVDA 2016.4 and 2017.1 to see if we can isolate this further? Thanks.

@jcsteh
Copy link
Contributor

@jcsteh jcsteh commented Jun 6, 2017

@josephsl
Copy link
Collaborator

@josephsl josephsl commented Jun 6, 2017

@tayarndt
Copy link

@tayarndt tayarndt commented Jun 6, 2017

@fisher729
Copy link
Author

@fisher729 fisher729 commented Jul 10, 2017

Hello. Any updates on this? It is affecting many more users now, since a lot more persons are now on the Creator's update. Any idea when this will be fixed? I turned off reporting help balloons because of this issue, but would love to turn it back on.

@jcsteh
Copy link
Contributor

@jcsteh jcsteh commented Jul 11, 2017

We believe this to be a bug in UI Automation Core, but we'll be stuck with it for a while even if Microsoft eventually fix it, so p2 to work around it in NVDA.

@josephsl
Copy link
Collaborator

@josephsl josephsl commented Jul 11, 2017

@michaelDCurran
Copy link
Contributor

@michaelDCurran michaelDCurran commented Jul 11, 2017

josephsl added a commit to josephsl/nvda that referenced this issue Jul 11, 2017
…lt last toast message to make sure it is different, caused by possible problem in uIA Core in Creators Update and later. re nvaccess#7128.

According to mick Curran (NV Access), UIA Core may have bugs when it comes to firing multiple toast events after using UWP's for a while, so detect this by consulting last toast message if the build is 15063 or later. This does not affect older releases such as Anniversary Update (build 14393).
michaelDCurran added a commit that referenced this issue Jul 25, 2017
…lt last toast message in case a repeat event was fired. re #7128 (#7376)

* UIA/ToastWin10/build 15063 and later: before announcing toasts, consult last toast message to make sure it is different, caused by possible problem in uIA Core in Creators Update and later. re #7128.

According to mick Curran (NV Access), UIA Core may have bugs when it comes to firing multiple toast events after using UWP's for a while, so detect this by consulting last toast message if the build is 15063 or later. This does not affect older releases such as Anniversary Update (build 14393).

* Duplicate toasts: check runtime ID and time instead of name.

Reviewed by Mick Curran (NV Access): check runtime ID and timestamp instead of name alone. However, in latest Windows Insider build (1623x), toasts have same runtime ID, so both this and timestamp must be checked (leave the event if runtime ID's are the same and timestamps are less than a second apart).

* ToastWin10: typo (toastTimestamt -> toastTimestamp).

Caught by Mick Curran (NV Access): toastTimestamt -> toastTimestamp (thanks).
@michaelDCurran
Copy link
Contributor

@michaelDCurran michaelDCurran commented Jul 25, 2017

Fixed in PR #7376

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
8 participants
You can’t perform that action at this time.