Opt-in
The phone peek switch.
Phones get cols = 1, so the design fills the screen exactly and a
horizontally-scrolling card deck shows no sign that it scrolls.
sqr-peek shrinks the solve slightly so the edge of the next card
stays visible.
<html> <!-- peek off (default) -->
<html class="sqr-peek"> <!-- peek on, factor 0.89 -->
<html class="sqr-peek" data-sqr-peek="0.85"> <!-- peek on, factor 0.85 -->
The factor is clamped to 0.5 … 1.0 and falls back to
0.89 on anything unparseable. It applies to phones only — the
multiplication sits inside the cols == 1 branch, so it is inert on
tablet and desktop. A mutation observer on <html> re-solves when
you toggle it, so you can flip it live in the console — and
window.squareRootResolve(), the one function the script puts on
window, forces a solve yourself. Give it about a second; the solve is
asynchronous.
document.documentElement.classList.toggle('sqr-peek');
document.documentElement.dataset.sqrPeek = '0.85';
window.squareRootResolve();
What peek costs you
With peek on, the canonical width is no longer the viewport width
— the headline invariant of the framework, broken deliberately.
sqr-w-6 stops being full-bleed and renders at about 89% of the
screen, and so does every full-width element built on the canon. A background
band, an edge-to-edge image or a sticky footer will leave a bare strip on one
side. That strip is the feature; it is also the thing that will surprise you.
What still holds: every ratio between units is preserved, and the design is
uniformly scaled rather than reflowed. Nothing re-wraps and no breakpoint fires.
Watch the small end though — at 360px with peek on the finger unit measures
53.4px, and at 320px it measures 47.5px. Still inside the cited touch band, but
that is the floor.
Use peek on a card deck. Leave it off on a full-bleed page.