Press each side button separately in the test area. Note which row signals a press and a release before changing any settings.
Follow the signal
- Both rows update. The browser receives Back and Forward as standard mouse buttons. In the game, clear any conflicting bindings and bind them again in the current profile.
- Another action happens. Check the active per-app profile in Logitech Options+, G HUB, or Razer Synapse as applicable. Restore the default Back and Forward assignments temporarily. A button mapped to a key or macro may no longer send a mouse-button event.
- One row stays blank. Compare the same physical button in another browser and on a second computer with default mappings. Keep the pointer in the test area so the page can observe the input.
Check whether a game accepts side buttons in menus and gameplay separately. A game can ignore a valid input when a chat box is focused or when a binding is unset. More than two thumb buttons may require assigning keyboard shortcuts in vendor software.
Use the full Mouse Button Test for the event log. If unrelated buttons also fail, work through the hardware versus software guide.