Mouse Side Button Test

A mouse side button test listens for browser mouse transitions inside a defined surface. It displays the numeric `button` value that changed, a cautious label for commonly used codes, the currently pressed codes, total events, and a recent event timeline. Separate down and up entries help show whether the browser received a complete interaction rather than only one edge of the sequence.

The browser standard defines common primary, auxiliary, and secondary values, while extra controls are exposed through additional codes when the platform passes them through. Many environments use code 3 for Back and code 4 for Forward, often marketed as mouse buttons 4 and 5. That association is useful for display, but it is not a guarantee about physical placement or user configuration.

A mouse button 4 test may show a Back-like code on one system and a different logical action on another. Vendor software can assign media keys, macros, keyboard shortcuts, middle click, or disabled behavior. Gaming profiles may switch when an executable gains focus. Operating-system utilities and accessibility tools can transform an auxiliary press before the browser receives it.

Browsers also reserve some side-button activity for history navigation, and a remote desktop or virtual machine can translate it again. The mouse button 5 test therefore reports the final browser-visible code and phase, not the original firmware report. When a mapping differs, record the active profile and compare a second application before changing settings.

A normal mouse back button can immediately leave the page, which would erase an in-memory sample. After you explicitly start the tool, the test surface calls the available event-cancellation mechanism for extra button codes. The prevention applies only inside that surface. Ordinary links, keyboard shortcuts, and controls outside it continue to use normal browser behavior.

Containment is best effort rather than a promise. Some browser, operating-system, extension, or driver combinations can act before page script receives a cancelable event. Save work in other tabs before testing, keep the pointer centered in the target, and avoid rapid presses until you know how the environment behaves. A navigation despite containment is a compatibility observation, not evidence of faulty hardware.

Latest button code identifies the most recent logical control. Typical mapping translates common values into readable labels while retaining words such as ‘typical’ so remapping is not hidden. Down state lists controls that have sent a press without a matching release. Event count includes both phases, while the Back and Forward press metrics count only down transitions to avoid doubling one physical action.

A down state that remains after you release deserves a repeat, but it does not prove a stuck physical button. The window may have lost focus, navigation may have occurred, an extension may have intercepted the release, or the pointer path may differ by browser. Reset the mouse side button test, make slower isolated presses, and see whether the same incomplete sequence recurs.

Use the mouse back button test when browser history navigation has stopped, goes the wrong way, or occurs twice. Use the mouse forward button test when the front control has been remapped by a game or productivity profile. Developers can check whether an interface should respond to auxiliary input without assuming that every user owns the same button layout.

For support work, test the rear control five times, reset, then test the front control five times. Keep the device profile, browser, and connection fixed. Next compare the general mouse test, which shows left, middle, right, wheel, and side activity together. If the side code appears there but the target application ignores it, investigate that application’s shortcut handling first.

Confirm that the explicit test state is active. Check official mouse software for disabled controls, per-application profiles, onboard memory, and macro assignments. Reconnect the device or receiver, verify battery condition, and try a supported wired mode if available. Test a clean browser window or another browser to rule out an extension or history gesture conflict.

If the expected auxiliary event never reaches any application, try the mouse on another computer or use manufacturer diagnostics. Avoid untrusted driver-download sites and preserve any profile before resetting it. A browser page cannot determine whether missing input comes from a physical switch, firmware, wireless transport, a driver, an operating-system reservation, or application mapping.

The timeline stays in browser memory and is bounded so extended testing cannot grow indefinitely. The tool does not need screen coordinates, a device serial number, or a server upload to display button codes. An optional saved result contains only summary counts and observed code labels on the current browser profile.

No side-button result is a hardware certificate. A received code establishes that the browser observed a logical event in this session; it does not confirm physical construction or future reliability. Repeat the mouse side button test in the software where the control matters, and treat any difference as evidence about the input path rather than a verdict about the mouse.