v149 · Origin Trial · Device

Input Frequency Meter

High-frequency gamepads report input far faster than requestAnimationFrame fires. This meter compares how many events per second arrive via the new event-driven path versus the polling path — making the sub-frame resolution visible as data.

Connect a gamepad. Plug in a USB or Bluetooth gamepad and press any button to activate it. The event-driven path (rawgamepadinputchange) requires Chrome 149+ with the Gamepad origin trial or flag enabled. Polling always works as the baseline.
No gamepad connected. Connect one and press any button.
Event-driven (rawgamepadinputchange) 0 Hz
0total events
0peak Hz
0avg Hz
Polling (requestAnimationFrame) 0 Hz
0total polls
0peak Hz
0avg Hz
Event/poll ratio:  ·  Events per frame:  ·  Sub-frame inputs:

what the numbers mean

A 60Hz display gives you 60 poll opportunities per second. A high-frequency gamepad at 120Hz sends 120 input events per second. If the event/poll ratio is 2×, the event-driven path captured twice as much input fidelity. Sub-frame inputs are events that arrived between two consecutive animation frames — those are the presses the polling path missed entirely.

see also

implementation reference

Need the exact API surface, compatibility boundaries, errors, lifecycle, and source links? Read the matching gendn reference ↗