/* ════════════════════════════════════════════════════════════════════════════ FRB SHELL — the app page itself, not the parts inside it. frb-tokens.css says what the values are. frb-components.css says what a button, a field, a head is. frb-compat.css maps 101 pages' own class names onto those. This file says what an APP PAGE IS: a rail, a bar carrying the trail down from the portals, a head, and sections under it — in that order, at those sizes, on every one of them. It exists because four waves of mapping could not close the gap. A stylesheet can only restyle what the markup already contains; it cannot put the trail somewhere it is not, cannot delete a second name bar, and cannot decide that an app should have a head. Those are markup, and markup is what the shell reconstruction changes. This file is the target that reconstruction aims at. TWO HALVES, and the split matters: · GLOBAL — the dropdown list and the scrollbar. Every page gets these, reconstructed or not, because both are defects rather than differences. · THE SHELL — layout, scoped to `body[data-frb-shell]`. A page opts in by carrying that attribute, which it gets when its markup is reconstructed to the shape below. An un-reconstructed page is untouched, so the rollout can be done app by app and verified app by app. The shape, which is Industry Hub's and Carbon Snippet Studio's — the two the product owner picked out as right:

the view's name, its line, its actions

Name

One sentence.

…

════════════════════════════════════════════════════════════════════════════ */ /* ═══ GLOBAL 1 — THE DROPDOWN LIST ═════════════════════════════════════════ Measured across the product: 380