Start with the symptom

Device Troubleshooting: Find the Right Hardware Test

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

Mouse & trackpad

A mouse button does not respond

First checks

Reconnect the mouse, try another USB port, then verify every physical button produces a browser event.

Mouse & trackpad

A single click becomes a double-click

First checks

Compare repeated click intervals and check whether unintended rapid clicks continue after lowering the operating-system double-click speed.

Mouse & trackpad

The wheel skips or scrolls the wrong way

First checks

Clean around the wheel, disable smooth-scroll extensions, and compare the direction and size of consecutive wheel events.

Mouse & trackpad

Dragging drops, stutters, or jumps

First checks

Draw several slow paths and look for broken trails before changing pointer speed, surface, or wireless connection.

Mouse & trackpad

Trackpad drag releases too early

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.

Keyboard

Some keyboard keys do not work

First checks

Change the active keyboard layout if needed, disable remapping software, and verify keydown and keyup events across the layout.

Keyboard

A key types twice or repeats unexpectedly

First checks

Test one key at a time and compare rapid repeated presses while ignoring the browser's normal held-key auto-repeat.

Display & touch

The screen has a fixed bright or dark dot

First checks

Clean the panel gently, enter full screen, and inspect the same position against several solid colors.

Audio

The microphone has no input

First checks

Check the physical mute control, select the intended input, allow browser permission, and watch for a live level change.

Audio

Speakers or headphones have no sound

First checks

Check mute and volume, reconnect the output, confirm the operating-system output device, then play a browser test tone.

Audio

Left and right audio channels are reversed

First checks

Check cable orientation and balance settings, then play isolated left and right tones before changing drivers or wiring.

Camera

The camera will not open in the browser

First checks

Close other camera apps, allow site and operating-system camera access, then reload and select the intended device.

Camera

The camera image is blurry or low quality

First checks

Clean the lens, improve front lighting, disable virtual cameras, and inspect the negotiated resolution and frame rate.

Use the results in three steps

  1. 1

    Reproduce the problem in the focused test without changing several settings at once.

  2. 2

    Repeat after one controlled change, such as another port, browser permission, cable, or device selection.

  3. 3

    Compare the result on another browser or computer before deciding that the hardware is faulty.

What a browser test cannot prove

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.

No. Permissions, drivers, cables, wireless pairing, another application, and browser limitations can produce the same result. Repeat the test after isolating those factors.
The diagnostic interactions run in the browser. Camera and microphone access still requires explicit browser permission; review each tester's privacy guidance before starting.
Choose the closest device category and begin with its general tester. If the device is not exposed to the browser at all, check operating-system detection, connections, power, and drivers first.