feat: an unsealing wave for the boot splash #22
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/unsealing-loader"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Boot loading moment, framed as ritual rather than apology. Designed via
/grilling.Grain.
noise.gif755,823 → 40,857 bytes (−94.6%). Cropped to a 128px tile rather than downscaled — scaling averages grain into mush. Same 7 frames and delays, indistinguishable at the real 3% opacity. LCP 4604 → 3580 ms.Loader. Indeterminate wave, no percentage: there is no honest denominator before the app has loaded, so the only thing it says is when it stops. Boot only, route-agnostic — a share link is that visitor's boot. 900ms floor on first visit, lifted for returning visitors via
localStorage, sinceimmutablecaching would otherwise flash it past unseen. Replaces the ring and the "...". Reduced motion gets a still line and frozen grain; the floor stays.Two bugs found.
SplashScreen's grain class was missing its closing bracket, so the splash has never had grain. Fixing it doubles the texture over<main>, which already carries it — left off, needs your call..grain { position: relative }strippedfixedoff the splash; this stylesheet loads after the Tailwind utilities and wins the tie. Removed.Verified.
tsc, 71 tests, both build modes, all four perf budgets. The wave does not become the LCP element — that stays the heroh1.