@axiapps/axi-design 1.28.0 → 1.30.0

package/README.md

@@ -138,6 +138,10 @@ not "what does the system look like". Everything else is
 | `--axi-check-size` | the size of an `.axi-check` or `.axi-radio` box | `22px` | `<input type="checkbox" class="axi-check" style="--axi-check-size: 16px">` |
 | `--axi-check-fill` | the fill a checked `.axi-check` takes, and the colour of a checked `.axi-radio`'s diamond | `var(--axi-accent)` | `<input type="checkbox" class="axi-check" style="--axi-check-fill: var(--axi-danger)">` |
 | `--axi-textarea-h` | the minimum height of a `<textarea class="axi-input">` | `90px` | `<textarea class="axi-input" style="--axi-textarea-h: 200px">` |
+| `--axi-btn-pad` | the padding inside an `.axi-btn`. The three named steps set it for you; reach for the knob only for a size they do not cover | `12px 20px` | `<button class="axi-btn" style="--axi-btn-pad: 3px 7px">` |
+| `--axi-btn-size` | an `.axi-btn`'s text size, which travels with its padding | `13px` | `<button class="axi-btn" style="--axi-btn-size: 10px">` |
+| `--axi-input-pad` | the padding inside an `.axi-input`, for a field that is furniture in a header rather than a control on a page | `11px 12px` | `<input class="axi-input" style="--axi-input-pad: 7px 12px">` |
+| `--axi-input-size` | an `.axi-input`'s text size, which travels with its padding | `14px` | `<input class="axi-input" style="--axi-input-size: 13px">` |
 | `--axi-well-pad` | the padding inside an `.axi-well` | `10px` | `<div class="axi-well" style="--axi-well-pad: 18px">` |
 | `--axi-well-radius` | an `.axi-well`'s corner radius, for a well used at reading scale rather than page scale | `var(--axi-radius)` | `<div class="axi-well" style="--axi-well-radius: var(--axi-radius-sm)">` |
 | `--axi-rail-w` | an `.axi-rail`'s width, for labels longer than the default holds | `208px` | `<aside class="axi-rail" style="--axi-rail-w: 260px">` |

package/dist/axi.css

