Open LeonarddeR opened 7 years ago
Agree that not being able to silence those is a bug, however, they do I think? visually show up.
I don't consider it a bug, when I plug headphones into my system on the windows lock screen I see a notification. Why shouldn't NVDA make you aware of this information?
it's more that I can't tell NVDA to shut up after it starts going blah blah blah.
@feerrenrut: Do you also see this notification when you are at a logon prompt? Note that on the Windows 10 lock screen itself still talks with the user instance. The problem applies to toast notification spoken by the user instance when the system instance has foreground.
Ah, I tested this again. The messages are shown visually on the lock screen, but not at the logon prompt. I understand what you mean about not being able to silence the messages as well, you can actually get NVDA talking twice which is pretty confusing to deal with. We should try to match the visual behaviour, speak the messages when on the lock screen, but not when on the logon prompt.
I'm going to try to clarify the title and description of this issue a little bit.
Sorry for being a bit vague here.
I still belief this can be generalised to silencing toast messages, not specifically when on the logon screen, but in general when sleep mode is on. Note that API messages also come through while sleep mode is on.
Yes, thanks @leonardder. The technical details are appreciated. Just trying to keep the main description / title as user facing as possible. I have the (perhaps flawed) understanding that sleep mode was supposed to be per application? Either way, it does not change the fundamental request in this issue. It may mean that silencing the user instance of NVDA should not be done using sleep mode.
It seems this occurs also for speech sent through controller client, not only for toast notificatoins. See also #2163.
Steps to reproduce:
win+L
to go to the lock screenesc
to go to the logon screenExpected behavior:
NVDA should not announce the message.
Actual behavior:
NVDA speaks the incoming toast messages and you are unable to silence these messages. There are actually two instances of NVDA running one user instance, and one system instance. These two instances can be made to talk at the same time, which is quite confusing.
System configuration:
NVDA next-14463,7dca66c4, Windows 10 creators update