@khipu/design-system 0.3.5-alpha.13 → 0.3.5-alpha.15

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -15,7 +15,7 @@
15
15
  *
16
16
  * AUTO-GENERATED FILE - DO NOT EDIT MANUALLY
17
17
  * Source: design-system/src/tokens/tokens.json
18
- * Generated: 2026-08-17T18:53:32.414Z
18
+ * Generated: 2026-08-26T20:01:58.534Z
19
19
  *
20
20
  * To regenerate:
21
21
  * cd design-system && npm run tokens:generate
@@ -399,13 +399,13 @@
399
399
  /* ============================================================================
400
400
  DARK MODE COLOR TOKENS
401
401
  Override only color variables; everything else inherits from :root.
402
- Activated via [data-theme="dark"] on <html>, <body>, or a wrapper —
403
- or via the BeerCSS-style body.dark class. Both selectors are emitted so
404
- a body.dark app gets the FULL dark theme (core + extended tokens); a
405
- single source flipping only partially is how mixed light/dark bugs arise.
402
+ Activated ONLY via [data-theme="dark"] on <html>, <body>, or a wrapper.
403
+ body.dark is deliberately NOT a trigger: BeerCSS adds that class on its
404
+ own when the OS reports a dark preference, so honouring it turns dark on
405
+ for consumers that never opted in. Dark stays opt-in until an app sets
406
+ data-theme explicitly.
406
407
  ============================================================================ */
407
408
 
408
- .kds-theme-root.dark,
409
409
  .kds-theme-root [data-theme="dark"] {
410
410
 
411
411
  /* Primary palette - Khipu brand */
@@ -881,11 +881,10 @@
881
881
  values so selected states / rows / hovers adapt. Additive: the light
882
882
  :root / body.light values above are unchanged. Tokens already defined as
883
883
  var() refs (warning-soft, danger-soft) adapt on their own and are omitted.
884
- body.dark is included on purpose: the light group above also matches
885
- body.dark (specificity 0,1,1), so a bare [data-theme] override (0,1,0)
886
- would lose on a body that carries the transitional dark class.
884
+ body.dark is deliberately NOT a trigger: BeerCSS adds that class on its own
885
+ when the OS reports a dark preference, so honouring it turns dark on for
886
+ consumers that never opted in. Dark stays opt-in via data-theme.
887
887
  ======================================== */
888
- .kds-theme-root.dark,
889
888
  .kds-theme-root [data-theme="dark"] {
890
889
  --kds-color-primary-faint: #1E1030; /* dark brand-tinted subtle surface (selected rows/cards) */
891
890
  --kds-color-info-soft: var(--kds-alert-info-bg); /* dark translucent blue */
@@ -919,7 +918,7 @@
919
918
  opt-out for Chrome/WebView "Auto Dark Theme" on Android: without it, an
920
919
  OS-dark device heuristically darkens SOME elements of a light page (mixed
921
920
  light/dark rendering in production apps). Dark is reached only by an
922
- explicit [data-theme="dark"] / body.dark opt-in. */
921
+ explicit [data-theme="dark"] opt-in. */
923
922
  .kds-theme-root,
924
923
  .kds-theme-root,
925
924
  .kds-theme-root {
@@ -938,8 +937,7 @@
938
937
  }
939
938
 
940
939
  /* Explicit dark theme: let native UI (form controls, scrollbars) render dark. */
941
- .kds-theme-root [data-theme="dark"],
942
- .kds-theme-root.dark {
940
+ .kds-theme-root [data-theme="dark"] {
943
941
  color-scheme: dark;
944
942
  }
945
943