max / quasi

Fold a menu run's overflow, since only a browser can measure it Fallback::Menu says the members a Shed would drop move into one overflow control instead. It has been drawn as wrap since it existed, and makeover-webview's own CSS says why: the fold needs to know the run is out of room, @container compares against a length, and every honest CSS spelling needs the authored breakpoint the room ruling forbids. menu.js is the measuring. It reads what makeover-webview emits and nothing else -- .run-menu, and the two priority classes Ranked already writes -- and builds its control out of that crate's .run-overflow classes, so the surface is the design system's and only the measurement is here. A tab strip is one member of its run and its tabs are what fold. That is the shape all five described MNW strips have: across(Fallback::Menu) on a tab group whose run holds no members of its own, so a reading that only looked at the run's children would find one strip that always fits. Shedding is by priority tier and then last-first within a tier, which is what "by priority, not by document order" leaves once priority is spent. Never the last member: a control that folded everything into itself leaves a strip with nothing on it. Degrading is the default rather than the failure. A page that never runs this keeps .run-menu's own flex-wrap: wrap and every member stays reachable, which is rule 1; the data-menu mark this script writes is what turns wrapping off. This replaces MNW's core/tabs.ts tabOverflow, which looked for .tabs and never saw a described strip at all. Takes makeover-webview 0.64.0.