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
fix: window menu should handle keys correctly #21434
Conversation
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.
LGTM for the patch given regression caused.
Date: Thu, 4 Oct 2018 14:57:02 -0700 | ||
Subject: fix: add back virtual methods in AccessiblePaneView | ||
|
||
Mark SetPaneFocus and RemovePaneFocus as virtual in AccessiblePaneView, as we |
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.
Can you open the CL to chromium and add that CL to this patch so that we can more easily follow/track this patch to ensure it's deleted in future?
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.
Submitted https://crrev.com/c/1959189.
Release Notes Persisted
|
I have automatically backported this PR to "8-x-y", please check out #21452 |
I have automatically backported this PR to "7-1-x", please check out #21453 |
Description of Change
Fix a few weird behaviors and crashes when controlling window menu by keys, for example:
This was caused by Chromium removing a few virtual methods. I have added the
virtual
s back, and I'll try to upstream the patch.Checklist
npm test
passesRelease Notes
Notes: Fix a weird behaviors and crashes when controlling window menu by keys.