You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
Microsoft Edge comes with Reading view, a way to reformat the current page for smooth reading. However, NVDA does not announce certain notifications about it, including on pages where this view is not supported. Investigation shows this is tied to notification event introduced in IUIA5.
Steps to reproduce:
Open Google with Edge.
Press Control+Shift+R to enable reading view.
Please also remember to attach a zip of any files required to reproduce the issue.
Expected behavior:
NVDA announces, "reading view is not available for this page".
Actual behavior:
No announcement.
System configuration:
NVDA next.15316 (installed), Windows 10 April 2018 Update.
Other questions:
Reproducible: yes.
Did restart help: no.
Technical details:
Certain notifications are sent via UiaRaiseNotificationEvent (see #7984 for details), and reading view announcement is one of them. At the moment NVDA checks to make sure focused control is part of the active application where the notification came from, but Edge uses at least two processes when run:
MicrosoftEdge.exe: main process.
MicrosoftEdgeCP.exe: content process.
Notifications are sent by the first process, thus failing the notification announcement criteria.
Solution:
The Edge app module (microsoftedge.py) will gain notification event handler that'll announce all messages. This was tested on Windows 10 App Essentials add-on and was successful.
Thanks.
The text was updated successfully, but these errors were encountered:
josephsl
added a commit
to josephsl/nvda
that referenced
this issue
Jun 20, 2018
…ng view availability. Re nvaccess#8423.
Certain notifications, including reading view availability are fired by main Edge process, not the content process. This means NvDA will ignore such notifications. Resolved by adding a dedicated app module for Edge main process that'll catch notifications and announce them, and propogate them no more.
…s#8423.
Reviewed by @leonardder: limit Edge notificaiton context to Edge only. This is done by checking to make sure focused element is indeed part of Edge, and if not, notifications will be silenced. This resolves an issue where Edge notifications are heard while using other apps.
…ng view availability (#8424)
* Edge: announce notifications fired by main Edge process such as reading view availability. Re #8423.
Certain notifications, including reading view availability are fired by main Edge process, not the content process. This means NvDA will ignore such notifications. Resolved by adding a dedicated app module for Edge main process that'll catch notifications and announce them, and propogate them no more.
* Edge: review actionn (limit notificaiton context to Edge). Re #8423.
Reviewed by @leonardder: limit Edge notificaiton context to Edge only. This is done by checking to make sure focused element is indeed part of Edge, and if not, notifications will be silenced. This resolves an issue where Edge notifications are heard while using other apps.
* Update what's new
Hi,
Microsoft Edge comes with Reading view, a way to reformat the current page for smooth reading. However, NVDA does not announce certain notifications about it, including on pages where this view is not supported. Investigation shows this is tied to notification event introduced in IUIA5.
Steps to reproduce:
Expected behavior:
NVDA announces, "reading view is not available for this page".
Actual behavior:
No announcement.
System configuration:
NVDA next.15316 (installed), Windows 10 April 2018 Update.
Other questions:
Reproducible: yes.
Did restart help: no.
Technical details:
Certain notifications are sent via UiaRaiseNotificationEvent (see #7984 for details), and reading view announcement is one of them. At the moment NVDA checks to make sure focused control is part of the active application where the notification came from, but Edge uses at least two processes when run:
Notifications are sent by the first process, thus failing the notification announcement criteria.
Solution:
The Edge app module (microsoftedge.py) will gain notification event handler that'll announce all messages. This was tested on Windows 10 App Essentials add-on and was successful.
Thanks.
The text was updated successfully, but these errors were encountered: