- From: Reilly Grant <notifications@github.com>
- Date: Fri, 26 Oct 2018 06:15:47 -0700
- To: w3c/gamepad <gamepad@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 26 October 2018 13:16:10 UTC
Chatted offline with @samuelweiler and we decided that the language in the spec was a convoluted way of saying that `timestamp` starts at `0` when the navigation is started. We agreed that this is not likely a vector for fingerprinting as each frame has a different zero-point. The question of events delivered to multiple browsing contexts is a separate issue. Given that this is a polling as well as event-driven interface we should consider both whether connect/disconnect events (as well as future button/axis events) are fired for a visible, but not foreground, frame and whether a page polling `navigator.gamepads` in the background observes changes. -- 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/gamepad/issues/74#issuecomment-433403518
Received on Friday, 26 October 2018 13:16:10 UTC