What is my browser?

A developer needs enough to reproduce the bug on the same setup: the browser and its full version, the operating system and its version, the device type, the screen size and the browser window size. For layout bugs add the device pixel ratio and the zoom level; for date, time and number bugs add the language and time zone; for anything that differs between users add the cookie, privacy and accessibility settings.

The bug report format here puts the key facts in a short table and folds the rest away in a details block, which GitHub, GitLab and Azure DevOps render as a collapsed section. The JSON format includes every value and the raw client hints, for attaching to automated reports.

Chromium browsers now report their version as 141.0.0.0 in the user agent, whatever the real build. The full version, such as 141.0.7390.108, only comes through User-Agent Client Hints, which this page reads where the browser supports them. A fix released in one build and not another is invisible if the report only says the major version.

The same applies to the browser name. Microsoft Edge, Opera, Brave, Vivaldi and Samsung Internet are all built on Chromium, and several of them say "Chrome" in their user agent. Rendering is usually identical, but extensions, built-in blockers and feature flags are not, so record the real browser.

Many bugs only appear under one setting. Dark mode, reduced motion, increased contrast and Windows high contrast mode change how pages render; Do Not Track and Global Privacy Control change what consent banners and analytics do; blocked cookies or storage break sign-in. The touch and pointer values show whether the device has a mouse, a touch screen or both, which decides whether hover menus can be used at all.

Capturing all of this at the moment the bug is seen saves the round trip of asking the person who reported it, often days later, on a device they may no longer have to hand.