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 without Ctrl and Cmd 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 without Ctrl and Cmd.
Do you think this is a good idea: add a option to disable error sound but menu accelerator won't work without Cmd and Ctrl. And should it be default?
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
keyDownback again with several workaround. But I think we should not handle any accelerator withoutCtrlandCmdthis 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 withoutCtrlandCmd.Do you think this is a good idea: add a option to disable error sound but menu accelerator won't work without
CmdandCtrl. And should it be default?