- From: Boaz Sender <boaz@bocoup.com>
- Date: Fri, 14 Oct 2011 18:48:43 -0400
- To: Jerome Etienne <jerome.etienne@gmail.com>
- Cc: public-games@w3.org
- Message-ID: <CAHx3KheKVUBOGjd+Qpi_PuPLijWrLck7uLvBCnGbyAsNAPFm=A@mail.gmail.com>
Thanks Jerome! Great idea. The issue that always comes up with requests like this is identity security/fingerprinting. What I think will probably have to happen, based on my conversations with browser vendors, is that we will need to recommend a good user interface for allowing permission to information like this, and a good programming interface for requesting it and getting it back in an abstract way so the details of the hardware/peripherals can't be logged. We'll definitely put this topic on the agenda for the forthcoming summit. -Boaz -- Boaz Sender http://bocoup.com | 1-617-379-2752 355 Congress St, Boston MA, 02210 On Oct 14, 2011 6:12 PM, "Jerome Etienne" <jerome.etienne@gmail.com> wrote: > Hello, > > First, i love the initiative. Just an idea i havent seen in > http://www.w3.org/2011/09/games > > * expose keyboard layout > * use case: the users uses AWSD keys to move the player. > * issue: it works on qwerty, but not with others keyboard layout > * current workaround: ask the player to configure the keys, before > playing for the first time. not too user friendly > * example: on azerty, it should be QZSD keys > > * expose the keys i can receive in a webpage > * use case: the webpage cant know which keys may be trigger a dom events > * example: it isn't possible to receive ctrl+f on most browser as it > intercepted by the browser for search > * example: it isn't possible to receive cmd+esc on macos as it is > intercepted by the os for front-row > * It makes keys binding quite hard in practice. it requires to test all > browser/os combinations.... > > Jerome >
Received on Friday, 14 October 2011 22:49:11 UTC