New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: drop unresponsive suppressor for menus #35498
Conversation
Wanna ensure we don't reintroduce #2947 |
I tested this PR on Windows 10 and was unable to reproduce #2947. |
cc @zcbenz in case there's anything I missed—this code has a long heritage! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The menu popup loop still runs on UI thread, #20114 didn't change that. But code had been added to allow nested tasks in menu popup loop so the unresponsive problem may have been solved by it.
I think we should still do testing on macOS.
@@ -156,7 +155,6 @@ | |||
base::mac::ScopedSendingEvent sendingEventScoper; | |||
|
|||
// Don't emit unresponsive event when showing menu. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This can be removed too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See #35507
I did test on macOS and wasn't able to cause an unresponsive event to happen by showing a menu. |
mac test failures are flake; merging. |
No Release Notes |
Description of Change
This no longer seems to be necessary since #20114 moved the menu popup loop off
the UI thread.
Checklist
npm test
passesRelease Notes
Notes: none