Confirmed users
321
edits
JoystickAPI: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 29: | Line 29: | ||
** Across multiple devices this is insanity | ** Across multiple devices this is insanity | ||
** Should try to expose enough info to let content handle this, Kevin Gadd has an "Input Device API" that is higher-level and might be a good fit here. | ** Should try to expose enough info to let content handle this, Kevin Gadd has an "Input Device API" that is higher-level and might be a good fit here. | ||
= Discussion = | |||
* Pages will want instantaneous state of device, we might as well expose it (may alleviate polling concerns as well) | |||
** Expose a joyState property on each event, content can hold on to that object and it will update live as input happens | |||
* Not sure about mapping various devices to a sane set of controls | |||
** Going to try exposing a device ID for testing, collect some data and see what it looks like | |||
** Probably a fingerprinting concern, may not want to ship this | |||
** How much do we push to content vs. try to handle in the browser? | |||
** We'll get new try builds and put up a web page to gather data from users with various devices | |||
* Need timestamps per event (using milliseconds like requestAnimationFrame) | |||
* sicking is going to schedule a security review to get some more people thinking about it | |||