Report a possible error
A useful report identifies the affected URL or case ID, the exact statement or behavior in question, reproducible conditions, and any primary source that conflicts with the current page.
Review sequence
- Record the affected page, reported issue, date received, and available reproduction details.
- Reproduce the issue before changing the conclusion. If the current claim is unreliable, mark the content for review while preserving the existing evidence.
- Update the fixture, assertion, source interpretation, or explanatory text needed to address the cause.
- Run the required browser and viewport matrix under a new evidence run ID.
- Review the new manifests and screenshots, update the page's real review date, and record a material change in the changelog.
What counts as a material correction
Material corrections include an incorrect root cause, a fix that does not produce the claimed result, unsupported browser coverage, misleading accessibility guidance, a broken experiment, or a privacy statement that no longer matches deployed behavior. Spelling and formatting changes do not receive a false new review date.
Evidence is not overwritten
Earlier evidence runs remain separate historical records. Replacement measurements use a new run ID and disclose the browser versions, environment, viewport, assertions, and fixture version actually tested.
Security and private data
Reports must not include passwords, session tokens, private account data, or unnecessary personal information. The project does not need access to a production account to reproduce the responsive-layout fixtures published here.