/* article.small.css — the blog article below 768px * * From the Mobile view design setup mobile handoff → * `design_handoff_mobile_pages/Blog Article Mobile.dc.html`, designed at 375px. * * ── THE RAIL UNROLLS ──────────────────────────────────────────────────────── * Desktop is `aside.ar__rail | article.ar__main`. The mobile design dissolves * the rail and threads its parts through the article: byline at the top, * contents under the lede, newsletter and share near the foot. * * `display: contents` on BOTH boxes is what makes that possible. It flattens * thirteen elements into one flex column on .ar__grid, and from there `order` * puts each exactly where the design wants it — which no amount of ordering * could do while the two containers still boxed their own children. * * THE
ROLE SURVIVES THIS. That was worth checking rather than * assuming: `display: contents` used to drop an element out of the * accessibility tree entirely, which would have been an unacceptable price for * a layout. The bug is long fixed — measured on this page through CDP's * Accessibility.getFullAXTree, the article role is present both with and * without the rule. If that ever regresses, the fallback is to box .ar__main * again and accept contents landing above the title. * * ORDER IS DECLARED FOR EVERY ITEM, not just the ones that move. With two * containers flattened into one column, source order describes nothing a reader * of this file would guess, so leaving any item on the default 0 would be a * trap rather than a saving. * * Unlike the design: the theme's contents is a