@kolkrabbi/kol-theme 0.90.0 → 0.92.0

package/kol-components-atoms.css

@@ -243,7 +243,7 @@
   border: 1px solid transparent;
 }
 @media (hover: hover) {
-  .kol-btn-primary:not(.kol-btn-animate):hover {
+  .kol-btn-primary:not(.kol-btn-animate):not(.kol-dd-trigger):hover {
     background-color: var(--kol-oq-08);
     color: var(--kol-surface-on-primary);
   }
@@ -256,7 +256,7 @@
   font-weight: 500;
 }
 @media (hover: hover) {
-  .kol-btn-secondary:not(.kol-btn-animate):hover {
+  .kol-btn-secondary:not(.kol-btn-animate):not(.kol-dd-trigger):hover {
     background-color: var(--kol-oq-inverse-40);
     color: var(--kol-surface-primary);
     border-color: transparent;
@@ -270,7 +270,7 @@
   font-weight: 500;
 }
 @media (hover: hover) {
-  .kol-btn-accent:not(.kol-btn-animate):hover {
+  .kol-btn-accent:not(.kol-btn-animate):not(.kol-dd-trigger):hover {
     background-color: var(--kol-accent-primary-strong);
     color: var(--kol-accent-on-primary);
   }
@@ -286,7 +286,7 @@
   border: 1px solid var(--kol-oq-08);
 }
 @media (hover: hover) {
-  .kol-btn-outline:not(.kol-btn-animate):hover {
+  .kol-btn-outline:not(.kol-btn-animate):not(.kol-dd-trigger):hover {
     background-color: var(--kol-oq-02);
     border-color: color-mix(in srgb, var(--kol-surface-on-primary) 25%, var(--kol-surface-primary));
     color: var(--kol-surface-on-primary);
@@ -299,7 +299,7 @@
   border: 1px solid transparent;
 }
 @media (hover: hover) {
-  .kol-btn-ghost:not(.kol-btn-animate):hover {
+  .kol-btn-ghost:not(.kol-btn-animate):not(.kol-dd-trigger):hover {
     background-color: var(--kol-oq-04);
     color: var(--kol-surface-on-primary);
   }
@@ -318,7 +318,7 @@
   border: 1px solid transparent;
 }
 @media (hover: hover) {
-  .kol-btn-nav:not(.kol-btn-animate):hover {
+  .kol-btn-nav:not(.kol-btn-animate):not(.kol-dd-trigger):hover {
     background-color: var(--kol-oq-04);
     color: var(--kol-surface-on-primary);
   }
@@ -343,7 +343,7 @@
   border: 1px solid transparent;
 }
 @media (hover: hover) {
-  .kol-btn-grey:not(.kol-btn-animate):hover {
+  .kol-btn-grey:not(.kol-btn-animate):not(.kol-dd-trigger):hover {
     background-color: var(--kol-oq-16);
     color: var(--kol-surface-on-primary);
   }
@@ -360,7 +360,7 @@
   font-weight: 500;
 }
 @media (hover: hover) {
-  .kol-btn-danger:not(.kol-btn-animate):hover {
+  .kol-btn-danger:not(.kol-btn-animate):not(.kol-dd-trigger):hover {
     background-color: color-mix(in srgb, var(--ui-error) 80%, var(--kol-surface-primary));
     color: var(--kol-color-absolute-white);
   }
@@ -372,13 +372,19 @@
 
 /* Press feedback — one stop past hover (2026-07-08 button-states spec).
  * Outside the hover guard: :active fires on touch too. */
-.kol-btn-primary:not(.kol-btn-animate):not(:disabled):active { background-color: var(--kol-oq-16); }
-.kol-btn-secondary:not(.kol-btn-animate):not(:disabled):active { background-color: var(--kol-oq-inverse-48); color: var(--kol-surface-primary); }
-.kol-btn-accent:not(.kol-btn-animate):not(:disabled):active { background-color: color-mix(in srgb, var(--kol-accent-primary) 70%, var(--kol-surface-primary)); }
-.kol-btn-outline:not(.kol-btn-animate):not(:disabled):active,
-.kol-btn-ghost:not(.kol-btn-animate):not(:disabled):active { background-color: var(--kol-oq-08); }
-.kol-btn-danger:not(.kol-btn-animate):not(:disabled):active { background-color: color-mix(in srgb, var(--ui-error) 70%, var(--kol-surface-primary)); }
-.kol-btn-grey:not(.kol-btn-animate):not(:disabled):active { background-color: var(--kol-oq-24); }
+/* NO HOVER, NO PRESS ON A DROPDOWN TRIGGER (user ruling 2026-08-28). Every
+ * variant excludes `.kol-dd-trigger` at the SOURCE. It used to be cancelled
+ * downstream — kol-components-molecules re-stated each variant's rest colours
+ * on :hover — and that restatement was specificity (0,4,0) against the sunken
+ * tone's (0,2,0), so hovering a SUNKEN trigger repainted it in the untoned
+ * fill: a light box beside two icon controls that stayed dark. */
+.kol-btn-primary:not(.kol-btn-animate):not(:disabled):not(.kol-dd-trigger):active { background-color: var(--kol-oq-16); }
+.kol-btn-secondary:not(.kol-btn-animate):not(:disabled):not(.kol-dd-trigger):active { background-color: var(--kol-oq-inverse-48); color: var(--kol-surface-primary); }
+.kol-btn-accent:not(.kol-btn-animate):not(:disabled):not(.kol-dd-trigger):active { background-color: color-mix(in srgb, var(--kol-accent-primary) 70%, var(--kol-surface-primary)); }
+.kol-btn-outline:not(.kol-btn-animate):not(:disabled):not(.kol-dd-trigger):active,
+.kol-btn-ghost:not(.kol-btn-animate):not(:disabled):not(.kol-dd-trigger):active { background-color: var(--kol-oq-08); }
+.kol-btn-danger:not(.kol-btn-animate):not(:disabled):not(.kol-dd-trigger):active { background-color: color-mix(in srgb, var(--ui-error) 70%, var(--kol-surface-primary)); }
+.kol-btn-grey:not(.kol-btn-animate):not(:disabled):not(.kol-dd-trigger):active { background-color: var(--kol-oq-24); }
 
 .kol-btn:disabled,
 .kol-btn[disabled] {

package/kol-components-molecules.css

@@ -48,31 +48,15 @@
 .kol-dd-trigger.kol-btn-sm { height: 28px; padding-block: 0; }
 .kol-dd-trigger.kol-btn-md { height: 32px; padding-block: 0; }
 .kol-dd-trigger.kol-btn-lg { height: 36px; padding-block: 0; }
-/* REST AND OPEN ARE THE ONLY STATES (2026-07-15 ruling, re-called twice
- * 2026-08-09). The trigger wears button chrome, and button chrome hovers AND
- * presses — so every kol-btn variant :hover and :active is PINNED BACK TO
- * REST here. The :not(:disabled) carries the weight of the atoms :active
- * selectors; this sheet loads after atoms in the same layer, so ties resolve
- * to these rules. */
-.kol-dd-trigger.kol-btn-primary:not(:disabled):hover,
-.kol-dd-trigger.kol-btn-primary:not(:disabled):active {
-  background: var(--kol-surface-secondary);
-  color: var(--kol-surface-on-primary);
-}
-/* oq-08, NOT oq-16 (DropdownHeightAndHover, kol-fxr 2026-08-28). This is a
- * pin-back to rest and it stopped being one: `.kol-btn-outline`'s rest border
- * moved to `oq-08` on 2026-08-26 ("ONE outline border across the controls"),
- * and this line kept the old `oq-16` — so the outline trigger quietly grew a
- * hover the 2026-07-15 ruling forbids, and an untoned Dropdown lit while a
- * sunken one beside it did not. A pin-back has to be re-read whenever the rest
- * value it mirrors moves; that is the cost of expressing "no state" as a
- * restatement rather than as an absence. */
-.kol-dd-trigger.kol-btn-outline:not(:disabled):hover,
-.kol-dd-trigger.kol-btn-outline:not(:disabled):active {
-  background: transparent;
-  color: var(--kol-surface-on-primary);
-  border-color: var(--kol-oq-08);
-}
+/* REST AND OPEN ARE THE ONLY STATES (2026-07-15, re-called 2026-08-09 and
+ * 2026-08-28). No :hover or :active rules for the trigger live here any more —
+ * kol-components-atoms.css excludes `.kol-dd-trigger` from every variant's
+ * hover and press instead. The pin-backs that stood here restated each
+ * variant's REST colours to cancel the button's, and that failed twice: one
+ * went stale when `.kol-btn-outline`'s rest border moved (2026-08-26), and a
+ * pin-back out-specifies the tone, so a sunken trigger hovered into the
+ * untoned fill. "No state" is an absence now, not a mirror. */
+
 /* ONE PIECE MEANS ONE WIDTH (2026-08-09 user call — "they are connected").
  * The trigger reserves the widest option's width by stacking every label in
  * one grid cell (hidden ghosts), so the panel — pinned to the trigger by
@@ -1278,19 +1262,13 @@
  * ink `fg-96`. `.kol-tone-inverse` stays selected for any class
  * hand-stamped on the old name.
  * ───────────────────────────────────────────────────────────────────── */
-.kol-view-toggle.kol-tone-sunken, .kol-view-toggle.kol-tone-inverse { background-color: var(--kol-fg-inverse-96); }
+.kol-view-toggle.kol-tone-sunken, .kol-view-toggle.kol-tone-inverse { background-color: var(--kol-tone-sunken-bg); }
 .kol-view-toggle.kol-tone-sunken > button[aria-pressed="true"], .kol-view-toggle.kol-tone-inverse > button[aria-pressed="true"] { background-color: var(--kol-fg-08); }
 .kol-view-toggle.kol-tone-sunken > button:not([aria-pressed="true"]):hover, .kol-view-toggle.kol-tone-inverse > button:not([aria-pressed="true"]):hover { background-color: color-mix(in srgb, var(--kol-color-absolute-white) 8%, transparent); }
-.kol-control.kol-tone-sunken, .kol-control.kol-tone-inverse { background-color: var(--kol-fg-inverse-96); }
-.kol-expand.kol-tone-sunken, .kol-expand.kol-tone-inverse { background-color: var(--kol-fg-inverse-96); }
-/* NO HOVER STATE ON THE DROPDOWN (user ruling 2026-08-28). Rest and open are
- * its only states — and the three selectors are what ENFORCE that: the base
- * `.kol-dd-trigger:hover/:active` rules paint surface-secondary, so the tone
- * re-states its own fill on all three and nothing moves. Deleting them gives
- * the hover back. */
-.kol-dd-trigger.kol-tone-sunken, .kol-dd-trigger.kol-tone-inverse,
-.kol-dd-trigger.kol-tone-sunken:not(:disabled):hover, .kol-dd-trigger.kol-tone-inverse:not(:disabled):hover,
-.kol-dd-trigger.kol-tone-sunken:not(:disabled):active, .kol-dd-trigger.kol-tone-inverse:not(:disabled):active { background-color: var(--kol-fg-inverse-96); }
+.kol-control.kol-tone-sunken, .kol-control.kol-tone-inverse { background-color: var(--kol-tone-sunken-bg); }
+.kol-expand.kol-tone-sunken, .kol-expand.kol-tone-inverse { background-color: var(--kol-tone-sunken-bg); }
+/* the tone's fill, one selector — nothing left to cancel (2026-08-28) */
+.kol-dd-trigger.kol-tone-sunken, .kol-dd-trigger.kol-tone-inverse { background-color: var(--kol-tone-sunken-bg); }
 /* THE PANEL IS OPAQUE (user 2026-08-28: "transparent doesn't work for
  * dropdown") — it floats over page content, and every `fg-*` stop is an alpha
  * wash that the content reads through. `oq-inverse-*`, the opaque tier, bakes
@@ -1298,7 +1276,7 @@
  * lands ~23.5 against the #121215 page's 18: lighter than the page, the wrong
  * side of it. `surface-tertiary` is the flat twin of what the trigger renders:
  * #0e0e11 (14.0) in dark against the trigger's 14.2, #ffffff in light. */
-.kol-dd-panel.kol-tone-sunken, .kol-dd-panel.kol-tone-inverse { background-color: var(--kol-surface-tertiary); }
+.kol-dd-panel.kol-tone-sunken, .kol-dd-panel.kol-tone-inverse { background-color: var(--kol-tone-sunken-bg); }
 /* the rest of the set — Button (icon-only especially), IconFrame, ThemeToggle:
  * the well, transparent edge, fg-96 ink; hover the white wash, pressed the
  * fg-08 chip — both LAYERED over the well (a gradient image over the fill),
@@ -1306,20 +1284,20 @@
 .kol-btn.kol-tone-sunken,
 .kol-icon-frame.kol-tone-sunken,
 .kol-theme-toggle.kol-tone-sunken {
-  background-color: var(--kol-fg-inverse-96);
+  background-color: var(--kol-tone-sunken-bg);
   border-color: transparent;
   color: var(--kol-fg-96);
 }
 @media (hover: hover) {
   .kol-btn.kol-tone-sunken:not(.kol-btn-animate):not(:disabled):hover {
-    background-color: var(--kol-fg-inverse-96);
+    background-color: var(--kol-tone-sunken-bg);
     background-image: linear-gradient(color-mix(in srgb, var(--kol-color-absolute-white) 8%, transparent), color-mix(in srgb, var(--kol-color-absolute-white) 8%, transparent));
     color: var(--kol-fg-96);
   }
 }
 .kol-btn.kol-tone-sunken.kol-btn-pressed,
 .kol-btn.kol-tone-sunken:not(:disabled):active {
-  background-color: var(--kol-fg-inverse-96);
+  background-color: var(--kol-tone-sunken-bg);
   background-image: linear-gradient(var(--kol-fg-08), var(--kol-fg-08));
   color: var(--kol-fg-96);
 }

package/kol-design-tokens.css

@@ -74,6 +74,19 @@
    * first fifth of the duration and the rest on a settle you cannot see — so
    * every motion read as instant no matter what duration it was given, and a
    * small hover affordance never showed its move at all. */
+  /* THE SUNKEN PLATE (ControlToneSunken, user ruling 2026-08-28) — the one fill
+   * every `tone="sunken"` control paints: ViewToggle's well, Input, SearchInput,
+   * the Dropdown trigger AND its panel, Button, IconFrame, ThemeToggle.
+   *
+   * OPAQUE and theme-invariant, and both halves are the ruling: "opaque so it
+   * doesn't bleed". A translucent well renders whatever is under it, which is
+   * how this went wrong twice in a day — `fg-absolute-24` and `fg-inverse-96`
+   * are washes, and the second one also follows the theme stamp, so an app
+   * painting a dark page without stamping `data-theme` got a near-white control
+   * row. Sunken means BELOW the plane; a plate that changes with the plane
+   * cannot say that. Ship one colour and let it be the same everywhere. */
+  --kol-tone-sunken-bg: color-mix(in srgb, var(--kol-color-absolute-white) 11%, var(--kol-color-absolute-black));
+
   --kol-ease-house: cubic-bezier(0.4, 0, 0.2, 1);
   /* the bounce — overshoots past its target and settles back (y > 1 is what
    * makes it bounce; house only decelerates). For a press that should feel

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kolkrabbi/kol-theme",
-  "version": "0.90.0",
+  "version": "0.92.0",
   "description": "KOL (Kolkrabbi) design-system tokens + base CSS — brand-neutral. The canonical token/cascade layer every other KOL package and consumer builds on.",
   "license": "MIT",
   "type": "module",