Horizontal Scroll Test

deltaX

15-second horizontal input track

15s
1Tilt the wheel2Try Shift + wheel3Use a two-finger swipe
Status: Idle
Negative trace · deltaX < 0Positive trace · deltaX > 0No input · flat line
Send horizontal input inside this areaOnly this card contains motion during the test; the rest of the page remains scrollable.
deltaX events0
Calibrated side
Same / opposite
Σ |deltaX|0.0
Peak |deltaX|0.0
shiftKey0/0

Start the test and use the wheel inside the capture area.

This pattern cannot prove whether the source was a tilt wheel, trackpad, Shift remapping, or another device.

This is a browser-level observation, not a laboratory measurement or a definitive hardware diagnosis. Read the disclaimer.

See horizontal input without guessing its source

Browsers expose horizontal deltas but usually do not provide a dependable label for tilt wheels, trackpads, remapping software, or accessibility devices. This test keeps the observable value separate from the possible source.

How to use the Horizontal Scroll Test

Try one method

Begin with a tilt wheel, Shift plus wheel, or a two-finger horizontal gesture rather than mixing all three.

Start the quick run

Press Start and keep the pointer over the wide track while sending horizontal input for up to 15 seconds.

Check deltaX first

If only deltaY appears, the browser received vertical wheel input; try another supported method or application.

What deltaX means in a horizontal scroll test

`deltaX` is the horizontal component of a browser `WheelEvent`. A nonzero value indicates that the page received a sideways input component in the event’s declared `deltaMode`. The horizontal scroll test counts those events, sums their absolute magnitude, records a peak, and calibrates the first dominant sign as one side. The sign is a session-relative label because direction settings and application mappings can vary.

A large `deltaX` is not a physical travel distance. Pixel, line, and page modes use different units, and software can accelerate or smooth them. Compare raw values only within the same environment. The moving indicator is intentionally bounded so one extreme event cannot push the layout beyond the test card.

Tilt wheel, Shift mapping, and trackpad gestures

Some mice support a physical left or right tilt. Some operating systems and applications translate Shift plus vertical wheel input into horizontal movement. Touchpads can create two-dimensional deltas directly, sometimes including both axes in the same event. Any of these may produce `deltaX`, but the browser generally does not state which source was responsible, so a sideways scrolling test must not advertise device detection.

Use one method per run and note the `shiftKey` count. A Shift count supports the observation that the modifier was held; it does not prove that the browser or application mapped it horizontally. Likewise, zero Shift events with `deltaX` does not prove the presence of a tilt mechanism because a gesture or remapping layer may be involved.

When only vertical input appears

If the horizontal scroll test records `deltaY` but no `deltaX`, the browser is receiving vertical wheel input from your current action. Confirm that the pointer is inside the card and the run is active. Try a genuinely horizontal touchpad gesture, check whether your mouse supports tilt, or hold Shift while rotating the wheel if your operating system or application uses that convention.

Next compare a wide spreadsheet, timeline, or design canvas. Some applications implement their own Shift mapping even when a browser page does not. Review official device software for button or tilt assignments, and inspect application shortcuts. Do not install unknown remapping utilities solely to force a result.

Why horizontal behavior differs by application

Applications can cancel a wheel event, convert vertical deltas to horizontal movement, reserve gestures for navigation, or apply acceleration. Browser extensions and accessibility tools may also transform input. A page can receive `deltaX` without scrolling if there is no overflow or if script uses the event for another action. This is why the `wheel` event and the resulting `scroll` are related but not identical.

The capture card prevents its own accidental motion during the active horizontal scroll test, but no global listener is installed. Move the pointer outside the card and ordinary page scrolling remains available. This limited scope is both easier to understand and less likely to interfere with normal navigation.

Where sideways scrolling matters

Horizontal input can help with wide tables, audio or video timelines, design canvases, code editors, map interfaces, and image strips. The useful question is whether your intended action produces predictable motion in the target application. A consistent deltaX trace in this test provides one point of comparison, while application behavior confirms whether mapping and overflow work where you need them.

If one side never appears, repeat the same side with controlled movements, test another browser, check official assignments, and compare another computer if available. If neither side produces input anywhere, follow the troubleshooting guide. The horizontal scroll result remains an event observation rather than proof that a tilt switch exists or has failed.

Horizontal Scroll Test questions

Can this horizontal scroll test detect a tilt wheel?

It can detect deltaX events, but it cannot reliably identify whether they came from tilt hardware, a trackpad, Shift mapping, or other software.

Why does Shift plus wheel still show deltaY?

Shift mapping is application- and platform-dependent. The modifier may be present without the browser converting the delta axis.

Does the test block normal scrolling?

Only the capture card contains movement during the test. There is no document-level wheel listener, so input outside remains normal.

What are good deltaX values?

There is no universal scale. Use repeated values from the same device, mode, browser, and settings to judge consistency.

Continue your check