@fusion.dev/helix-headless 0.16.3 → 0.16.5

package/custom-elements.json

@@ -2330,12 +2330,22 @@
               "kind": "field",
               "name": "value",
               "type": {
-                "text": "string"
+                "text": "number | string"
               },
               "default": "''",
-              "description": "The count or short text to show.\n\nAbsent shows a dot, zero shows nothing.",
+              "description": "The count or short text to show.\n\nAbsent shows a dot, zero shows nothing.\n\n**A string, and a number is taken anyway.** What this shows is usually a\ncount, so `value={unread}` is the first thing a React consumer writes, and\na property assignment does not go through the attribute converter that\nwould have made it a string. Read raw it went straight into\n`this.value.trim()`, which threw inside `render` and left the mark showing\nwhatever it had last: measured, a badge set to the number 2 stayed an 8px\ndot with no digit in it, and the console carried\n`TypeError: this.value.trim is not a function`. A component whose whole job\nis showing a count must not lose the count for being handed one.",
               "attribute": "value"
             },
+            {
+              "kind": "field",
+              "name": "given",
+              "type": {
+                "text": "string"
+              },
+              "privacy": "private",
+              "description": "The value as text, whatever it was set to.",
+              "readonly": true
+            },
             {
               "kind": "field",
               "name": "blank",
@@ -2551,10 +2561,10 @@
             {
               "name": "value",
               "type": {
-                "text": "string"
+                "text": "number | string"
               },
               "default": "''",
-              "description": "The count or short text to show.\n\nAbsent shows a dot, zero shows nothing.",
+              "description": "The count or short text to show.\n\nAbsent shows a dot, zero shows nothing.\n\n**A string, and a number is taken anyway.** What this shows is usually a\ncount, so `value={unread}` is the first thing a React consumer writes, and\na property assignment does not go through the attribute converter that\nwould have made it a string. Read raw it went straight into\n`this.value.trim()`, which threw inside `render` and left the mark showing\nwhatever it had last: measured, a badge set to the number 2 stayed an 8px\ndot with no digit in it, and the console carried\n`TypeError: this.value.trim is not a function`. A component whose whole job\nis showing a count must not lose the count for being handed one.",
               "fieldName": "value"
             }
           ],
@@ -41012,7 +41022,7 @@
                   "text": "TemplateResult | typeof nothing"
                 }
               },
-              "description": "The control that removes the item, with the mark a consumer can replace.\n\n**A method rather than markup inside `render`, and the slot moves with\nit.** A fallback answers a consumer and a seam answers the tier above, which\nare different people: the styled tier wants an icon here, and with the slot\nwritten inline the only way to change it is to reimplement the whole\ntemplate. Moving only the fallback out is not enough: the slot is the thing\na tier redraws.\n\n**The mark is drawn rather than typed, which is what lets it align.** A\ncharacter such as `&times;` is placed by its font rather than by its box:\nmeasured against the ghost button beside it at 8x, the cross carried 6\npixels of ink to the label's 9.5 and sat 1.5 pixels below its center, in two\nboxes whose own centers agreed to a tenth of a pixel. No stylesheet can\ncorrect that, because the offset is inside the glyph. An `<svg>` is centered\non its own viewBox, so it lands where the box says and takes the icon step\nthe row is already set in. It is the `x` the Tag's dismiss draws, so two\ncontrols that mean \"take this away\" are one mark."
+              "description": "The control that removes the item, with the mark a consumer can replace.\n\n**A method rather than markup inside `render`, and the slot moves with\nit.** A fallback answers a consumer and a seam answers the tier above, which\nare different people: the styled tier wants an icon here, and with the slot\nwritten inline the only way to change it is to reimplement the whole\ntemplate. Moving only the fallback out is not enough: the slot is the thing\na tier redraws.\n\n**The mark is drawn rather than typed, which is what lets it align.** A\ncharacter such as `&times;` is placed by its font rather than by its box:\nmeasured against the ghost button beside it at 8x, the cross carried 6\npixels of ink to the label's 9.5 and sat 1.5 pixels below its center, in two\nboxes whose own centers agreed to a tenth of a pixel. No stylesheet can\ncorrect that, because the offset is inside the glyph. An `<svg>` is centered\non its own viewBox, so it lands where the box says and takes the icon step\nthe row is already set in.\n\n**A trash and not the `x` the Tag draws, because the two do not mean the\nsame thing.** A tag's cross takes a token off a field the reader is still\nfilling in, and putting it back is retyping a word. A notification is the\nonly copy of something that happened, and this removes it from the feed for\ngood, so the mark is the one every other interface uses for that and the\nink is `danger`. It is only ever on screen while the row is hovered or\nfocused, so a feed of twenty is not a column of red."
             },
             {
               "kind": "method",
@@ -75760,7 +75770,7 @@
                 "text": "string"
               },
               "default": "''",
