
The Top Bar That Was Eating the Phone Screen
Two lines where one would do: how a global CSS reset and an orphan style block made the Arachne bar eat 117 pixels on mobile — and what finally measured the difference.
4 posts

Two lines where one would do: how a global CSS reset and an orphan style block made the Arachne bar eat 117 pixels on mobile — and what finally measured the difference.

The portfolio's projects section almost got a category filter. It didn't — and that was the best decision. The story of a 2-column grid that resisted the lure of complexity.

After 5 days making the circle start from the click on desktop, mobile still used a crossfade — by documented decision: clip-path paints per frame and janks weak GPUs. Until Samuel asked for the opposite. What made the reversal possible? The anti-stutter fixes that were already in global.css.

Portfolio was 100% functional, 218 tests passing, zero CI errors. But mobile Chrome users saw old versions when restoring tabs. The cause: Chrome's bfcache ignores HTTP headers — and the fix came cross-project from LifeLog.