Steps to reproduce
Melanie Richards <firstname.lastname@example.org
UI / App name:
Web Platform (EdgeHTML)
Does not meet MAS requirement:
If a web developer provides a custom context menu, the user can’t get access to that custom context menu when invoking it via touch Narrator.
Must be followed on a touch device.
Turn on Narrator.
in Microsoft Edge. This is an example where the page scripts are intercepting the default contextmenu with an alert.
Tab to move focus to the “Focus me…” element.
Double tap on the screen, within the web document, with two fingers.
User gets the generic context menu.
Right click on the element or (making sure that focus is still on the element) hit Shift + F10.
User gets an alert intercepting the generic context menu: “Successfully intercepted context menu!”
Provide work-around, if any:
User can get the web dev’s custom context menu using Shift + F10.
Mitigating circumstances, if any:
Regression from past release:
Not a regression
This is feature-level work requiring a major refactor of a primary platform pipeline and would be addressed via
. There is a high risk of introducing other accessibility bugs. Due to resourcing realities for the amount of work involved, this cannot be addressed in the current release.
ETA to fix:
- Open any web site in Edge
- Subscribe to contextmenu event: document.addEventListener('contextmenu’, ()=>console.log(‘context’));3. Start narrator (Ctrl+Win+Enter)
- Double-tap with two fingers on the document
Expected: the contextmenu event fired
Actual: nothing happens
Comments and activity
- Microsoft Edge Team
Changed Assigned To to “Kamen M.”
Changed Assigned To to “Bogdan B.”
Changed Assigned To to “David F.”
Changed Assigned To from “David F.” to “Anton V.”
Changed Assigned To from “Anton V.” to “Bogdan B.”
Changed Assigned To from “Bogdan B.” to “Rossen A.”
Changed Status to “Confirmed”
Changed Steps to Reproduce