Cascade 0.2.3 — the column presets get a gap

On X-style and Bluesky-style the left rail sat flush against the feed — a Calendar link, a widget caption and a leaderboard count all measuring exactly 0px from the edge. Text touching a boundary reads as clipped even when nothing is cut.

Those two presets set the column gap to 0 on purpose: their feed column is drawn with borders rather than whitespace. But that also removed the only thing keeping the rail off it. They now use an 18px gap.

🚨 Padding could never have fixed this, and it is worth knowing why. Both .IndexPage-nav and its ul compute a fixed width pinned to the sidebar variable rather than filling their parent — so they sit straight over any padding their container is given. Two attempts died there before measuring the ul. Separation between fixed-width columns has to be a gap.

Two gaps cost 36px, taken off the feed at every band, so the totals are unchanged: 1180 / 1352 / 1448 / 1576 exactly as in 0.2.2. The feed still runs 682 → 1008 across the ladder, and there is now 18px either side of it.

Also reverts the max-height / overflow-y from 0.2.0's pinned rail, which had quietly made the sidebar a clipping container on both axes and would have cut off any dropdown opening inside it. The rail is still sticky.

• Support: https://ernestdefoe.online
• Packagist: https://packagist.org/packages/ernestdefoe/cascade