@@ -374,13 +374,15 @@ button.axi-panel--tile:hover,
 /* ---------- button ---------- */
 .axi-btn {
   display: inline-flex; align-items: center; gap: 8px;
-  padding: 12px 20px;
+  padding: var(--axi-btn-pad, 12px 20px);
   border: var(--axi-border-control) solid var(--axi-ink-line);
   border-radius: var(--axi-radius-sm);
   background: var(--axi-ground);
   color: var(--axi-text-dim);
   font: var(--axi-t-label);
   letter-spacing: var(--axi-ls-label);
+  /* After the `font` shorthand, which sets 13px and would otherwise reset it. */
+  font-size: var(--axi-btn-size, 13px);
   text-transform: uppercase;
   text-decoration: none;
   cursor: pointer;
@@ -388,8 +390,18 @@ button.axi-panel--tile:hover,
 }
 /* Hover lifts. Nothing in this language fades or glows: the block deepens and
    the element moves against it, which reads instantly even in peripheral
-   vision and costs no colour. */
-.axi-btn:hover {
+   vision and costs no colour.
+
+   :where() around the state, not decoration. `.axi-btn:hover` weighs two
+   classes, so it beat the ink layer's one and a button written
+   `class="axi-btn axi-ink-danger"` went from danger red to plain white under
+   the cursor - the verdict disappearing at the moment the reader reaches for
+   it. That is rule 6's "a component may not out-rank its own modifiers" with
+   a pseudo-class doing the out-ranking instead of an element, and it wants the
+   same fix. The dim-to-plain brighten still happens: it is the fallback now,
+   not an override, so it applies to exactly the buttons that have not been
+   told what colour they are. */
+.axi-btn:where(:hover) {
   color: var(--axi-text);
   box-shadow: var(--axi-shadow-control);
   transform: translate(-2px, -2px);
@@ -402,13 +414,33 @@ button.axi-panel--tile:hover,
 /* The one button that rests with a block already under it, so the generic
    hover's translate alone would move element and block together and leave the
    lower-right edge where it started - the "grows rather than lifts" failure
-   rule 4 warns about. It lifts the way a panel does: the block deepens too. */
+   rule 4 warns about. It lifts the way a panel does: the block deepens too.
+
+   Not wrapped in :where() the way the generic hover is: this colour is the
+   accent fill's contrast pair, not a default a consumer might mean to replace.
+   An ink reaching it would put a status colour on top of the accent block and
+   the label would stop being legible, which is rule 5's reason for the chip. */
 .axi-btn--primary:hover {
   color: var(--axi-accent-ink);
   box-shadow: var(--axi-shadow-control-hover);
 }
 .axi-btn--ghost { background: transparent; }
 .axi-btn--dashed { background: transparent; border-style: dashed; }
+/* Three sizes, because one was a fiction. A language that ships a single
+   button leaves every dense place in an app - a filter beside 11px type, a
+   toolbar, a row of controls in a card header - to spell its own padding and
+   font-size in utilities, and at that point the button is only borrowing the
+   border. The steps are named rather than left to the knobs for the same
+   reason .axi-table--dense is: a consumer saying "this is the small one"
+   should not have to pick the numbers, and the numbers should move together
+   when they move.
+   The icon step is the one the language got wrong rather than omitted. An
+   icon-only button has no label to pad around, so the 20px sides meant for
+   one produced a wide rectangle around a single glyph - visible in this
+   language's own gallery, in the example titled "Alone in a button". */
+.axi-btn--sm   { --axi-btn-pad: 8px 13px; --axi-btn-size: 12px; }
+.axi-btn--xs   { --axi-btn-pad: 5px 9px;  --axi-btn-size: 11px; }
+.axi-btn--icon { --axi-btn-pad: 7px; }
 
 /* ---------- pill ---------- */
 /* A filter toggle. Its pressed state fills with whatever colour the consumer
@@ -429,7 +461,10 @@ button.axi-panel--tile:hover,
   cursor: pointer;
   transition: transform .1s, box-shadow .1s;
 }
-.axi-pill:hover {
+/* :where() for the same reason the button's hover has it - the brighten is
+   what a pill that has not been told its colour falls back to, not an override
+   of one that has. See rule 6's addendum. */
+.axi-pill:where(:hover) {
   color: var(--axi-text);
   box-shadow: var(--axi-shadow-control);
   transform: translate(-2px, -2px);
@@ -439,11 +474,14 @@ button.axi-panel--tile:hover,
   color: var(--axi-accent-ink);
   box-shadow: var(--axi-shadow-control);
 }
-/* Spelled out rather than left to source order: `.axi-pill:hover` and
-   `.axi-pill[aria-pressed="true"]` have identical specificity, so without this
-   rule a pressed pill under the cursor kept its pressed block while still
-   taking the hover's translate - a slide, not a lift, decided by which rule
-   happened to come last in the file. A pressed pill keeps its fill and lifts. */
+/* Spelled out rather than left to the cascade. This was originally about equal
+   specificity - the two rules weighed the same, so which one a pressed pill
+   under the cursor took was decided by file order. The hover's :where() ended
+   the tie in the pressed rule's favour, and made this rule matter more rather
+   than less: `transform` is set only by the hover, so a pressed pill would take
+   its own fill and block from the higher-weight rule while still taking the
+   hover's translate - a slide, not a lift, which is the failure rule 4 names.
+   A pressed pill keeps its fill and lifts. */
 .axi-pill[aria-pressed="true"]:hover {
   background: var(--axi-pill-fill, var(--axi-accent));
   color: var(--axi-accent-ink);
@@ -562,15 +600,23 @@ button.axi-panel--tile:hover,
 .axi-diamond--series { background: var(--axi-series, var(--axi-accent)); }
 
 /* ---------- input ---------- */
+/* Two knobs rather than one fixed size, for the same reason --axi-well-pad
+   exists: a field is used at two scales. A form control standing on a page is
+   the 14px default; a filter sitting in a section header or a row in a bar is
+   smaller, because there it is furniture next to 11px type rather than the
+   thing the page is for. The alternative is what this file did before - a
+   context selector per place that wanted the small one (.axi-palette__bar
+   .axi-input, still the only one upstream needs) - and that does not scale
+   past the cases upstream happens to ship. */
 .axi-input {
   width: 100%;
-  padding: 11px 12px;
+  padding: var(--axi-input-pad, 11px 12px);
   background: var(--axi-ground);
   border: var(--axi-border-control) solid var(--axi-ink-line);
   border-radius: var(--axi-radius-sm);
   color: var(--axi-text);
   font: var(--axi-t-label);
-  font-size: 14px;
+  font-size: var(--axi-input-size, 14px);
 }
 .axi-input::placeholder { color: var(--axi-text-faint); font-weight: 500; }
 
@@ -1411,7 +1457,7 @@ textarea.axi-input {
    not a form control standing on a page. No focus ring: the palette opens with
    the caret already here, so a permanent outline says nothing, and it would
    argue with the one mark that does - the accent on the cursor row. */
-.axi-palette__bar .axi-input { padding-top: 7px; padding-bottom: 7px; font-size: 13px; }
+.axi-palette__bar .axi-input { --axi-input-pad: 7px 12px; --axi-input-size: 13px; }
 .axi-palette__bar .axi-input:focus-visible { outline: none; }
 .axi-palette__filters { display: flex; align-items: center; gap: 6px; margin-top: 8px; }
 /* What the list is not showing. Meta, at the end of the filter row, because it

package/docs/RULES.md

@@ -260,12 +260,27 @@ there is no object, only a mark.
 
 They live in `src/utilities.css`, last in the cascade, which is how a single
 class overrules the component it sits inside without `!important`. That places
-an obligation on components in the other direction: **a component's base rules
-may not out-rank its own modifiers.** A rule written `.axi-table td` weighs a
-class and a type, so it silently defeats both `.axi-table__num` and any ink a
-consumer puts on the cell — the fix is `:where()` around the element, which
-spends no specificity. Where a component holds a consumer's content, wrap the
-element part.
+an obligation on components in the other direction: **a component's base and
+state rules may not out-rank its own modifiers.** A rule written `.axi-table td`
+weighs a class and a type, so it silently defeats both `.axi-table__num` and any
+ink a consumer puts on the cell — the fix is `:where()` around the element,
+which spends no specificity. Where a component holds a consumer's content, wrap
+the element part.
+
+A pseudo-class does the same arithmetic. `.axi-btn:hover` weighs two classes, so
+a button written `class="axi-btn axi-ink-danger"` was danger red at rest and
+plain white under the cursor: the verdict vanishing at the moment the reader
+reaches for it. Where a state rule restates a colour the consumer might have
+meant to set — a generic control's hover brighten, which applies to whatever has
+not been told what it is — wrap the state: `.axi-btn:where(:hover)`. The
+brighten becomes the fallback it always was.
+
+Two things this does not apply to. A colour that *is* the state's meaning stays
+at full weight, because there is nothing for an ink to add and an ink reaching it
+would be wrong: a selected rail item, a palette's cursor row, a pressed pill. And
+a colour that is a fill's contrast pair — `.axi-btn--primary`'s accent ink — stays
+too, because an ink there would put a status colour on the accent block and cost
+the label its legibility, which is rule 5's reason for the chip.
 
 ## 7. The diamond is the family motif
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@axiapps/axi-design",
-  "version": "1.28.0",
+  "version": "1.30.0",
   "description": "The design language for the axi suite — flat and outlined, dark, drawn in saturated ink.",
   "type": "module",
   "license": "MIT",

package/src/primitives.css

@@ -100,13 +100,15 @@ button.axi-panel--tile:hover,
 /* ---------- button ---------- */
 .axi-btn {
   display: inline-flex; align-items: center; gap: 8px;
-  padding: 12px 20px;
+  padding: var(--axi-btn-pad, 12px 20px);
   border: var(--axi-border-control) solid var(--axi-ink-line);
   border-radius: var(--axi-radius-sm);
   background: var(--axi-ground);
   color: var(--axi-text-dim);
   font: var(--axi-t-label);
   letter-spacing: var(--axi-ls-label);
+  /* After the `font` shorthand, which sets 13px and would otherwise reset it. */
+  font-size: var(--axi-btn-size, 13px);
   text-transform: uppercase;
   text-decoration: none;
   cursor: pointer;
@@ -114,8 +116,18 @@ button.axi-panel--tile:hover,
 }
 /* Hover lifts. Nothing in this language fades or glows: the block deepens and
    the element moves against it, which reads instantly even in peripheral
-   vision and costs no colour. */
-.axi-btn:hover {
+   vision and costs no colour.
+
+   :where() around the state, not decoration. `.axi-btn:hover` weighs two
+   classes, so it beat the ink layer's one and a button written
+   `class="axi-btn axi-ink-danger"` went from danger red to plain white under
+   the cursor - the verdict disappearing at the moment the reader reaches for
+   it. That is rule 6's "a component may not out-rank its own modifiers" with
+   a pseudo-class doing the out-ranking instead of an element, and it wants the
+   same fix. The dim-to-plain brighten still happens: it is the fallback now,
+   not an override, so it applies to exactly the buttons that have not been
+   told what colour they are. */
+.axi-btn:where(:hover) {
   color: var(--axi-text);
   box-shadow: var(--axi-shadow-control);
   transform: translate(-2px, -2px);
@@ -128,13 +140,33 @@ button.axi-panel--tile:hover,
 /* The one button that rests with a block already under it, so the generic
    hover's translate alone would move element and block together and leave the
    lower-right edge where it started - the "grows rather than lifts" failure
-   rule 4 warns about. It lifts the way a panel does: the block deepens too. */
+   rule 4 warns about. It lifts the way a panel does: the block deepens too.
+
+   Not wrapped in :where() the way the generic hover is: this colour is the
+   accent fill's contrast pair, not a default a consumer might mean to replace.
+   An ink reaching it would put a status colour on top of the accent block and
+   the label would stop being legible, which is rule 5's reason for the chip. */
 .axi-btn--primary:hover {
   color: var(--axi-accent-ink);
   box-shadow: var(--axi-shadow-control-hover);
 }
 .axi-btn--ghost { background: transparent; }
 .axi-btn--dashed { background: transparent; border-style: dashed; }
+/* Three sizes, because one was a fiction. A language that ships a single
+   button leaves every dense place in an app - a filter beside 11px type, a
+   toolbar, a row of controls in a card header - to spell its own padding and
+   font-size in utilities, and at that point the button is only borrowing the
+   border. The steps are named rather than left to the knobs for the same
+   reason .axi-table--dense is: a consumer saying "this is the small one"
+   should not have to pick the numbers, and the numbers should move together
+   when they move.
+   The icon step is the one the language got wrong rather than omitted. An
+   icon-only button has no label to pad around, so the 20px sides meant for
+   one produced a wide rectangle around a single glyph - visible in this
+   language's own gallery, in the example titled "Alone in a button". */
+.axi-btn--sm   { --axi-btn-pad: 8px 13px; --axi-btn-size: 12px; }
+.axi-btn--xs   { --axi-btn-pad: 5px 9px;  --axi-btn-size: 11px; }
+.axi-btn--icon { --axi-btn-pad: 7px; }
 
 /* ---------- pill ---------- */
 /* A filter toggle. Its pressed state fills with whatever colour the consumer
@@ -155,7 +187,10 @@ button.axi-panel--tile:hover,
   cursor: pointer;
   transition: transform .1s, box-shadow .1s;
 }
-.axi-pill:hover {
+/* :where() for the same reason the button's hover has it - the brighten is
+   what a pill that has not been told its colour falls back to, not an override
+   of one that has. See rule 6's addendum. */
+.axi-pill:where(:hover) {
   color: var(--axi-text);
   box-shadow: var(--axi-shadow-control);
   transform: translate(-2px, -2px);
@@ -165,11 +200,14 @@ button.axi-panel--tile:hover,
   color: var(--axi-accent-ink);
   box-shadow: var(--axi-shadow-control);
 }
-/* Spelled out rather than left to source order: `.axi-pill:hover` and
-   `.axi-pill[aria-pressed="true"]` have identical specificity, so without this
-   rule a pressed pill under the cursor kept its pressed block while still
-   taking the hover's translate - a slide, not a lift, decided by which rule
-   happened to come last in the file. A pressed pill keeps its fill and lifts. */
+/* Spelled out rather than left to the cascade. This was originally about equal
+   specificity - the two rules weighed the same, so which one a pressed pill
+   under the cursor took was decided by file order. The hover's :where() ended
+   the tie in the pressed rule's favour, and made this rule matter more rather
+   than less: `transform` is set only by the hover, so a pressed pill would take
+   its own fill and block from the higher-weight rule while still taking the
+   hover's translate - a slide, not a lift, which is the failure rule 4 names.
+   A pressed pill keeps its fill and lifts. */
 .axi-pill[aria-pressed="true"]:hover {
   background: var(--axi-pill-fill, var(--axi-accent));
   color: var(--axi-accent-ink);
@@ -288,15 +326,23 @@ button.axi-panel--tile:hover,
 .axi-diamond--series { background: var(--axi-series, var(--axi-accent)); }
 
 /* ---------- input ---------- */
+/* Two knobs rather than one fixed size, for the same reason --axi-well-pad
+   exists: a field is used at two scales. A form control standing on a page is
+   the 14px default; a filter sitting in a section header or a row in a bar is
+   smaller, because there it is furniture next to 11px type rather than the
+   thing the page is for. The alternative is what this file did before - a
+   context selector per place that wanted the small one (.axi-palette__bar
+   .axi-input, still the only one upstream needs) - and that does not scale
+   past the cases upstream happens to ship. */
 .axi-input {
   width: 100%;
-  padding: 11px 12px;
+  padding: var(--axi-input-pad, 11px 12px);
   background: var(--axi-ground);
   border: var(--axi-border-control) solid var(--axi-ink-line);
   border-radius: var(--axi-radius-sm);
   color: var(--axi-text);
   font: var(--axi-t-label);
-  font-size: 14px;
+  font-size: var(--axi-input-size, 14px);
 }
 .axi-input::placeholder { color: var(--axi-text-faint); font-weight: 500; }
 

package/src/shells.css

@@ -439,7 +439,7 @@
    not a form control standing on a page. No focus ring: the palette opens with
    the caret already here, so a permanent outline says nothing, and it would
    argue with the one mark that does - the accent on the cursor row. */
-.axi-palette__bar .axi-input { padding-top: 7px; padding-bottom: 7px; font-size: 13px; }
+.axi-palette__bar .axi-input { --axi-input-pad: 7px 12px; --axi-input-size: 13px; }
 .axi-palette__bar .axi-input:focus-visible { outline: none; }
 .axi-palette__filters { display: flex; align-items: center; gap: 6px; margin-top: 8px; }
 /* What the list is not showing. Meta, at the end of the filter row, because it