A mouse button does not respond
First checks
Reconnect the mouse, try another USB port, then verify every physical button produces a browser event.
Start with the symptom
Choose what is going wrong, run a focused browser test, and use the result to decide whether to check settings, connections, or the device itself.
17
Common symptoms
6
Device groups
Local
Data handling
17 matching symptoms
First checks
Reconnect the mouse, try another USB port, then verify every physical button produces a browser event.
First checks
Compare repeated click intervals and check whether unintended rapid clicks continue after lowering the operating-system double-click speed.
First checks
Clean around the wheel, disable smooth-scroll extensions, and compare the direction and size of consecutive wheel events.
First checks
Draw several slow paths and look for broken trails before changing pointer speed, surface, or wireless connection.
First checks
Compare simple pointer movement with held press-and-drag trails so you can tell whether the browser is losing the drag state or the trackpad is missing movement entirely.
First checks
Change the active keyboard layout if needed, disable remapping software, and verify keydown and keyup events across the layout.
First checks
Test one key at a time and compare rapid repeated presses while ignoring the browser's normal held-key auto-repeat.
First checks
Reconnect or pair the controller, press a button after loading the page, and confirm that the browser exposes a Gamepad API device.
First checks
Leave both sticks untouched and compare raw axis values with the 0.10 dead zone before recalibrating or cleaning the controller.
First checks
Clean the panel gently, enter full screen, and inspect the same position against several solid colors.
First checks
Disable night-light and adaptive display features, use neutral room lighting, then compare solid colors and gradients.
First checks
Remove gloves or a problematic protector, clean the panel, and trace every grid cell and corner with one or more fingers.
First checks
Check the physical mute control, select the intended input, allow browser permission, and watch for a live level change.
First checks
Check mute and volume, reconnect the output, confirm the operating-system output device, then play a browser test tone.
First checks
Check cable orientation and balance settings, then play isolated left and right tones before changing drivers or wiring.
First checks
Close other camera apps, allow site and operating-system camera access, then reload and select the intended device.
First checks
Clean the lens, improve front lighting, disable virtual cameras, and inspect the negotiated resolution and frame rate.
Reproduce the problem in the focused test without changing several settings at once.
Repeat after one controlled change, such as another port, browser permission, cable, or device selection.
Compare the result on another browser or computer before deciding that the hardware is faulty.
A browser can observe input events, media streams, and rendered test patterns, but it cannot inspect internal electronics, firmware, every driver setting, or physical damage. A failed test is evidence for further isolation, not a final hardware diagnosis. Stop using equipment that is hot, swollen, wet, sparking, or physically damaged.