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... JeromeReceived on Friday, 14 October 2011 22:11:59 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:50:27 UTC