/* The chrome: masthead, mega-menu, drawer, footer, dialog. Phase F stop F4.2. * * WHERE THIS COMES FROM. Every rule is ported from a generator whose output the * owner signed off, not re-derived from prose -- ops/mockups/README.md states * that reasoning and ops/docs/phase-f/f4-build.md section 7 requires it: * * .mh-* masthead chrome_shared.py F3.4, signed off 2026-08-31 * .mm-* mega-menu nav-build.py F3.3, signed off 2026-08-29 * .dw-* drawer nav-build.py F3.3, variant A * .ftr-* footer footer-build.py F3.5, signed off 2026-09-01 * .dlg-* dialog dialog-build.py F3.6, signed off 2026-09-02 * * FOUR THINGS ARE DELIBERATELY NOT COPIED, because a mockup is a picture of a * page inside another page and this is the page: * * 1. THE WIDTH SWITCH. The mockups select layout with .uc[data-w="390"] and * friends, because a frame of fixed pixel width cannot ask the viewport. Here * those become real media queries on ONE breakpoint, 1200px -- chrome.md * section 3.1. Below it: hamburger, drawer, no phone in the row, mark-only * logo, no mega-menu. At and above: mega-menu, phone in the row, the wordmark, * no hamburger. * 2. THE FRAME SCOPE. Every mockup rule is prefixed .uc and positioned * `absolute` against it. The drawer, its scrim and the dialog are `fixed` * here: they belong to the viewport, not to an element. * 3. THE TOKENS. The mockups redeclare --brand and the rest on .uc / .mk. They * are on :root in uc-ds.css and are not redeclared. * 4. THE VARIANT TOGGLES. nav-build.py carries both drawer variants behind * [data-v]. Only variant A ships -- ADR 0037, the owner's decision of * 2026-08-29: a group expands in place, with its header sticky. * * ONE KNOWN DEPARTURE FROM A SIGNED-OFF ARTEFACT, and it is the specification's. * chrome_shared.py switches the wordmark on data-w="390" alone, so its 1010 * frame draws the full lockup. chrome.md says mark-only below 1200 in section * 3.1's table and again in 3.3. The spec wins; the mockup carries a note saying * so and was not edited, because a signed-off artefact is an acceptance * criterion. * * .mm-* IS ALSO MMENU'S NAMESPACE. There is no clash because jquery.mmenu.all * .css leaves base.html in this same commit. Do not reintroduce it. */ /* ------------------------------------------------------------ page ground */ /* The first element rules in the project. F4.1 could carry none -- its whole * acceptance was that no existing page changed -- and that constraint is * deliberately given up here, which is what f4-build.md rule B1 anticipates: * F4.2 onward changes markup and CSS together and is verified by browsing. * * These reach EVERY page, including the ones not rewritten until F4.4 to F4.6, * so they are the smallest set that makes the chrome coherent and no more. * * THE RESET BELOW WAS ARGUED AGAINST HERE AND THE ARGUMENT EXPIRED. This block * said there must be no global margin or box-sizing reset, "because Bootstrap * still lays out the body of those pages and resetting under it would move * them". True while every page loaded Bootstrap. F4.3 made index_new.html and * flatpages/default.html the first templates to empty the legacy block -- so * they had NO reset at all, the browser's default `body{margin:8px}` applied, * and the page rendered inside an 8px frame. Reported on review 2026-09-05. * * IT IS A NO-OP ON THE LEGACY PAGES. Bootstrap 3 sets exactly these two things: * `*{box-sizing:border-box}` on every element and its pseudo-elements, and * `body{margin:0}`. Declaring them here changes nothing where Bootstrap is * loaded and supplies them where it is not, which is the only shape that works * while both kinds of page exist. ~~It stays after F4.7~~ -- it stayed at * F4.8a, and it is now the only copy rather than a duplicate. */ *, *::before, *::after { box-sizing: border-box; } body { margin: 0; background: var(--surface); color: var(--ink); font-family: var(--font-sans); font-size: var(--fs-base); line-height: var(--lh-base); -webkit-font-smoothing: antialiased; } /* Prices and counts line up. tnum is in the subset and verified to survive it. */ .tabular { font-variant-numeric: tabular-nums; } /* --------------------------------------------------- the chrome's link styling */ /* WRITTEN TO HOLD BOOTSTRAP OFF, AND KEPT AT F4.8a WHEN BOOTSTRAP WENT. * * The header below says this block goes with bootstrap.min.css. It does not, * and the reason is worth stating: these rules were written to neutralise * Bootstrap's element-level defaults, but what they declare -- no underline on * the four navigation roots, white on hover for the masthead phone and cart -- * is now the chrome's own appearance rather than a counterweight to somebody * else's. Deleting them does not restore a neutral state; it underlines every * masthead, menu, drawer and footer link and turns two of them blue on hover. * * So the rules stay and only their justification changes. Whether the chrome * should keep this appearance now that nothing forces it is a question for * someone looking at the rendered page, not for the stop that deleted the * stylesheet -- f4-build.md B1, one kind of change per stop. * * The scoping comment below is also spent: it explains why this is scoped to * the chrome's five roots rather than written as a global reset, and the reason * was that un-rewritten page bodies still laid out under Bootstrap. There are * no un-rewritten page bodies. The scoping is now simply narrow. * * WHAT IT WAS FOR, kept because it is the record of four real symptoms. * Reported on the F4.2 review, 2026-09-04, as four symptoms with one cause: * * a:hover,a:focus{color:#23527c;text-decoration:underline} * underlined the masthead phone AND recoloured it -- and #23527c is * Bootstrap 3's untouched @link-hover-color, the value design-system.md * section 5 records as the nearest thing the old stylesheet had to a brand * colour. Bootstrap blue, on a teal masthead. * * It also explains why «Сушилки для рук» alone looked wrong in the menu * bar: it is the ONLY among the eight top-level items -- the other * seven are