editor-shell 0.33.0 → 0.33.1

package/dist/panel/panel.css

@@ -186,6 +186,56 @@
   flex: none;
 }
 
+/* …EXCEPT IN THE ONE SLOT THIS PACKAGE HANDS CONSUMERS (card 66516).
+
+   `SettingsField` stacks its control into `.es-field-ctl`, and that slot is
+   `display: flex`. So `flex: none` above stops meaning "do not stretch" and
+   starts meaning "size to your own content" — and `container-type:
+   inline-size` is size containment on that axis, so this wrapper HAS no
+   content width to size to. The strip comes out at ZERO.
+
+   ⚠️ NEITHER DECLARATION ABOVE IS WRONG, WHICH IS WHY THIS IS AN EXCEPTION AND
+   NOT AN EDIT. The containment is what lets `100cqi` mean the strip's own
+   width for the word-drop arithmetic further down; `flex: none` is what keeps
+   the strip from stretching in the contexts it was written for. They collide
+   only here.
+
+   MEASURED, `tests/fixtures/field-slot-basis.html`, Chromium, before this rule:
+
+       panel   field content   strip in .es-field-ctl   strip in a block row
+       320px   320px           0px                      320px
+       220px   220px           0px                      220px
+
+   The block-row column is the control: it is where every one of these strips
+   lived until now — a consumer's own block row, where `flex: none` is inert
+   and the box fills the line. That is why this looked right for a year and
+   why it broke for the first consumer that took this package's own advice.
+
+   ⚠️ FOUND BY A PERSON LOOKING, NOT BY A GUARD. Card 66508 shipped 1198 green
+   checks over this: every button present, `aria-pressed` correct, exactly one
+   chip active, the glyph in its slot, `tsc` clean, the PR MERGEABLE. All of
+   that is true of a control 0px wide. Our checks ask whether markup EXISTS;
+   this one asks whether it OCCUPIES SPACE, which is the gap that let it ship.
+
+   `flex: 1 1 auto` rather than a percentage width: the slot is a flex row that
+   may hold a value readout or a second control beside the strip, and a
+   percentage would overflow it the day it does. `min-width: 0` because a flex
+   item's automatic minimum is its content size, and the containment above
+   makes that meaningless here — without it the strip cannot shrink below the
+   basis the parent gives it.
+
+   BOTH `-fit` WRAPPERS, though only the segmented one has a live consumer
+   today. Measured in the shop at the time of writing: 1845 custom fields
+   rendered, 68 draw a tab strip, 0 of them inside `.es-field-ctl`. But
+   `PanelTabs` already draws a strip AMONG the fields and is one refactor from
+   the slot, and the two wrappers share the declaration that causes this — a
+   rule that fixed one and left the other would be a trap wearing a fix. */
+.es-field-ctl > .es-tabs-fit,
+.es-field-ctl > .es-segs-fit {
+  flex: 1 1 auto;
+  min-width: 0;
+}
+
 /* THE TRACK (card 66138). Lewis, looking at a real settings panel: the tab he
    is NOT on does not invite a click — it does not even look like a button. He
    was shown six treatments in `mockups/settings-tab-strip-options.html` and

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "editor-shell",
-  "version": "0.33.0",
+  "version": "0.33.1",
   "description": "Shared editor-chrome primitives for the EFFICIENT editors: EditorRail (a Next-16-safe left icon-rail leaf), the shell token layer, and GoldTextInput — type in place and watch the markup formatting appear as you type.",
   "license": "MIT",
   "author": "Lewis Liu",