Re: [w3c/gamepad] Make gamepads accessible by web worker (#37)

kvnloo left a comment (w3c/gamepad#37)

Chromium's new raw-input path strengthens the worker use case here.

The browser process already detects gamepad changes on its polling thread and transports `GamepadRawInputChanged` through Mojo. Chromium also records telemetry for the end-to-end delay from the gamepad timestamp to dispatch of `gamepadrawinputchanged`.

The remaining main-thread dependency is therefore relatively late in the pipeline.

A worker experiment could measure the same timestamp→handler latency on Window vs Worker and quantify exactly how much main-thread contention worker exposure eliminates.


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

Message ID: <w3c/gamepad/issues/37/5941893591@github.com>