Fix context menu focus for Edge downloads#15300
Conversation
See test results for failed build of commit 5da41e4e78 |
|
Hello all. |
|
Hi, For me that fix worked. |
|
@Carlos-EstebanM Thanks for reporting this. Here it works as expected. Could you please ensure the following?
If this doesn't work, please provide a log as follows:
|
|
@LeonarddeR I also don't seem to be having success with this. That said, I'm not an Edge user, normally, so perhaps I'm doing it wrong. |
|
It looks like in your case the window class is Chrome_WidgetWin_1, not Chrome_WidgetWin_2. I changed the code to support all incarnations of Chrome_WidgetWin_* |
|
It works for me with the latest commit. like @carlos, I also have an instance with the 'Chrome_WidgetWin_1' class. It also fixed the Folder menu in the add or edit favorite dialog as I expected. So far so good. Thanks @LeonarddeR for such a quick turnaround. |
|
Hi, |
|
Apologies but this is much too late for a beta at this point. Unless another serious regression is found, we don't plan on releasing another beta. |
|
But I think this bug seriously affects the experience of NVDA users. This is a bug specific to NVDA and Edge. |
|
Since Microsoft Edge is the pre-installed browser of Windows 10 and 11, this problem may affect many users, and the scenarios involved are also critical. I really hope to consider fixing it in time in this version |
|
@seanbudd Given the volume of complaints and users effected, and given how long
this has been an outstanding issue (long before the first beta): as you're not
inclined to do another beta cycle to include this, would a 2023.2.1 be possible?
Though I would think a third beta would be easier, and less confusing to the
users.
For myself I don't care, as I don't use Edge more than once a quarter, but users
really want this fix, if mailing list traffic and number of issues about Edge
context menus are any measure.
|
|
It seems that a bad merge from master occurred - there are a lot of unrelated changes in the diff |
|
ah - I see it was a merge from beta - can this be rebased on master instead? |
I don't think there's consensus yet about whether this has to go to 2023.2, 2023.3 or a potential 2023.2.1 😉 |
|
Hi @seanbudd
Based on the above, I think community users are suffering from this bug, can you reconsider giving this fix to beta branch? Thanks |
|
Hello. I personally use nvda and edge. I am one of those suffering from this problem. I would like this to be released as soon as possible. I have many friends who use microsoft edge and this problem is quite annoying. |
In my opinion, a bug like this even deserves a hotfix. It affects multiple areas in the default browser. It can fully block at least 1 use case, in this case allowing the download of unsigned executables that are blocked by Windows defender. Users shouldn't wait an entire quarter or be forced to use development builds or install an add-on to get around an issue that blocks functionality in the default browser. |
|
@seanbudd |
Note, created against beta because this issue can be pretty annoying and it is a relatively small fix with a major positive impact for Edge users.
Link to issue number:
Fixes #14916
Summary of the issue:
When opening the context menu from the Edge downloads window, NVDA doesn't reflect this.
Description of user facing changes
Context menu is read again.
Description of development approach
UIAHandler.getNearestWindowHandlereturns when a cached window handle couldn't be fetched from an UIAElement due to a COMError.Testing strategy:
Tested that the context menu of a download item in Edge reads again.
Known issues with pull request:
The first item in the menu is read twice. I've tried to fix this without success. It looks like our duplicate focus event logic doesn't kick in properly. Note that Edge firing duplicate events is a bug on their end anyway.
Change log entries:
Bug fixes
Code Review Checklist: