Why Do Touch and Hover Signals Differ?

A website can switch to touch-sized controls, hide hover menus, or report that touch support disagrees with the pointer type it detects. These results come from several browser signals rather than one “touchscreen” flag. Check the signals together before changing the profile.

Separate capability signals from actual input

Websites commonly compare four kinds of information:

• navigator.maxTouchPoints reports the maximum number of simultaneous touch contacts the browser says it supports.
• CSS pointer and hover media queries describe the primary pointing device.
• CSS any-pointer and any-hover describe the combined capabilities of all available pointing devices.
• PointerEvent.pointerType describes the input that produced a particular event, such as mouse, pen, or touch.

These values do not have to describe only one device. A touch-capable laptop with a mouse or trackpad can legitimately have a precise, hover-capable primary pointer while any-pointer also reports a coarse touch input. An actual mouse click can still produce pointerType: "mouse" in that environment.

Understand the two input-device choices

MaskPilot provides Desktop device and Hybrid device under More environment options → Input devices:

• Desktop device is for a mouse- or trackpad-led workflow. On a compatible desktop host, the browser reports no touch contacts and exposes a precise, hover-capable pointer profile.
• Hybrid device is for a touch-capable computer that also has a mouse or trackpad. It keeps the supported host touch-point count and exposes both coarse and precise capabilities through the any-* queries, while the primary pointer remains precise and hover-capable.

The setting coordinates the browser’s touch, pointer, and hover capability signals. It does not install a touchscreen, turn mouse clicks into touch events, or rewrite the pointerType of real input. MaskPilot therefore does not offer a touch-only choice that would continue producing mouse events while claiming that no precise pointer exists.

If the host cannot support the corresponding capability set, the browser keeps its native input capabilities instead of claiming input that cannot occur. Use Hybrid device only when the computer and real workflow are actually hybrid.

Check one profile after a full restart

1. In the affected profile, record the page address, browser version, visible layout, and whether you used a mouse, pen, or touchscreen.
2. If the site provides a diagnostic, record maxTouchPoints plus the pointer, hover, any-pointer, and any-hover results from the same page load. Do not combine results from different profiles or test tools.
3. Fully close the profile and wait until its status becomes available.
4. Edit the same profile, open More environment options, and check Input devices.
5. Choose Desktop device for a mouse/trackpad-only workflow, or Hybrid device for a touch-capable computer that also uses a precise pointer.
6. Save only that change, relaunch the same profile, reload the same page, and repeat the observation once without editing anything.

Input-device settings are read when the browser process starts. If the old result remains after a complete relaunch, follow why profile settings did not apply before changing another field.

Interpret common combinations

• Zero touch points with a precise, hover-capable pointer: this is the expected desktop pattern.
• Touch points present, primary pointer precise, and both coarse and precise available: this can be a valid hybrid pattern; the primary and combined-capability queries answer different questions.
• A touch-oriented layout while actual clicks still report mouse input: capability queries can affect layout, while each event still reports the input that produced it.
• Values change only during an automated or emulated run: the automation or debugging layer may be overriding device capabilities. Repeat the check with the same profile outside that override before editing MaskPilot.
• A site expects touch-only behavior: changing the user agent, viewport size, or screen resolution does not create touch hardware or touch events.

Do not inject page scripts to replace only maxTouchPoints. A one-field override can disagree with CSS media queries and actual events. Also avoid changing screen, media-device, language, and browser-version settings in the same test; those settings describe different surfaces and make the result harder to attribute.

Verify the real workflow, not only a checker

A site can cache a layout choice or make its own assumptions from several signals. If the diagnostic values are stable but the interface still looks wrong, test the actual menu, drag, scroll, or gesture that matters. Use a test profile rather than clearing production site data just to force a new layout decision.

For the wider configuration lifecycle, see configure a stable browser fingerprint. MDN defines navigator.maxTouchPoints as the maximum supported simultaneous touch contacts. The W3C Media Queries Level 5 specification distinguishes primary pointer and hover capabilities from the combined any-pointer and any-hover capabilities.