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

Spec seems to describe an implementation #13

Closed
dtapuska opened this issue Mar 29, 2017 · 2 comments
Closed

Spec seems to describe an implementation #13

dtapuska opened this issue Mar 29, 2017 · 2 comments

Comments

@dtapuska
Copy link

When reading:
https://garykac.github.io/system-keyboard-lock/#key-press-handler

It seems that the "system key press handler" is describing an implementation. An alternate implementation is that you could just have a table and know that the registered document/navigator has priority over executing the UA default action for these events.

It isn't clear to me that you need to hook the system listeners in order to implement this.

@jamiewalch
Copy link
Collaborator

The system hook is needed for keyboard shortcuts that the browser would not otherwise receive; Alt+Tab is the canonical example we've been using for that. Other keys could be handled either by the same hook or by the regular input processing pipeline, at the discretion of the UA.

@garykac
Copy link
Owner

garykac commented Apr 26, 2017

This issue was moved to WICG/keyboard-lock#13

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

No branches or pull requests

3 participants