You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
From @dtapuska on March 29, 2017 14:4
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.
Copied from original issue: garykac/system-keyboard-lock#13
The text was updated successfully, but these errors were encountered: