Quick answer
What this guide helps you determine
Review common capability and display values while understanding reduced user agents and fingerprinting risk.
Begin with the observable browser result, repeat it under the same conditions, and change one connection, setting or application at a time. A browser result narrows likely causes but does not certify hardware or decide a repair.
Scope of this check
Browsers expose capabilities and layout context such as viewport, screen values, language, timezone, touch points and supported APIs. They increasingly reduce exact hardware and user-agent detail to limit fingerprinting, so these values should not be presented as a guaranteed retail model identity.
Step-by-step method
- Review each value with its source: screen and viewport are layout context, feature flags show API presence, and language/timezone reflect preferences. Permission may reveal media device labels, but the site should not combine them into a persistent identifier.
- Resize the window, change zoom or move between displays to see which values are contextual. Compare another browser to observe intentional generalization rather than assuming one is wrong.
- When sharing support information, include only the fields needed to reproduce the issue—usually browser family, OS family, page URL and visible result. Omit full user agents, device labels and other identifiers unless a trusted support process specifically needs them.
What to check first
Use these checkpoints to keep the comparison focused. Record the visible behavior rather than assigning a fault label too early.
- Capability detection is different from identity
- Device labels require permission in many browsers
- A responsible tool does not combine values into an identifier
How to read what you see
| Observation | What it can suggest | Useful next check |
|---|---|---|
| Viewport changes with the window | It describes page layout, not hardware identity. | Use it for responsive troubleshooting. |
| Browser or model label is generic | Privacy reduction or user-agent generalization is active. | Rely on feature detection. |
| A feature exists but an operation fails | Permission, secure context or connected hardware still matters. | Read the specific runtime error. |
Common mistakes to avoid
- Do not claim exact model detection from generalized browser values.
- Do not assemble a fingerprint for convenience.
- Do not share more diagnostic fields than the support task requires.
Build evidence another person can use
Write down the exact action, visible result and whether it repeats. Include the browser family, operating-system family, connection type and the single comparison that changed the result. Quote the observation directly—for example, “Viewport changes with the window”—then add where it occurred and which comparison changed it.
Change one condition per comparison and return settings that have no effect. Follow model-specific manufacturer instructions before firmware changes, cleaning, disassembly or warranty action.
When to seek qualified support
If the same problem remains in multiple applications and on another compatible connection or computer, collect the repeatable observations and contact the manufacturer or a qualified technician. Stop using equipment that is physically damaged, unusually hot, wet, sparking or unsafe. Device Test Bench cannot inspect electrical condition or make a repair decision.
Privacy during testing
Our public tests process key events, pointer values, media streams and controller input locally. Do not send private recordings, complete typed text or device identifiers when asking for help. A short description of the behavior, browser and page URL is normally enough.
Questions readers ask
Can a browser read my serial number?
Ordinary web pages generally do not receive hardware serial numbers; browser-exposed values are intentionally limited.
Why do two devices show the same browser information?
Modern user agents can be reduced or standardized, and capability profiles are shared by many devices.
Primary technical references
The following specifications define the browser APIs discussed in this guide. They are primary web-platform references, not product repair manuals.