@fusion.dev/helix 0.139.0 → 0.141.0

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@fusion.dev/helix",
   "description": "Styled component tier. Extends the headless tier with token-driven presentation.",
-  "version": "0.139.0",
+  "version": "0.141.0",
   "license": "MIT",
   "author": "Ross Sheppard <ross.sheppard@fusion.dev>",
   "repository": {
@@ -53,13 +53,13 @@
   },
   "bugs": "https://github.com/project-fusion/fusion/issues",
   "dependencies": {
-    "@fusion.dev/helix-core": "0.139.0",
-    "@fusion.dev/helix-headless": "0.139.0",
-    "@fusion.dev/helix-styles": "0.139.0"
+    "@fusion.dev/helix-core": "0.141.0",
+    "@fusion.dev/helix-headless": "0.141.0",
+    "@fusion.dev/helix-styles": "0.141.0"
   },
   "devDependencies": {
-    "@fusion.dev/helix-cem": "0.139.0",
-    "@fusion.dev/helix-testing": "0.139.0",
+    "@fusion.dev/helix-cem": "0.141.0",
+    "@fusion.dev/helix-testing": "0.141.0",
     "@fusion.dev/scripts": "0.0.0-dev",
     "@happy-dom/global-registrator": "^20.0.0",
     "@lit-labs/ssr": "^4.1.0",

package/types/jsx.d.ts

@@ -1428,8 +1428,8 @@ a small mark carrying a meaning beside something else, and the two had
 different sets for no reason anybody decided: a tag could say `success` and
 a badge could not, so a page marking a build green wrote one word on the
 chip and had no word for the count beside it. Every fill these name already
-exists and every one carries `foreground-on-accent`, so this costs a rule
-apiece and no new color.
+exists with its family's label, so this costs a rule apiece and no new
+color.
 
 **`primary` is sayable as well as the default**, which is the reason
 `Announcement` gives for its own neutral: a generated page should be able to
@@ -1467,8 +1467,8 @@ a small mark carrying a meaning beside something else, and the two had
 different sets for no reason anybody decided: a tag could say `success` and
 a badge could not, so a page marking a build green wrote one word on the
 chip and had no word for the count beside it. Every fill these name already
-exists and every one carries `foreground-on-accent`, so this costs a rule
-apiece and no new color.
+exists with its family's label, so this costs a rule apiece and no new
+color.
 
 **`primary` is sayable as well as the default**, which is the reason
 `Announcement` gives for its own neutral: a generated page should be able to
@@ -2533,9 +2533,9 @@ export type HelixCalloutProps = {
   /** What kind of attention the passage needs.
 
 `tone` is the axis for what a thing means, and this is a subset of it: a
-callout reports a status and never a brand role, so it takes four of the
-seven values. One word per axis is the whole of the registry, which is why
-there is no `severity` beside it. */
+callout reports a status, or `neutral` for an aside that reports none, and
+never a brand role, so it takes five of the seven values. One word per axis
+is the whole of the registry, which is why there is no `severity` beside it. */
   tone?: (HelixCallout["tone"]) | undefined;
 };
 
@@ -2543,9 +2543,9 @@ export type HelixCalloutSolidJsProps = {
   /** What kind of attention the passage needs.
 
 `tone` is the axis for what a thing means, and this is a subset of it: a
-callout reports a status and never a brand role, so it takes four of the
-seven values. One word per axis is the whole of the registry, which is why
-there is no `severity` beside it. */
+callout reports a status, or `neutral` for an aside that reports none, and
+never a brand role, so it takes five of the seven values. One word per axis
+is the whole of the registry, which is why there is no `severity` beside it. */
   "prop:tone"?: (HelixCallout["tone"]) | undefined;
 
   /** Set the innerHTML of the element */
@@ -28106,8 +28106,8 @@ export type CustomElements = {
    * different sets for no reason anybody decided: a tag could say `success` and
    * a badge could not, so a page marking a build green wrote one word on the
    * chip and had no word for the count beside it. Every fill these name already
-   * exists and every one carries `foreground-on-accent`, so this costs a rule
-   * apiece and no new color.
+   * exists with its family's label, so this costs a rule apiece and no new
+   * color.
    *
    * **`primary` is sayable as well as the default**, which is the reason
    * `Announcement` gives for its own neutral: a generated page should be able to
@@ -29117,7 +29117,9 @@ export type CustomElements = {
   >;
 
   /**
-   * The background is a tint of the tone's status color, mixed with `color-mix`.
+   * The background is a tint of the tone's color, mixed with `color-mix`. A
+   * `neutral` callout is drawn in the muted ink, for a note that reports no
+   * status, so it keeps to the palette whatever the brand.
    * A bar on the inline start edge also marks the tone, so it still shows in
    * grayscale and for people who do not distinguish the hues.
    *
@@ -29131,9 +29133,9 @@ export type CustomElements = {
    * - `tone`: What kind of attention the passage needs.
    *
    * `tone` is the axis for what a thing means, and this is a subset of it: a
-   * callout reports a status and never a brand role, so it takes four of the
-   * seven values. One word per axis is the whole of the registry, which is why
-   * there is no `severity` beside it.
+   * callout reports a status, or `neutral` for an aside that reports none, and
+   * never a brand role, so it takes five of the seven values. One word per axis
+   * is the whole of the registry, which is why there is no `severity` beside it.
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
    * **Named `whenSettled` because `settled` is taken four times over**, by
@@ -50304,8 +50306,8 @@ export type CustomElementsSolidJs = {
    * different sets for no reason anybody decided: a tag could say `success` and
    * a badge could not, so a page marking a build green wrote one word on the
    * chip and had no word for the count beside it. Every fill these name already
-   * exists and every one carries `foreground-on-accent`, so this costs a rule
-   * apiece and no new color.
+   * exists with its family's label, so this costs a rule apiece and no new
+   * color.
    *
    * **`primary` is sayable as well as the default**, which is the reason
    * `Announcement` gives for its own neutral: a generated page should be able to
@@ -51338,7 +51340,9 @@ export type CustomElementsSolidJs = {
   >;
 
   /**
-   * The background is a tint of the tone's status color, mixed with `color-mix`.
+   * The background is a tint of the tone's color, mixed with `color-mix`. A
+   * `neutral` callout is drawn in the muted ink, for a note that reports no
+   * status, so it keeps to the palette whatever the brand.
    * A bar on the inline start edge also marks the tone, so it still shows in
    * grayscale and for people who do not distinguish the hues.
    *
@@ -51352,9 +51356,9 @@ export type CustomElementsSolidJs = {
    * - `tone`: What kind of attention the passage needs.
    *
    * `tone` is the axis for what a thing means, and this is a subset of it: a
-   * callout reports a status and never a brand role, so it takes four of the
-   * seven values. One word per axis is the whole of the registry, which is why
-   * there is no `severity` beside it.
+   * callout reports a status, or `neutral` for an aside that reports none, and
+   * never a brand role, so it takes five of the seven values. One word per axis
+   * is the whole of the registry, which is why there is no `severity` beside it.
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
    * **Named `whenSettled` because `settled` is taken four times over**, by

package/types/vue.d.ts

@@ -770,8 +770,8 @@ a small mark carrying a meaning beside something else, and the two had
 different sets for no reason anybody decided: a tag could say `success` and
 a badge could not, so a page marking a build green wrote one word on the
 chip and had no word for the count beside it. Every fill these name already
-exists and every one carries `foreground-on-accent`, so this costs a rule
-apiece and no new color.
+exists with its family's label, so this costs a rule apiece and no new
+color.
 
 **`primary` is sayable as well as the default**, which is the reason
 `Announcement` gives for its own neutral: a generated page should be able to
@@ -1317,9 +1317,9 @@ export type HelixCalloutVueProps = {
   /** What kind of attention the passage needs.
 
 `tone` is the axis for what a thing means, and this is a subset of it: a
-callout reports a status and never a brand role, so it takes four of the
-seven values. One word per axis is the whole of the registry, which is why
-there is no `severity` beside it. */
+callout reports a status, or `neutral` for an aside that reports none, and
+never a brand role, so it takes five of the seven values. One word per axis
+is the whole of the registry, which is why there is no `severity` beside it. */
   tone?: (HelixCallout["tone"]) | undefined;
 };
 
@@ -15131,7 +15131,7 @@ export interface WcToolkitVueGlobalComponents {
     HelixButtonVueProps,
     HelixButtonVueEvents
   >;
-  /** The background is a tint of the tone's status color, mixed with 'color-mix'. A bar on the inline start edge also marks the tone, so it still shows in grayscale and for people who do not distinguish the hues.  This tier has no treatment property. 'tone' is set on the headless tier and carries the meaning, and this tier draws it. */
+  /** The background is a tint of the tone's color, mixed with 'color-mix'. A 'neutral' callout is drawn in the muted ink, for a note that reports no status, so it keeps to the palette whatever the brand. A bar on the inline start edge also marks the tone, so it still shows in grayscale and for people who do not distinguish the hues.  This tier has no treatment property. 'tone' is set on the headless tier and carries the meaning, and this tier draws it. */
   "helix-callout": DefineCustomElement<
     HelixCallout,
     HelixCalloutVueProps,