Guide: inspect browser capabilities and environment
Compatibility bugs hinge on user agent, viewport, locale, cookies, WebGL, approximate memory, and experimental APIs. Asking users to open `about:` pages does not scale — one panel speeds support triage.
Data comes from public browser APIs (`navigator`, `screen`, feature detection) with no report sent to WebDevTools. Attach the summary to bug tickets with exact session context.
Use for Safari iOS, Android PWA, or third-party blocking issues. Copy the summary to Slack or Jira before requesting more screenshots.
Step by step
- Open the tool page — The panel auto-loads user agent, platform, resolution, and preferred language.
- Review supported features — Check WebP, service workers, localStorage, hardware hints — gaps explain silent failures.
- Compare to expected environment — Cross-check analytics: corporate WebViews often disable APIs.
- Copy the report — Paste into support tickets or repro PRs — no passwords or tokens.