Re: [w3c/gamepad] It is unclear if the algorithm for gamepadconnected event matches implementations (Issue #215)

kvnloo left a comment (w3c/gamepad#215)

Chromium's new raw-input event path makes this more important to specify.

`GamepadService` only forwards raw-input changes to consumers that are both active and have observed a user gesture. We should test visibility/focus transitions explicitly so a page doesn't receive a stale burst of queued raw events when it becomes active again.

For realtime input, "latest state on resume" is likely more useful than replaying old motion.


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/gamepad/issues/215#issuecomment-5941897840
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/gamepad/issues/215/5941897840@github.com>