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
Regression: Invisible menu items no longer work via their accelerator keys #12025
Comments
👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can. To help make it easier for us to investigate your issue, please follow the contributing guidelines. |
@stephenmartindale what platform was this on? |
It was Windows 10.0.16299, x64.
…On 1 April 2018 at 06:05, Shelley Vohr ***@***.***> wrote:
@stephenmartindale <https://github.com/stephenmartindale> what platform
was this on?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#12025 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGEzYQQhkaJ_8OlVimCdhpRdglG7ARuKks5tkFIHgaJpZM4SQ82m>
.
|
I can also reproduce this on Windows |
FYI: I tested this on |
i can take a look at this next week! |
@stephenmartindale verdict is that this happened as a result of some separator filtering i implemented; i'll see if i can open a PR to remedy this side effect. |
With Electron
1.8
, it was possible to create an invisible menu item in the application menu and, assuming it was still enabled, it could be invoked via its accelerator key. This provided a mechanism for creating application-wide shortcut keys that were independent from content.For example, this menu-item template worked just fine:
Since upgrading to
Electron2.0.0-beta.1
, this no longer works. Instead, I have to make the menu item visible and give it a name in order for it to be triggered by its accelerator key:Is this just a regression or is this by design? If it is by design, is there any way to achieve window-level shortcut keys without resorting to nasty
keydown
andkeyup
handlers on the content level?The text was updated successfully, but these errors were encountered: