← Back to Channels and integrationsOpenClaw browser
Mobile, responsive, and render QA
Mobile QA is not done because the DOM looks fine. It is done when the phone-width rendering is actually checked and the result is readable.
Mobile QA ruleUse phone-sized screenshots for layout truth. Snapshots alone are not enough for clipping or overflow claims.
Evidence types
What proves the mobile view actually works?
Viewport-sized screenshotBest for checking hero layout, headline wrapping, and obvious clipping.
Full-page screenshotBest for checking long-scroll issues, repeated overflow, or stacked-section spacing.
SnapshotUseful for action refs, but weaker than screenshots for visual QA.
Common failures
What usually breaks first on mobile?
Right-edge clippingUsually caused by oversized headings, min-width mistakes, or hidden overflow assumptions.
Broken stackingDesktop multi-column layouts may collapse badly if the mobile breakpoint rules are weak.
Dense unreadable spacingEven when nothing technically overflows, mobile can still fail if spacing and line length are bad.
Open deeper reference links for this page