System baselines for browser compatibility tests

A browser feature works on one computer but fails on another, or the same test gives different results after an update. Without a baseline, it is hard to tell whether the cause is the browser, the device, a permission or a setting.

Record the conditions before you compare results. TooLab’s Browser Info and System Info show useful details in your browser, so you can repeat the check after a change and see what is different.

Build a browser compatibility baseline

1. Open Browser Info in the browser you plan to test. Note its version and engine, then record the permissions, codecs or supported features that matter to your test.
2. Open System Info. Record the processor, graphics, screen and any battery or network details that could affect the feature. The information a browser can see varies by device and browser, so write down what is shown rather than filling in missing values by guesswork.
3. Note the environment that the tools do not capture for you: operating system and version, browser profile, extensions, page zoom, whether you are on a laptop or desktop, and any connected display or accessory. On Windows 11, find the operating system details at Settings › System › About. On a Mac, use Apple menu › About This Mac.
4. Run the same compatibility test and write down the exact action and result. For example, record which page or feature you tested, what you clicked, what happened and whether an error appeared. Take a screenshot if the result is visual.

Keep the notes together with the date and time. A short record is more useful than a long list of details you cannot repeat. If you plan to compare a second browser or device, keep the test page and steps the same.

What the baseline tells you

The browser version or engine differs

The browsers may use different rendering or web-feature implementations. A browser engine is the software that handles page layout and web features. Record both the browser name and engine when Browser Info reports them, because the browser name alone may not explain a difference.

A needed feature is not listed as supported

This points to a browser or device capability gap. A feature may be missing, disabled or unavailable in that browser environment. Check the same feature in the browser’s own settings and retest after an update, but do not assume that a newer version will support every feature.

The feature is listed, but the test still fails

A supported-feature report does not guarantee that a particular website or app will use the feature successfully. Permissions, extensions, privacy settings, a driver or the page’s own code can still block it. Treat the support report as one clue, then follow the same steps again while checking those conditions.

System details differ between runs

The comparison may include a changed device or setup, not just a browser change. Check whether you switched displays, connected a dock, changed power state or opened the test on another computer. For network-dependent tests, note whether you changed from Wi-Fi to Ethernet or moved to another network.

How to investigate a mismatch

1. Repeat the exact test. Reload the same page, use the same steps and record the result again. A one-time failure may come from a temporary loading problem rather than a compatibility issue.
2. Check the page permission. Click the site information icon next to the address bar and check the permission needed for the test, such as camera or microphone access. Reload the page after changing it. The permission prompts and controls vary by browser.
3. Check the operating system permission. For a camera or microphone test, Windows 11 has controls at Settings › Privacy & security › Camera or Settings › Privacy & security › Microphone. On macOS, check System Settings › Privacy & Security › Camera or System Settings › Privacy & Security › Microphone. Allow the browser if it is listed, then test again.
4. Try a clean browser profile. Open a new profile without extensions and repeat the same test. If it works there, re-enable extensions one at a time to find a possible conflict. Keep the original profile details in your baseline.
5. Compare the browser version. Check whether the browser updated between tests. If it did, record the new version and run the same case again. Change one thing at a time so you can tell which change affected the result.
6. Test another browser or device. Keep the test steps identical. If one browser fails on one device while another succeeds, the pattern narrows the cause, but it does not by itself identify a defective component.

Keep comparisons useful

Do not update the browser, change permissions, switch displays and disable extensions all at once. Make one change, run the test, and update the notes. This simple sequence makes it easier to connect a changed result to the condition that changed.

Also record the limits of the information. Browser reports can expose only what the browser allows a page to see. For example, a browser gets a rounded hint about RAM size, not an exact memory capacity. A blank or simplified field does not necessarily mean the hardware is missing or faulty.

Store the baseline with the test steps, and remove account names or other private details before sharing screenshots with support.