Pointer Event Inspector

View pointer type, ID, buttons, pressure, contact geometry, tilt, twist, timestamps, coalesced-event counts, and a copyable recent-event log locally in your browser.

Move, press, drag, touch, or use a pen here

Pointer data stays in this page.

—pointerType

—pointerId

—pressure

0coalesced events

0buttons

—contact width × height

—tilt X / Y

—twist

Recent PointerEvents

No pointer events yet.

Pointer Events unify mouse, pen, and touch at the browser API level. Hardware-specific fields are only shown when the browser/device exposes them; zeros can mean “not applicable” or “not reported.”

What the browser can measure

Start with a functional check, measure only what the browser can actually expose, then retest after one change.

ConnectChoose the actual browser-visible device or grant permission when required.

TestConfirm basic signal, input, output, preview or display behavior.

MeasureUse browser-exposed levels, timing, resolution, FPS, axes or event data.

DiagnoseCompare the symptom with the specific diagnostic instead of relying on one number.

RetestRepeat after changing the device, cable, permission, browser or system setting.

Pre-call Mic Webcam Keyboard Mouse Gamepad Display Permissions

Browser boundary
These tools observe browser APIs and local media/event streams. They cannot certify hardware condition, bypass denied permissions, or expose measurements the browser/OS does not provide.

Pointer-event session statistics

Summarize the recent PointerEvent log into pointer types, pressure range, tilt range and event frequency, then export the session evidence as CSV.

—Events

—Pointer types

—Pressure range

—Observed event rate

Generate PointerEvents in the main pad first.

Browser-local does not mean laboratory measurement

These pages can report Web API data such as events, stream settings, frame timing and audio samples. They do not certify hardware condition or bypass browser and operating-system limits.

PointerEvent fields are reported with support boundaries

Pressure, contact size, tilt, twist and coalesced events are browser-exposed fields. Zero or missing values are not treated as proof that the hardware lacks a capability.

Browser-observed input is not raw hardware telemetry

Pointer Event Inspector measures events after they have passed through the device firmware, operating system, browser, event loop, and page. Sampling rate, background load, power-saving behavior, accessibility settings, acceleration, browser coalescing, and display refresh can therefore influence what the page observes.

How to make the test more useful

Repeat the same action several times, close heavy background work, keep the browser focused, and compare patterns rather than treating one sample as a hardware specification. A missing event can indicate rollover or browser behavior without proving an electrical keyboard fault; timing variation can indicate scheduling noise without proving sensor jitter. For warranty, competitive-latency, or hardware diagnostics, confirm findings with the device vendor’s tools or a lower-level measurement method.