Bendik Aagaard Lynghaug
2422f5fb49
Deploy / deploy (push) Successful in 34s
The container-rect approach (reading .hero-canvas's rendered rect via ResizeObserver) still jumped on the real device: .hero-copy kept sliding down as the address bar collapsed even with svh (then lvh) driving .hero-yes's height, meaning the box's actual rendered height wasn't holding still the way the "stable" viewport units are spec'd to. Reading a rect only helps if what it reads is actually fixed - it wasn't, so no amount of matching the canvas to it would help. yes.js now writes the fix instead of reading around it: it measures window.innerWidth/innerHeight once and sets that literal px height as an inline style on the hero element. Inline style beats the stylesheet's `height: 100svh` in the cascade, so the box's rendered height becomes a fixed number in the DOM rather than something recomputed from a viewport unit on every layout - nothing the browser does with svh afterward can move it. The old width-gated resize listener comes back to re-freeze on a genuine resize (orientation change), since that's still the correct signal for "the address-bar animation is not what's happening right now."