From f4b3ec23aa17738d95ede506f2fa6ad79c8407cd Mon Sep 17 00:00:00 2001 From: Sam Shao Date: Sun, 9 Aug 2026 20:47:48 -0700 Subject: [PATCH] Fix footer-legal to span full width and reach the footer's true bottom MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Root cause: footer.css's own "footer .footer > div" rule applied its 1240px-max-width/centered/padded box to the shared wrapper div that both the black footer's columns section AND the new footer-legal section sit inside — footer.js flattens the fragment's sections into one plain, unconstrained wrapper div, so that single rule was constraining both sections together as one unit, not each individually. footer-legal's own full-bleed override on .footer-legal-container alone couldn't undo that: the constraint was on their shared *parent*, not on the section itself, so no override on the section could widen it. This also explains the leftover gap at the very bottom — the wrapper's own 32px bottom padding applied once, after whichever section happened to be last. Fix: retarget footer.css's rule to each ".section" child individually (matching how main > .section > div already lets page-level sections like cards-panel differ from each other instead of all sharing one box), so footer-legal's own override can correctly widen just itself. Bumped that override's own specificity to guarantee it wins regardless of stylesheet load order (block CSS loads when each block decorates, and footer-legal decorates as a block nested inside footer's own fragment, so there's no hard guarantee footer.css settles first). Verified at 390px and 1464px: footer-legal now spans the full viewport width and its bottom edge lines up exactly with