Skip to content
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

BUGFIX: directly register event-listener for ctrl-k #40

Merged
merged 2 commits into from Mar 15, 2023

Conversation

PRGfx
Copy link
Contributor

@PRGfx PRGfx commented Mar 15, 2023

I removed the registration of the ctrl+k hotkey for Neos completely and added the event-handler directly analogous to the module-ui.

Sadly it doesn't seem possible to prevent the default-behavior with the neos-ui hotkey-handling, as neither the event is passed to the handler nor a return value could be set from the handler:
https://github.com/neos/neos-ui/blob/a0683ed157699042aa269ea0819977efafb5be46/packages/neos-ui-sagas/src/UI/Hotkeys/index.js#L14-L16

This PR does not contain a build to avoid conflicts, but I can add it, if preferred.

As this is a browser-hotkey on Windows and Linux, we need to prevent the
default-handling of the event, but the neos-ui doesn't provide a way to
configure hotkeys like that.
@Sebobo Sebobo self-requested a review March 15, 2023 13:57
Copy link
Owner

@Sebobo Sebobo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we remove both hotkeys we can also remove the filter in the settings.

Configuration/Settings.Neos.yaml Outdated Show resolved Hide resolved
@Sebobo Sebobo merged commit 0f9776a into Sebobo:main Mar 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants