Mouse button remap test for buttons 4 and 5

Check whether a physical mouse button reaches the expected browser event and spot driver or profile remapping without installing software.

Start the mouse test

Check whether a physical button reaches the expected event

Choose the button you intend to test, then press it while your pointer is over this page. A different browser button code can reveal a driver or profile remap.

Mapping mismatches0

Expected browser button

Press the selected physical buttonWaiting for inputYour browser will report the button code it receives.

Expected button 0Matches 0Mismatches 0

Recent browser button codes—

Browser events cannot identify buttons handled entirely by vendor software

How to check mouse button 4 and 5 remapping

Select the physical button you intend to test, press it over the test area and compare the received code with the expected one. A driver can intentionally map a side button to another browser button or keep it as a macro that the page cannot see.

Run the same sequence after switching profiles, disabling remapping software and trying a second browser. This isolates a browser-visible mapping issue from a dead switch or an input that is reserved by the operating system.

Can a browser identify mouse buttons 4 and 5?

A browser can identify standard button events that reach the page: left, middle, right, back and forward. Buttons handled entirely by vendor software, macros or DPI profiles may never produce a browser event.

What does a mismatch in the mouse remap test mean?

A mismatch means the page received a different browser button code than the one you selected. Check your mouse profile or driver, then repeat the test in a second browser before treating it as a hardware fault.