origam 2.18.10 → 2.18.11

package/dist/src/components/Btn/OrigamBtn.vue

@@ -440,6 +440,24 @@ defineExpose({
 	.origam-btn {
 		$this: &;
 
+		// ⛔ #933 — `display` was never declared here. The root then fell back
+		// to the UA default, which for the `<a>` / `<span>` tags `useLink`
+		// renders is `inline`. An inline box ignores `height`, `min-width` and
+		// vertical `padding`, and it stretches to the full line box — so a Btn
+		// dropped into a plain block parent (`<p>`, `<div>`) rendered as a
+		// full-width, 15px-tall strip. Every Btn in this DS *looked* correct
+		// only because its parent happened to be a flex/grid container, which
+		// blockifies the child: measured on the marketing site, all 9 visible
+		// Btn roots computed `display: block` with a `display: flex` parent,
+		// and the single Btn inside a `<p>` computed `inline` at 984px wide.
+		//
+		// `inline-block` is the value the rest of this rule already assumed —
+		// `vertical-align: middle` right below only has meaning on an
+		// inline-level box. It is also the safest: inside a flex/grid parent it
+		// blockifies to `block`, i.e. byte-for-byte today's computed value, so
+		// no existing layout moves. `&--block` still overrides it with `flex`.
+		display: inline-block;
+
 		position: var(--origam-btn---position, relative);
 		vertical-align: middle;
 		flex-shrink: 0;

package/dist/src/components/List/OrigamList.vue

@@ -355,7 +355,16 @@ defineExpose({
 		}
 
 		&--nav {
-			--origam-list---padding-inline: 8px;
+			// ⛔ #934 — this used to declare `--origam-list---padding-inline`,
+			// a name NOTHING reads. A custom property is not a shorthand: it
+			// expands to nothing, so `padding-inline-start/end` above kept
+			// resolving to the sheet's `--origam-space---0`. Measured on the
+			// marketing appbar menu across all 8 identities: list inline
+			// padding `0px/0px`, so the rows ran edge-to-edge inside the menu
+			// and their hover surface was clipped by the menu's own corner
+			// radius. The two longhands are the names the base rule reads.
+			--origam-list---padding-inline-start: var(--origam-space---2, 8px);
+			--origam-list---padding-inline-end: var(--origam-space---2, 8px);
 			--origam-list-subheader---font-size: var(--origam-list__subheader---nav-font-size, 0.75rem);
 			--origam-list---indent-padding: var(--origam-list---indent-padding-nav, -8px);
 		}

package/dist/src/components/List/OrigamListItem.vue

@@ -626,7 +626,12 @@ defineExpose({
 		}
 
 		&--nav {
-			--origam-list-item---padding-inline: 8px;
+			// ⛔ #934 — same dead name as `.origam-list--nav` carried:
+			// `--origam-list-item---padding-inline` is read nowhere. The base
+			// rule reads the two longhands, inside a `calc()` that also folds
+			// in indent and density, so they go in here under the same names.
+			--origam-list-item---padding-inline-start: var(--origam-space---2, 8px);
+			--origam-list-item---padding-inline-end: var(--origam-space---2, 8px);
 
 			&:not(:only-child) {
 				--origam-list-item---margin-block-end: 4px;

package/dist/src/components/Switch/OrigamSwitch.vue

@@ -473,6 +473,44 @@ defineExpose({
           }
         }
       }
+
+      /*
+       * ⛔ MEASURED (Chromium, /why-origam demo, all 8 marketing identities,
+       * light + dark, checked + unchecked): `OrigamSelectionControl`'s shared
+       * `&--focus-visible` rule draws its outline on
+       * `.origam-selection-control__input` — a ~28px square hit-area that is
+       * a SIBLING of `.origam-switch-track` (rendered via the `default`
+       * slot), never a descendant. The track's `overflow: hidden` therefore
+       * can never clip that outline, and because the square hit-area is
+       * already taller than the track (24px default / 32px inset) and offset
+       * by the thumb's hardcoded ±10px `translateX`, the ring visibly
+       * detaches from the track: 8px past its top/bottom edge and 8px past
+       * whichever side the thumb isn't currently near (right when ON, left
+       * when OFF) on every identity, `material` included — its own
+       * screenshot simply wasn't captured while focused.
+       *
+       * For Checkbox/Radio the square hit-area IS the visible control, so
+       * the shared rule is correct there and stays untouched
+       * (`OrigamSelectionControl.vue` is not modified). For Switch the
+       * visible control is the elongated track, so the ring is moved onto
+       * `.origam-switch-track` instead — same two tokens the shared rule
+       * already reads (`--origam-border__width---2`,
+       * `--origam-color__border---focus`), just retargeted to the shape a
+       * switch actually is. Native `outline` already follows an element's
+       * own `border-radius` in every supported browser, so the ring traces
+       * the track's real shape (pill / rounded / square per `rounded` prop)
+       * with no extra CSS.
+       */
+      &--focus-visible {
+        :deep(.origam-selection-control__input) {
+          outline: none;
+        }
+
+        :deep(.origam-switch-track) {
+          outline: var(--origam-border__width---2, 2px) solid var(--origam-color__border---focus, currentColor);
+          outline-offset: var(--origam-space---1, 2px);
+        }
+      }
     }
 
     &.origam-input {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "origam",
-  "version": "2.18.10",
+  "version": "2.18.11",
   "type": "module",
   "description": "origam — a Vue 3 design system with multi-theme design tokens, CSS-first components and TypeScript types.",
   "keywords": [