-              "description": "Controls beyond the ones every player has, named in the order they appear.\n\nA list rather than a property apiece. A bar is a row with a budget, and a\nboolean per feature invites a consumer to switch all of them on: naming\nthem makes the row a decision, and makes the order theirs. Anything\nunrecognized is skipped rather than throwing, since the list is markup and\na typo should cost a control, not a page.\n\n`pip` is offered only where the platform has it, checked rather than\nassumed: it is absent on iPhone and behind a flag in Firefox, and a button\nthat cannot work is worse than one that is not there.\n\nThe names are `speed`, `pip`, `remote` and `download`.\n\n**`download` is named and never assumed.** Offering the file is a decision\nabout the content rather than about the player, and plenty of consumers\ndecline it deliberately. It is also the one control whose success is not\nours to promise: the attribute is ignored cross-origin, so a file served\nfrom somewhere else opens rather than saves, which is the browser's rule\nand not something a player can work around.",
+              "description": "Controls beyond the ones every player has, named in the order they appear.\n\nA list rather than a property apiece. A bar is a row with a budget, and a\nboolean per feature invites a consumer to switch all of them on: naming\nthem makes the row a decision, and makes the order theirs. Anything\nunrecognized is skipped rather than throwing, since the list is markup and\na typo should cost a control, not a page.\n\n`pip` is offered only where the platform has it, checked rather than\nassumed: it is absent on iPhone and behind a flag in Firefox, and a button\nthat cannot work is worse than one that is not there.\n\nThe names are `speed`, `pip`, `remote`, `download`, `rewind`, `forward`,\n`previous` and `next`.\n\n**`previous` and `next` do nothing to the video, and are offered anyway.**\nThey announce `helix-previous` and `helix-next` and stop there, so what\nthey move is whatever holds the set, which is what `VideoPlaylist` listens\nfor. A player standing alone therefore draws a pair of controls that change\nnothing, and that is deliberate: a player cannot know whether it is inside\na set, and one that hid them until it could prove there was one would be a\nplayer that never offers them. Name them where something is listening.\n\n**`download` is named and never assumed.** Offering the file is a decision\nabout the content rather than about the player, and plenty of consumers\ndecline it deliberately. It is also the one control whose success is not\nours to promise: the attribute is ignored cross-origin, so a file served\nfrom somewhere else opens rather than saves, which is the browser's rule\nand not something a player can work around.",
               "attribute": "extra-controls"
             },
             {
@@ -76916,7 +76926,7 @@
                 "text": "string"
               },
               "default": "''",
-              "description": "Controls beyond the ones every player has, named in the order they appear.\n\nA list rather than a property apiece. A bar is a row with a budget, and a\nboolean per feature invites a consumer to switch all of them on: naming\nthem makes the row a decision, and makes the order theirs. Anything\nunrecognized is skipped rather than throwing, since the list is markup and\na typo should cost a control, not a page.\n\n`pip` is offered only where the platform has it, checked rather than\nassumed: it is absent on iPhone and behind a flag in Firefox, and a button\nthat cannot work is worse than one that is not there.\n\nThe names are `speed`, `pip`, `remote` and `download`.\n\n**`download` is named and never assumed.** Offering the file is a decision\nabout the content rather than about the player, and plenty of consumers\ndecline it deliberately. It is also the one control whose success is not\nours to promise: the attribute is ignored cross-origin, so a file served\nfrom somewhere else opens rather than saves, which is the browser's rule\nand not something a player can work around.",
+              "description": "Controls beyond the ones every player has, named in the order they appear.\n\nA list rather than a property apiece. A bar is a row with a budget, and a\nboolean per feature invites a consumer to switch all of them on: naming\nthem makes the row a decision, and makes the order theirs. Anything\nunrecognized is skipped rather than throwing, since the list is markup and\na typo should cost a control, not a page.\n\n`pip` is offered only where the platform has it, checked rather than\nassumed: it is absent on iPhone and behind a flag in Firefox, and a button\nthat cannot work is worse than one that is not there.\n\nThe names are `speed`, `pip`, `remote`, `download`, `rewind`, `forward`,\n`previous` and `next`.\n\n**`previous` and `next` do nothing to the video, and are offered anyway.**\nThey announce `helix-previous` and `helix-next` and stop there, so what\nthey move is whatever holds the set, which is what `VideoPlaylist` listens\nfor. A player standing alone therefore draws a pair of controls that change\nnothing, and that is deliberate: a player cannot know whether it is inside\na set, and one that hid them until it could prove there was one would be a\nplayer that never offers them. Name them where something is listening.\n\n**`download` is named and never assumed.** Offering the file is a decision\nabout the content rather than about the player, and plenty of consumers\ndecline it deliberately. It is also the one control whose success is not\nours to promise: the attribute is ignored cross-origin, so a file served\nfrom somewhere else opens rather than saves, which is the browser's rule\nand not something a player can work around.",
               "fieldName": "extraControls"
             },
             {

package/dist/badge/root/badge-root.d.ts

@@ -46,8 +46,20 @@ export declare class HelixHeadlessBadge extends HelixElement {
      * The count or short text to show.
      *
      * Absent shows a dot, zero shows nothing.
+     *
+     * **A string, and a number is taken anyway.** What this shows is usually a
+     * count, so `value={unread}` is the first thing a React consumer writes, and
+     * a property assignment does not go through the attribute converter that
+     * would have made it a string. Read raw it went straight into
+     * `this.value.trim()`, which threw inside `render` and left the mark showing
+     * whatever it had last: measured, a badge set to the number 2 stayed an 8px
+     * dot with no digit in it, and the console carried
+     * `TypeError: this.value.trim is not a function`. A component whose whole job
+     * is showing a count must not lose the count for being handed one.
      */
-    value: string;
+    value: number | string;
+    /** The value as text, whatever it was set to. */
+    private get given();
     /** Whether the value counts nothing, in which case there is no mark. */
     private get blank();
     /** What the indicator reads, once the cap has been applied. */

package/dist/badge/root/badge-root.js

@@ -13,15 +13,18 @@ let HelixHeadlessBadge = class HelixHeadlessBadge extends HelixElement {
         this.label = '';
         this.value = '';
     }
+    get given() {
+        return String(this.value ?? '');
+    }
     get blank() {
-        return this.value.trim() !== '' && Number(this.value) === 0;
+        return this.given.trim() !== '' && Number(this.given) === 0;
     }
     get text() {
-        const count = Number(this.value);
+        const count = Number(this.given);
         if (this.max !== undefined && Number.isFinite(count) && count > this.max) {
             return `${this.max}+`;
         }
-        return this.value;
+        return this.given;
     }
     render() {
         const blank = this.blank;

package/dist/notifications/notification/notification.d.ts

@@ -146,8 +146,15 @@ export declare class HelixHeadlessNotification extends HelixElement {
      * boxes whose own centers agreed to a tenth of a pixel. No stylesheet can
      * correct that, because the offset is inside the glyph. An `<svg>` is centered
      * on its own viewBox, so it lands where the box says and takes the icon step
-     * the row is already set in. It is the `x` the Tag's dismiss draws, so two
-     * controls that mean "take this away" are one mark.
+     * the row is already set in.
+     *
+     * **A trash and not the `x` the Tag draws, because the two do not mean the
+     * same thing.** A tag's cross takes a token off a field the reader is still
+     * filling in, and putting it back is retyping a word. A notification is the
+     * only copy of something that happened, and this removes it from the feed for
+     * good, so the mark is the one every other interface uses for that and the
+     * ink is `danger`. It is only ever on screen while the row is hovered or
+     * focused, so a feed of twenty is not a column of red.
      */
     protected renderDismiss(): TemplateResult | typeof nothing;
     /**

package/dist/notifications/notification/notification.js

@@ -5,7 +5,7 @@ var __decorate = (this && this.__decorate) || function (decorators, target, key,
     return c > 3 && r && Object.defineProperty(target, key, r), r;
 };
 import { customElement, HelixDismissEvent, HelixElement, HelixReadEvent, hostAria, requestChange, slotFilled, } from '@fusion.dev/helix-core';
-import { x } from '@fusion.dev/helix-icons';
+import { trash } from '@fusion.dev/helix-icons';
 import { nothing } from 'lit';
 import { property } from 'lit/decorators.js';
 import { unsafeSVG } from 'lit/directives/unsafe-svg.js';
@@ -83,9 +83,9 @@ let HelixHeadlessNotification = class HelixHeadlessNotification extends HelixEle
           data-glyph
           fill="currentColor"
           part="dismiss-mark"
-          viewBox=${x.viewBox}
+          viewBox=${trash.viewBox}
         >
-          ${unsafeSVG(x.content)}
+          ${unsafeSVG(trash.content)}
         </svg>
       </slot>
     </button>`;

package/dist/video/root/video-root.d.ts

@@ -159,7 +159,16 @@ export declare class HelixHeadlessVideo extends HelixElement {
      * assumed: it is absent on iPhone and behind a flag in Firefox, and a button
      * that cannot work is worse than one that is not there.
      *
-     * The names are `speed`, `pip`, `remote` and `download`.
+     * The names are `speed`, `pip`, `remote`, `download`, `rewind`, `forward`,
+     * `previous` and `next`.
+     *
+     * **`previous` and `next` do nothing to the video, and are offered anyway.**
+     * They announce `helix-previous` and `helix-next` and stop there, so what
+     * they move is whatever holds the set, which is what `VideoPlaylist` listens
+     * for. A player standing alone therefore draws a pair of controls that change
+     * nothing, and that is deliberate: a player cannot know whether it is inside
+     * a set, and one that hid them until it could prove there was one would be a
+     * player that never offers them. Name them where something is listening.
      *
      * **`download` is named and never assumed.** Offering the file is a decision
      * about the content rather than about the player, and plenty of consumers

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@fusion.dev/helix-headless",
   "description": "Headless component tier. Structure, accessibility, state, and form participation. No styling.",
-  "version": "0.16.3",
+  "version": "0.16.5",
   "license": "MIT",
   "author": "Ross Sheppard <ross.sheppard@fusion.dev>",
   "repository": {
@@ -45,14 +45,14 @@
   },
   "bugs": "https://github.com/project-fusion/fusion/issues",
   "dependencies": {
-    "@fusion.dev/helix-core": "0.16.3",
-    "@fusion.dev/helix-icons": "0.16.3",
+    "@fusion.dev/helix-core": "0.16.5",
+    "@fusion.dev/helix-icons": "0.16.5",
     "uqr": "^0.1.3"
   },
   "devDependencies": {
     "@custom-elements-manifest/analyzer": "^0.11.0",
-    "@fusion.dev/helix-cem": "0.16.3",
-    "@fusion.dev/helix-testing": "0.16.3",
+    "@fusion.dev/helix-cem": "0.16.5",
+    "@fusion.dev/helix-testing": "0.16.5",
     "@fusion.dev/scripts": "0.0.0-dev",
     "@happy-dom/global-registrator": "^20.0.0",
     "@lit-labs/ssr": "^3.3.0",

package/types/jsx.d.ts

@@ -802,7 +802,17 @@ Past it the indicator reads `{max}+`. */
   max?: (HelixHeadlessBadge["max"]) | undefined;
   /** The count or short text to show.
 
-Absent shows a dot, zero shows nothing. */
+Absent shows a dot, zero shows nothing.
+
+**A string, and a number is taken anyway.** What this shows is usually a
+count, so `value={unread}` is the first thing a React consumer writes, and
+a property assignment does not go through the attribute converter that
+would have made it a string. Read raw it went straight into
+`this.value.trim()`, which threw inside `render` and left the mark showing
+whatever it had last: measured, a badge set to the number 2 stayed an 8px
+dot with no digit in it, and the console carried
+`TypeError: this.value.trim is not a function`. A component whose whole job
+is showing a count must not lose the count for being handed one. */
   value?: (HelixHeadlessBadge["value"]) | undefined;
 };
 
@@ -817,7 +827,17 @@ Past it the indicator reads `{max}+`. */
   "prop:max"?: (HelixHeadlessBadge["max"]) | undefined;
   /** The count or short text to show.
 
-Absent shows a dot, zero shows nothing. */
+Absent shows a dot, zero shows nothing.
+
+**A string, and a number is taken anyway.** What this shows is usually a
+count, so `value={unread}` is the first thing a React consumer writes, and
+a property assignment does not go through the attribute converter that
+would have made it a string. Read raw it went straight into
+`this.value.trim()`, which threw inside `render` and left the mark showing
+whatever it had last: measured, a badge set to the number 2 stayed an 8px
+dot with no digit in it, and the console carried
+`TypeError: this.value.trim is not a function`. A component whose whole job
+is showing a count must not lose the count for being handed one. */
   "prop:value"?: (HelixHeadlessBadge["value"]) | undefined;
 
   /** Set the innerHTML of the element */
@@ -15173,7 +15193,16 @@ a typo should cost a control, not a page.
 assumed: it is absent on iPhone and behind a flag in Firefox, and a button
 that cannot work is worse than one that is not there.
 
-The names are `speed`, `pip`, `remote` and `download`.
+The names are `speed`, `pip`, `remote`, `download`, `rewind`, `forward`,
+`previous` and `next`.
+
+**`previous` and `next` do nothing to the video, and are offered anyway.**
+They announce `helix-previous` and `helix-next` and stop there, so what
+they move is whatever holds the set, which is what `VideoPlaylist` listens
+for. A player standing alone therefore draws a pair of controls that change
+nothing, and that is deliberate: a player cannot know whether it is inside
+a set, and one that hid them until it could prove there was one would be a
+player that never offers them. Name them where something is listening.
 
 **`download` is named and never assumed.** Offering the file is a decision
 about the content rather than about the player, and plenty of consumers
@@ -15194,7 +15223,16 @@ a typo should cost a control, not a page.
 assumed: it is absent on iPhone and behind a flag in Firefox, and a button
 that cannot work is worse than one that is not there.
 
-The names are `speed`, `pip`, `remote` and `download`.
+The names are `speed`, `pip`, `remote`, `download`, `rewind`, `forward`,
+`previous` and `next`.
+
+**`previous` and `next` do nothing to the video, and are offered anyway.**
+They announce `helix-previous` and `helix-next` and stop there, so what
+they move is whatever holds the set, which is what `VideoPlaylist` listens
+for. A player standing alone therefore draws a pair of controls that change
+nothing, and that is deliberate: a player cannot know whether it is inside
+a set, and one that hid them until it could prove there was one would be a
+player that never offers them. Name them where something is listening.
 
 **`download` is named and never assumed.** Offering the file is a decision
 about the content rather than about the player, and plenty of consumers
@@ -15402,7 +15440,16 @@ a typo should cost a control, not a page.
 assumed: it is absent on iPhone and behind a flag in Firefox, and a button
 that cannot work is worse than one that is not there.
 
-The names are `speed`, `pip`, `remote` and `download`.
+The names are `speed`, `pip`, `remote`, `download`, `rewind`, `forward`,
+`previous` and `next`.
+
+**`previous` and `next` do nothing to the video, and are offered anyway.**
+They announce `helix-previous` and `helix-next` and stop there, so what
+they move is whatever holds the set, which is what `VideoPlaylist` listens
+for. A player standing alone therefore draws a pair of controls that change
+nothing, and that is deliberate: a player cannot know whether it is inside
+a set, and one that hid them until it could prove there was one would be a
+player that never offers them. Name them where something is listening.
 
 **`download` is named and never assumed.** Offering the file is a decision
 about the content rather than about the player, and plenty of consumers
@@ -15423,7 +15470,16 @@ a typo should cost a control, not a page.
 assumed: it is absent on iPhone and behind a flag in Firefox, and a button
 that cannot work is worse than one that is not there.
 
-The names are `speed`, `pip`, `remote` and `download`.
+The names are `speed`, `pip`, `remote`, `download`, `rewind`, `forward`,
+`previous` and `next`.
+
+**`previous` and `next` do nothing to the video, and are offered anyway.**
+They announce `helix-previous` and `helix-next` and stop there, so what
+they move is whatever holds the set, which is what `VideoPlaylist` listens
+for. A player standing alone therefore draws a pair of controls that change
+nothing, and that is deliberate: a player cannot know whether it is inside
+a set, and one that hid them until it could prove there was one would be a
+player that never offers them. Name them where something is listening.
 
 **`download` is named and never assumed.** Offering the file is a decision
 about the content rather than about the player, and plenty of consumers
@@ -16143,6 +16199,16 @@ export type CustomElements = {
    * - `value`: The count or short text to show.
    *
    * Absent shows a dot, zero shows nothing.
+   *
+   * **A string, and a number is taken anyway.** What this shows is usually a
+   * count, so `value={unread}` is the first thing a React consumer writes, and
+   * a property assignment does not go through the attribute converter that
+   * would have made it a string. Read raw it went straight into
+   * `this.value.trim()`, which threw inside `render` and left the mark showing
+   * whatever it had last: measured, a badge set to the number 2 stayed an 8px
+   * dot with no digit in it, and the console carried
+   * `TypeError: this.value.trim is not a function`. A component whose whole job
+   * is showing a count must not lose the count for being handed one.
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
    * **Named `whenSettled` because `settled` is taken four times over**, by
@@ -29753,7 +29819,16 @@ export type CustomElements = {
    * assumed: it is absent on iPhone and behind a flag in Firefox, and a button
    * that cannot work is worse than one that is not there.
    *
-   * The names are `speed`, `pip`, `remote` and `download`.
+   * The names are `speed`, `pip`, `remote`, `download`, `rewind`, `forward`,
+   * `previous` and `next`.
+   *
+   * **`previous` and `next` do nothing to the video, and are offered anyway.**
+   * They announce `helix-previous` and `helix-next` and stop there, so what
+   * they move is whatever holds the set, which is what `VideoPlaylist` listens
+   * for. A player standing alone therefore draws a pair of controls that change
+   * nothing, and that is deliberate: a player cannot know whether it is inside
+   * a set, and one that hid them until it could prove there was one would be a
+   * player that never offers them. Name them where something is listening.
    *
    * **`download` is named and never assumed.** Offering the file is a decision
    * about the content rather than about the player, and plenty of consumers
@@ -30565,6 +30640,16 @@ export type CustomElementsSolidJs = {
    * - `value`: The count or short text to show.
    *
    * Absent shows a dot, zero shows nothing.
+   *
+   * **A string, and a number is taken anyway.** What this shows is usually a
+   * count, so `value={unread}` is the first thing a React consumer writes, and
+   * a property assignment does not go through the attribute converter that
+   * would have made it a string. Read raw it went straight into
+   * `this.value.trim()`, which threw inside `render` and left the mark showing
+   * whatever it had last: measured, a badge set to the number 2 stayed an 8px
+   * dot with no digit in it, and the console carried
+   * `TypeError: this.value.trim is not a function`. A component whose whole job
+   * is showing a count must not lose the count for being handed one.
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
    * **Named `whenSettled` because `settled` is taken four times over**, by
@@ -44434,7 +44519,16 @@ export type CustomElementsSolidJs = {
    * assumed: it is absent on iPhone and behind a flag in Firefox, and a button
    * that cannot work is worse than one that is not there.
    *
-   * The names are `speed`, `pip`, `remote` and `download`.
+   * The names are `speed`, `pip`, `remote`, `download`, `rewind`, `forward`,
+   * `previous` and `next`.
+   *
+   * **`previous` and `next` do nothing to the video, and are offered anyway.**
+   * They announce `helix-previous` and `helix-next` and stop there, so what
+   * they move is whatever holds the set, which is what `VideoPlaylist` listens
+   * for. A player standing alone therefore draws a pair of controls that change
+   * nothing, and that is deliberate: a player cannot know whether it is inside
+   * a set, and one that hid them until it could prove there was one would be a
+   * player that never offers them. Name them where something is listening.
    *
    * **`download` is named and never assumed.** Offering the file is a decision
    * about the content rather than about the player, and plenty of consumers

package/types/vue.d.ts

@@ -426,7 +426,17 @@ Past it the indicator reads `{max}+`. */
   max?: (HelixHeadlessBadge["max"]) | undefined;
   /** The count or short text to show.
 
-Absent shows a dot, zero shows nothing. */
+Absent shows a dot, zero shows nothing.
+
+**A string, and a number is taken anyway.** What this shows is usually a
+count, so `value={unread}` is the first thing a React consumer writes, and
+a property assignment does not go through the attribute converter that
+would have made it a string. Read raw it went straight into
+`this.value.trim()`, which threw inside `render` and left the mark showing
+whatever it had last: measured, a badge set to the number 2 stayed an 8px
+dot with no digit in it, and the console carried
+`TypeError: this.value.trim is not a function`. A component whose whole job
+is showing a count must not lose the count for being handed one. */
   value?: (HelixHeadlessBadge["value"]) | undefined;
 };
 
@@ -7819,7 +7829,16 @@ a typo should cost a control, not a page.
 assumed: it is absent on iPhone and behind a flag in Firefox, and a button
 that cannot work is worse than one that is not there.
 
-The names are `speed`, `pip`, `remote` and `download`.
+The names are `speed`, `pip`, `remote`, `download`, `rewind`, `forward`,
+`previous` and `next`.
+
+**`previous` and `next` do nothing to the video, and are offered anyway.**
+They announce `helix-previous` and `helix-next` and stop there, so what
+they move is whatever holds the set, which is what `VideoPlaylist` listens
+for. A player standing alone therefore draws a pair of controls that change
+nothing, and that is deliberate: a player cannot know whether it is inside
+a set, and one that hid them until it could prove there was one would be a
+player that never offers them. Name them where something is listening.
 
 **`download` is named and never assumed.** Offering the file is a decision
 about the content rather than about the player, and plenty of consumers
@@ -7840,7 +7859,16 @@ a typo should cost a control, not a page.
 assumed: it is absent on iPhone and behind a flag in Firefox, and a button
 that cannot work is worse than one that is not there.
 
-The names are `speed`, `pip`, `remote` and `download`.
+The names are `speed`, `pip`, `remote`, `download`, `rewind`, `forward`,
+`previous` and `next`.
+
+**`previous` and `next` do nothing to the video, and are offered anyway.**
+They announce `helix-previous` and `helix-next` and stop there, so what
+they move is whatever holds the set, which is what `VideoPlaylist` listens
+for. A player standing alone therefore draws a pair of controls that change
+nothing, and that is deliberate: a player cannot know whether it is inside
+a set, and one that hid them until it could prove there was one would be a
+player that never offers them. Name them where something is listening.
 
 **`download` is named and never assumed.** Offering the file is a decision
 about the content rather than about the player, and plenty of consumers