- From: Robat Williams <notifications@github.com>
- Date: Thu, 07 Mar 2019 11:07:17 -0800
- To: w3c/uievents <uievents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/uievents/issues/226@github.com>
When multiple keyboards are available, there is currently no way to distinguish which one a KeyboardEvent came from using web APIs. We should have one. Use case 1: special-purpose keyboards/keypads that are used alongside normal keyboards, for example financial [trading keypads](https://www.google.co.uk/search?q=trading+keypad&tbm=isch) and retail POS keyboards. They are used to provide quick access to regular/time-sensitive actions, while the normal full-sized keyboard is used for other input. The key codes they expose (as far as I know) are the same as for the normal keyboard (but the mappings can be programmed), so the listening application needs to use the source of the key event to determine what action to take. Use case 2 (similar): [gaming keyboards](https://www.google.co.uk/search?tbm=isch&q=gaming+keyboard+one+hand), if use of the main keyboard is also needed (otherwise the Keyboard Lock API seems like it would do the job). I started a discussion over at WICG Discourse: [Identify which of multiple keyboards an event came from](https://discourse.wicg.io/t/identify-which-of-multiple-keyboards-an-event-came-from/3416). Some of the ideas there would probably be within the scope of UI Events, but the more advanced ones would not. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/uievents/issues/226
Received on Thursday, 7 March 2019 19:07:38 UTC