Edge Chromium: NVDA does not turn back to browse mode after closing the context menu

[Adriani90]

Steps to reproduce:

1. Open MS Edge Chromium 83
2. With NVDA running, open the context menu on any element
3. Press escape

Actual behavior:

NVDA does not turn back to browse mode. You have to press tab once or to switch the window back and forth to make browse mode work again.

Expected behavior:

NVDA should turn back to browse mode after pressing escape.

System configuration

NVDA installed/portable/running from source:

Installed

NVDA version:

alpha-20220,1c4519a6

Windows version:

Windows 10 1909 Update

Name and version of other software in use when reproducing the issue:

Edge Chromium 83

Other information about your system:

It might be related, another issue is when opening the context menu and pressing down arrow, NVDA does not report the element focused but it works again after pressing arrow keys multiple times.

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.

2020.1, same issue. First occurance in Edge 83.

If addons are disabled, is your problem still occuring?

yes

Did you try to run the COM registry fixing tool in NVDA menu / tools?

yes, no effect.

[Adriani90]

This might need an external fix, so would be very appreciated if someone can also open a coresponding bug on Edge Chromium and post the link here.

If this is a Chromium issue in general, maybe @aleventhal can assist in this regard as well. Thanks.

[Adriani90]

@kypflug here is a contributor to the NVDA project, we are tracking in this NVDA repository some Edge Chromium issues regarding accessibility. Some of them require external fix from you guys, like for example this one. Is there an accessibility engineer for MS Edge Chromium who should be marked on such issues to make the Edge team aware of accessibility issues?
NVDA users often just create issues with NVDA repository when they are impacted rather than going directly to the feedback hub or to chromium bug tracker, so it would be more agile to mark someone of you here and then we can discuss if it requires an external fix or if NVDA should solve the issue.

Thank you!