-
-
Notifications
You must be signed in to change notification settings - Fork 283
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
Best approch to disable key error sound #799
Comments
Here are some uninformed suggestions that were probably already considered/tried: A
B
CSomething with DPut webview inside a subview inside the contentview, if that's any different from what was done before which removed resize/cursor events. EOverride the webview's keydown handler itself The missing events were the only functional issue with the subview approach, right? Did you figure out why exactly the events didn't work with that setup? |
Yeah I have tried above but they all have something doesn't work. Like The approach before #798 also have issues that accelerators without |
Is Electron's usage of |
I think I might've actually managed to fix it 🤞 |
After #798, we remove all keyDown implementations. Because key events on macOS is too messy, it's not worth it to implement our own. This will bring back beep sound when pressing key.
The error sound will fire when the view doesn't handle it, eg. there's no menu accelerator for it, or users are not typing in the textarea. To remove it, we can offer a config to add
keyDown
back again with several workaround. But I think we should not handle any accelerator withoutCtrl
andCmd
this time. Because the key event chain is totally different without them, and I have struggled to satisfy every scenarios. See this slides for more information. Official Apple apps seem to follow this convention too. They don't have acceleartors withoutCtrl
andCmd
.Do you think this is a good idea: add a option to disable error sound but menu accelerator won't work without
Cmd
andCtrl
. And should it be default?The text was updated successfully, but these errors were encountered: