Browser Monitor Tests: Straight Answers
Quick answers about fullscreen, saved history, HDR, refresh-rate readings, reaction timing, screenshots, photos, and defect reports.
Fullscreen did not open
The browser refused or could not complete the request. Fullscreen normally needs a direct click or key action, and browser permissions, embedded pages, or device policy can block it. Try the page's fullscreen button again, check the site permission, or continue in the largest available window. MDN documents the user-action and permission requirements in its Fullscreen API reference.
Saved history is missing
History is stored for this site in this browser on this device. It does not follow you to another browser or computer. Private sessions, storage restrictions, and clearing site data can remove it. Open Test History on the original device and export anything important instead of treating browser storage as the only copy.
The HDR page says the browser supports HDR
That is a capability signal, not proof that this page, a game, or a video is currently reaching the panel as HDR. The CSS dynamic-range feature can match when the browser and output device support a high range, even when that capability is not active. Confirm the operating-system HDR setting, the display's input mode, and the content itself. Use the HDR page for comparison, not peak-brightness or color-volume measurement.
The refresh-rate reading moves around
The page estimates browser animation cadence, so frame scheduling, system load, power mode, variable refresh, and tab visibility can affect the sample. Keep the test visible, stop heavy background work, and compare it with the selected rate in the operating system. A stable browser estimate is still not an external measurement of the panel's scan.
The reaction-time result looks high
Do not read it as monitor input lag. The trial includes your response, the mouse or keyboard, operating-system scheduling, browser event handling, rendering, and the display. Use the reaction-time page to compare the same person and setup after one change. Display-only latency needs a separate measurement method.
A screenshot does not show the defect
That is expected for a physical panel problem. A screenshot captures the image the computer rendered before the panel displayed it. Use a screenshot when the artifact also appears in the captured file; use a camera when the issue is a fixed pixel, edge light, reflection, flicker band, uniformity patch, or viewing-angle change.
The camera photo looks more dramatic than the screen
Automatic exposure, focus, shutter behavior, and image processing can exaggerate or hide what you saw. Keep the room condition and camera position consistent, avoid digital zoom when possible, and take both a close photo and a wider context photo. Treat the image as documentation, not a brightness or flicker measurement.
A useful defect report is specific
Include the exact model, purchase date, connection, resolution, picture mode, room condition, repeatable steps, physical screen location, and original photos. Add a serial or service identifier only when the company asks for it, and send it through that company's support channel—not a public post.
The defect report builder can organize the record. The seller or manufacturer still decides what evidence and policy apply.
Browser behavior references: Web Storage, requestAnimationFrame, and dynamic-range.
For the complete order of checks, use the monitor testing workflow.