@fusion.dev/helix-headless 0.174.0 → 0.176.0

package/custom-elements.json

@@ -42953,7 +42953,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "The list is a `Listbox`, which handles filtering, the empty state, the match\nhighlight, `aria-activedescendant`, scrolling an option into view, and moving\nbetween options with the keyboard. The palette adds a dialog and a hotkey\nthat opens it.\n\nThe palette keeps no value. It is not a form control and submits nothing.\nChoosing an option dispatches `helix-select` once. To remember the last\ncommand, store it yourself. An option with `href` is a link to a page, which\nthe browser follows once the palette has closed.\n\nThe hotkey listener is on the document, so the hotkey works from anywhere on\nthe page, including inside another control's text field, whether or not the\npalette is open. `mod` means Command on a Mac and Control elsewhere, so you\nwrite one binding.\n\nWith `inline`, the palette is drawn in the page with no dialog, as a search\nover a list that is always shown.\n\n**Pages.** A command can open a page of commands of its own, as a palette\noffers \"Change theme\" and then the themes. Give the option `opens` with a\nname, and slot the page's commands as `page:` and that name:\n\n```html\n<helix-command>\n  <helix-option value=\"theme\" opens=\"theme\">Change theme</helix-option>\n  <helix-option value=\"dark\" slot=\"page:theme\">Dark</helix-option>\n  <helix-option value=\"light\" slot=\"page:theme\">Light</helix-option>\n</helix-command>\n```\n\nChoosing the opener says `helix-select` with its value, and canceling it\nkeeps the page that is shown. The list then shows the page, named by the\nopener's words, and a screen reader hears those words. Backspace in an empty\nfilter goes back, and a screen reader hears the name of the page it goes\nback to. `page` says which page is shown.\n\nThe filter is cleared when the palette closes, so each opening starts from\nthe full list. Combobox and Select do the same. As typing narrows the list, a\nscreen reader hears how many commands are left, such as \"3 commands\".\n\n**Keyboard.** Focus goes to the filter field as the palette opens, and the\nhighlight moves through the commands while you type.\n\n| Key | What it does |\n|---|---|\n| `hotkey`, Command or Control with K by default | Opens the palette from anywhere on the page, or closes it. With `inline`, puts focus in its filter field. |\n| Down, Up | Moves the highlight to the next or the previous command, round from the last to the first. |\n| Page Down, Page Up | Moves the highlight by as many commands as the list shows at once. |\n| Home, End | Move the caret in the filter field. With `home-end=\"list\"`, move the highlight to the first or the last command. |\n| Left, Right | Move the caret in the filter field. |\n| Enter | Runs the highlighted command, or follows it where it is a link, and closes the palette. On a command with `opens`, shows its page. |\n| Command or Control with Enter | Takes the highlighted command's `alternate` destination, where it has one. |\n| Backspace | In an empty filter on a page, goes back to the page before. |\n| Escape | Clears the filter. With the filter empty, closes the palette and puts focus back where it was. |\n| Tab | Stays in the palette, which is modal. With `inline`, moves on through the page. |\n\n**ARIA.** The palette is a modal `dialog` named by `label`, or with\n`inline` no dialog at all. Inside it the filter field is a text field with\n`aria-autocomplete=\"list\"`, `aria-controls` on the list, and\n`aria-activedescendant` on the highlighted command, as the field of React\nAria's `Autocomplete` is. The commands are a `listbox` of `option`s. How many commands typing left, the empty text and\nthe loading text are said in a polite live region.",
+          "description": "The list is a `Listbox`, which handles filtering, the empty state, the match\nhighlight, `aria-activedescendant`, scrolling an option into view, and moving\nbetween options with the keyboard. The palette adds a dialog and a hotkey\nthat opens it.\n\nThe palette keeps no value. It is not a form control and submits nothing.\nChoosing an option dispatches `helix-select` once. To remember the last\ncommand, store it yourself. An option with `href` is a link to a page, which\nthe browser follows once the palette has closed.\n\nThe hotkey listener is on the document, so the hotkey works from anywhere on\nthe page, including inside another control's text field, whether or not the\npalette is open. `mod` means Command on a Mac and Control elsewhere, so you\nwrite one binding.\n\nWith `inline`, the palette is drawn in the page with no dialog, as a search\nover a list that is always shown.\n\n**Pages.** A command can open a page of commands of its own, as a palette\noffers \"Change theme\" and then the themes. Give the option `opens` with a\nname, and slot the page's commands as `page:` and that name:\n\n```html\n<helix-command>\n  <helix-option value=\"theme\" opens=\"theme\">Change theme</helix-option>\n  <helix-option value=\"dark\" slot=\"page:theme\">Dark</helix-option>\n  <helix-option value=\"light\" slot=\"page:theme\">Light</helix-option>\n</helix-command>\n```\n\nChoosing the opener says `helix-select` with its value, and canceling it\nkeeps the page that is shown. The list then shows the page, named by the\nopener's words, and a screen reader hears those words. Backspace in an empty\nfilter goes back, and a screen reader hears the name of the page it goes\nback to. `page` says which page is shown.\n\nThe filter is cleared when the palette closes, so each opening starts from\nthe full list. Combobox and Select do the same. As typing narrows the list, a\nscreen reader hears how many commands are left, such as \"3 commands\".\n\n**Keyboard.** Focus goes to the filter field as the palette opens, with no\ncommand highlighted, as in React Aria's Autocomplete, so Enter runs nothing\nuntil you type or press Down. Typing highlights the first command left, and\nthe highlight moves through the commands while you type.\n\n| Key | What it does |\n|---|---|\n| `hotkey`, Command or Control with K by default | Opens the palette from anywhere on the page, or closes it. With `inline`, puts focus in its filter field. |\n| Down, Up | Moves the highlight to the next or the previous command, round from the last to the first. |\n| Page Down, Page Up | Moves the highlight by as many commands as the list shows at once. |\n| Home, End | Move the caret in the filter field. With `home-end=\"list\"`, move the highlight to the first or the last command. |\n| Left, Right | Move the caret in the filter field. |\n| Enter | Runs the highlighted command, or follows it where it is a link, and closes the palette. On a command with `opens`, shows its page. |\n| Command or Control with Enter | Takes the highlighted command's `alternate` destination, where it has one. |\n| Backspace | In an empty filter on a page, goes back to the page before. |\n| Escape | Clears the filter. With the filter empty, closes the palette and puts focus back where it was. |\n| Tab | Stays in the palette, which is modal. With `inline`, moves on through the page. |\n\n**ARIA.** The palette is a modal `dialog` named by `label`, or with\n`inline` no dialog at all. Inside it the filter field is a text field with\n`aria-autocomplete=\"list\"`, `aria-controls` on the list, and\n`aria-activedescendant` on the highlighted command, as the field of React\nAria's `Autocomplete` is. The commands are a `listbox` of `option`s. How many commands typing left, the empty text and\nthe loading text are said in a polite live region.",
           "name": "HelixHeadlessCommand",
           "cssParts": [
             {
@@ -55485,7 +55485,7 @@
                 "text": "Date"
               },
               "privacy": "private",
-              "description": "The date the tab stop sits on, which is where the arrows move from.\n\nIt has to be a date the grid actually renders, so the month is compared\nwith its year. Comparing the month alone puts the stop on the same date a\nyear away, which is rendered nowhere, and the grid is left with no tab stop\nat all and no way into it from the keyboard.\n\nEach candidate is tested in turn rather than the first one winning\noutright. Where the last date focused is in some other month, the selected\ndate still holds the stop, then today, as the APG date picker and React\nAria's calendar put it, and only with none of them in view does it fall\nto the first of the month. Measured before today was a candidate: a\ncalendar with no value opened on October 5 with its stop on \"Thursday,\nOctober 1\".",
+              "description": "The date the tab stop sits on, which is where the arrows move from.\n\nIt has to be a date the grid actually renders, so the month is compared\nwith its year. Comparing the month alone puts the stop on the same date a\nyear away, which is rendered nowhere, and the grid is left with no tab stop\nat all and no way into it from the keyboard.\n\nEach candidate is tested in turn rather than the first one winning\noutright. Where the last date focused is in some other month, the selected\ndate still holds the stop, then today, as the APG date picker and React\nAria's calendar put it, and only with none of them in view does it fall\nto the first of the month. Measured before today was a candidate: a\ncalendar with no value opened on October 5 with its stop on \"Thursday,\nOctober 1\".\n\nToday counts only where it can be chosen, and the fallback is the first\nday of the month that can, so a reader tabbing in lands on a date they can\npick. Measured before: with `min=\"2026-03-03\"`, the stop sat on \"Sunday,\nMarch 1, 2026\", unavailable. A month with nothing to choose keeps its\nfirst day, so the grid still has a way in.",
               "readonly": true
             },
             {
@@ -58816,6 +58816,46 @@
         }
       ]
     },
+    {
+      "kind": "javascript-module",
+      "path": "src/dialog/form-method.ts",
+      "declarations": [
+        {
+          "kind": "function",
+          "name": "closeOnDialogSubmit",
+          "return": {
+            "type": {
+              "text": "void"
+            }
+          },
+          "parameters": [
+            {
+              "name": "event",
+              "type": {
+                "text": "SubmitEvent"
+              }
+            },
+            {
+              "name": "close",
+              "type": {
+                "text": "(returnValue?: string) => void"
+              }
+            }
+          ],
+          "description": "Closes a shadow `<dialog>` on a `<form method=\"dialog\">` submit slotted into\nit, the way the platform closes its own. `Dialog` and `Drawer` share it.\n\n**The platform cannot find the dialog from the form.** A submit with the\n`dialog` method closes the nearest `<dialog>` ancestor, and a slotted form's\nancestors are the light DOM, where there is none. So the submit is read on\nthe host, and the submitter's `value` is the `returnValue`, as it would be.\nA form inside a `<dialog>` of its own, or with any other method, is left to\nthe platform."
+        }
+      ],
+      "exports": [
+        {
+          "kind": "js",
+          "name": "closeOnDialogSubmit",
+          "declaration": {
+            "name": "closeOnDialogSubmit",
+            "module": "src/dialog/form-method.ts"
+          }
+        }
+      ]
+    },
     {
       "kind": "javascript-module",
       "path": "src/dialog/index.ts",
@@ -59079,7 +59119,7 @@
               "name": "handleSubmit",
               "privacy": "private",
               "readonly": true,
-              "description": "A `<form method=\"dialog\">` slotted into the dialog, closed the way the\nplatform closes its own.\n\n**The platform cannot find this dialog from the form.** A submit with the\n`dialog` method closes the nearest `<dialog>` ancestor, and a slotted form's\nancestors are the light DOM, where there is none. So the submit is read\nhere, and the submitter's `value` is the `returnValue`, as it would be."
+              "description": "A `<form method=\"dialog\">` slotted into the dialog closes it."
             },
             {
               "kind": "field",
@@ -62236,6 +62276,13 @@
               },
               "description": "Describes the panel by the words at the start of its body, where nothing\nelse describes it, as `Dialog` does. An `aria-describedby` on the host\ncomes first."
             },
+            {
+              "kind": "field",
+              "name": "handleSubmit",
+              "privacy": "private",
+              "readonly": true,
+              "description": "A `<form method=\"dialog\">` slotted into the drawer closes it, as in `Dialog`."
+            },
             {
               "kind": "method",
               "name": "renderDismissIcon",
@@ -69237,14 +69284,6 @@
             "module": "src/filter-input/grammar.js"
           }
         },
-        {
-          "kind": "js",
-          "name": "*",
-          "declaration": {
-            "name": "*",
-            "module": "src/filter-input/menu/filter-menu.js"
-          }
-        },
         {
           "kind": "js",
           "name": "*",
@@ -69269,7 +69308,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "Reads the `FilterField` declarations inside it and renders a two-level menu:\nthe fields, and under each field its operators and values. The menu does not\ninterpret what a field means.\n\n```html\n<helix-headless-filter-menu label=\"Filter\">\n  <helix-headless-filter-field name=\"disposition\" label=\"Disposition\">\n    <helix-headless-option value=\"refunded\">Refunded</helix-headless-option>\n  </helix-headless-filter-field>\n</helix-headless-filter-menu>\n```\n\nThat field declares no operators, so it offers `is any of` and `is none of`,\nthe two the typed grammar supports. The menu and the typed text offer the\nsame filters because both read `FilterField.vocabulary`. Declare other\noperators on the field when you need them.\n\nTicking a value applies the filter immediately. There is no Apply button.\nEach tick fires `helix-facet` with the field's whole set of values, so\nresults narrow as the user works. Unticking the last value fires an empty\nset, which is your cue to remove the chip.\n\nThe operator is chosen in the menu. `helix-facet` carries an empty\n`operatorLabel` when the operator is the field's default, which is the value\na chip's `operator-label` expects, so the operator segment appears only for a\nnon-default choice. The menu decides this because it is the only element that\nreads both the field and its operators.\n\nAn operator's `arity` sets what appears under it:\n\n- `arity=\"none\"`, such as `is empty` or `is set`, offers no values and clears\n  any that were ticked. The operator is the whole filter.\n- `arity=\"one\"` offers the values as a single choice. Pressing another value\n  replaces the choice, and pressing the chosen value clears it.\n\n`helix-facet` includes `arity`, so you can tell an empty filter from no\nfilter.\n\nThe menu applies nothing. The chips are your markup and the rows are your\ndata, so the menu fires the event and leaves the change to you, as\n`Notification` does for a read. Call `preventDefault()` on `helix-facet` to\ncancel the change.",
+          "description": "Reads the `FilterField` declarations inside it and renders a two-level menu:\nthe fields, and under each field its operators and values. The menu does not\ninterpret what a field means.\n\n```html\n<helix-headless-filter-menu label=\"Filter\">\n  <helix-headless-filter-field name=\"disposition\" label=\"Disposition\">\n    <helix-headless-option value=\"refunded\">Refunded</helix-headless-option>\n  </helix-headless-filter-field>\n</helix-headless-filter-menu>\n```\n\nThat field declares no operators, so it offers `is any of` and `is none of`,\nthe two the typed grammar supports. The menu and the typed text offer the\nsame filters because both read `FilterField.vocabulary`. Declare other\noperators on the field when you need them.\n\nTicking a value applies the filter immediately. There is no Apply button.\nEach tick fires `helix-facet` with the field's whole set of values, so\nresults narrow as the user works. Unticking the last value fires an empty\nset, which is your cue to remove the chip.\n\nThe operator is chosen in the menu. `helix-facet` carries an empty\n`operatorLabel` when the operator is the field's default, which is the value\na chip's `operator-label` expects, so the operator segment appears only for a\nnon-default choice. The menu decides this because it is the only element that\nreads both the field and its operators.\n\nAn operator's `arity` sets what appears under it:\n\n- `arity=\"none\"`, such as `is empty` or `is set`, offers no values and clears\n  any that were ticked. The operator is the whole filter.\n- `arity=\"one\"` offers the values as a single choice. Pressing another value\n  replaces the choice, and pressing the chosen value clears it.\n\n`helix-facet` includes `arity`, so you can tell an empty filter from no\nfilter.\n\nThe menu applies nothing. The chips are your markup and the rows are your\ndata, so the menu fires the event and leaves the change to you, as\n`Notification` does for a read. Call `preventDefault()` on `helix-facet` to\ncancel the change.\n\nImported from its own entry, `@fusion.dev/helix-headless/filter-input/menu`, which registers\nit with the `Menu` it draws its pages with. The family's entry leaves it out,\nso a field without a picker does not carry `Menu`.",
           "name": "HelixHeadlessFilterMenu",
           "cssParts": [
             {
@@ -69952,6 +69991,21 @@
         }
       ]
     },
+    {
+      "kind": "javascript-module",
+      "path": "src/filter-input/menu/index.ts",
+      "declarations": [],
+      "exports": [
+        {
+          "kind": "js",
+          "name": "*",
+          "declaration": {
+            "name": "*",
+            "module": "src/filter-input/menu/filter-menu.js"
+          }
+        }
+      ]
+    },
     {
       "kind": "javascript-module",
       "path": "src/filter-input/operator/filter-operator.ts",
@@ -70437,7 +70491,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "Tokens are your own elements, slotted in. A filter can be a facet with a\nprefix, a saved query, or a range, and these belong to your model, so the\nelement does not render tokens from a list of strings. Removing a token is a\nrequest the element fires, and you apply it. Combobox works the other way:\nits tokens show a selection it owns, drawn from the options it was given.\n\n`value` is the typed text. Every keystroke fires `input` with the text on the\nelement, so a table can narrow as the user types. Backspace in an empty field\nfires `helix-dismiss` on the last token, the same event its remove control\nfires, so one handler covers the pointer and the keyboard.\n\n**What a form receives.** The text under `name`, and then one more entry\nunder `name` for each token, in the order the tokens stand:\n\n| Token | Entry |\n|---|---|\n| Any element with a `value` attribute | The value as written: `saved:mine` |\n| `FilterChip` with `name` and values | `status:open,pending` |\n| The same, with `operator=\"none\"` (what a typed `-status:` makes) | `-status:open,pending` |\n| The same, with any other `operator` except `any` | `created[after]:2024` |\n| A token with neither | Nothing |\n\nThe values are the chip's text outside its `field` and `operator` slots,\nwith the spaces around each comma removed. A server splits an entry at its\nfirst colon, reads a leading `-` as the negation, and reads a word in\nbrackets before the colon as the comparison.\n\n**Keyboard.** Focus stays in the text, which is the field's one tab stop. The\ntext names the highlighted suggestion as its `aria-activedescendant`, and the\narrow keys reach the tokens.\n\n| Key | What it does |\n|---|---|\n| Enter | Presses the highlighted suggestion. With none highlighted, reads the typed filters into chips, or submits the form when there are none. |\n| Down, Up | Moves the highlight through the suggestions, wrapping, and opens the panel. |\n| Home, End | Highlights the first or the last suggestion while the panel is open. |\n| Escape | Closes the panel and stops there, so a dialog around the field stays open. |\n| Backspace | In an empty field, asks the last token to go. |\n| Left | With the caret at the start of the text, moves to the last token's remove button. Right on a right-to-left page. |\n| Left, Right on a token | Move between the tokens, and past the last back to the text. |\n| Delete, Backspace on a token | Asks the token to go. |\n\n**Typed filters.** The field parses only the fields you declare. Write\n`FilterField` elements, usually inside the `FilterMenu` slotted into `start`,\nso the picker and the text share one set. On Enter, the field reads the text\nagainst them. `disposition:refunded,settled` and `-disposition:refunded` fire\n`helix-facet` exactly as ticking those values in the picker would, and the\nparsed text is removed. Everything else stays, so `refund tuesday\ndisposition:settled` is a filter and a search at once. Helix defines the\npunctuation and you define every word. `grammar.ts` has the full rule, so\nread it before you rely on it. A field with no `FilterField` in it parses\nnothing.\n\nA field whose values cannot be listed, such as `assignee:ada`, goes directly\ninside this element, outside the menu. It is not assigned to a slot, so\nnothing draws it and the menu has no page for it, and the grammar still reads\nit.\n\n**Suggestions.** Slot options into `suggestions` and the field shows them,\nmoves through them with the arrow keys, and presses one on Enter. The option\nfires its own `helix-select`, and you decide what choosing it means. Keys\nbefore a colon and values after it use the same panel with different\ncontents. `filter-suggestions` narrows the panel to the options whose words\nhold the term at the caret, after its colon, ignoring case and accents, and\nhides the rest. `readFilterText` is exported so you can narrow it yourself\nagainst partly typed text. While the panel is open, a reader hears how many\nsuggestions it offers. The panel opens when it has options and closes when it has\nnone, and a choice does not close it, so after picking a key you see its\nvalues next. Use `selectionStart` and `setSelectionRange` to write a\ncompletion back and put the caret after it, or the next parse reads the wrong\nterm.\n\n**State.** Three things have three different owners:\n\n- `value` is the text. The user types, the element applies it, and `input`\n  reports it. Setting `value` seeds or corrects the text, and the next\n  keystroke overwrites it, even in React. To control the value, cancel\n  `helix-before-change` and write the value you want, as with every field in\n  this library. `default-value` seeds the field.\n- `open` is the suggestions panel. Cancel `helix-before-open` or\n  `helix-before-close` to control it, and use `default-open` to seed it.\n- Tokens are your elements in a slot and hold no state. A token goes when you\n  remove it from your markup after `helix-dismiss`. A `FilterChip` naming a\n  declared field works differently, because the picker holds what is ticked\n  and removing the chip alone would leave its value ticked in the hidden\n  menu. Its dismissal is treated as the field being filtered by nothing, so\n  it fires `helix-facet` like every other change, and the chip goes when the\n  filter goes. Set `chips` and the field adds, updates, and removes those\n  chips itself, from every `helix-facet` you do not cancel.",
+          "description": "Tokens are your own elements, slotted in. A filter can be a facet with a\nprefix, a saved query, or a range, and these belong to your model, so the\nelement does not render tokens from a list of strings. Removing a token is a\nrequest the element fires, and you apply it. Combobox works the other way:\nits tokens show a selection it owns, drawn from the options it was given.\n\n`value` is the typed text. Every keystroke fires `input` with the text on the\nelement, so a table can narrow as the user types. Backspace in an empty field\nfires `helix-dismiss` on the last token, the same event its remove control\nfires, so one handler covers the pointer and the keyboard.\n\n**What a form receives.** The text under `name`, and then one more entry\nunder `name` for each token, in the order the tokens stand:\n\n| Token | Entry |\n|---|---|\n| Any element with a `value` attribute | The value as written: `saved:mine` |\n| `FilterChip` with `name` and values | `status:open,pending` |\n| The same, with `operator=\"none\"` (what a typed `-status:` makes) | `-status:open,pending` |\n| The same, with any other `operator` except `any` | `created[after]:2024` |\n| A token with neither | Nothing |\n\nThe values are the chip's text outside its `field` and `operator` slots,\nwith the spaces around each comma removed. A server splits an entry at its\nfirst colon, reads a leading `-` as the negation, and reads a word in\nbrackets before the colon as the comparison.\n\n**Keyboard.** Focus stays in the text, which is the field's one tab stop. The\ntext names the highlighted suggestion as its `aria-activedescendant`, and the\narrow keys reach the tokens.\n\n| Key | What it does |\n|---|---|\n| Enter | Presses the highlighted suggestion. With none highlighted, reads the typed filters into chips, or submits the form when there are none. |\n| Down, Up | Moves the highlight through the suggestions, wrapping, and opens the panel. |\n| Home, End | Highlights the first or the last suggestion while the panel is open. |\n| Escape | Closes the panel and stops there, so a dialog around the field stays open. With the panel closed, empties the text. In an empty field, does nothing, so the page hears it. |\n| Backspace | In an empty field, asks the last token to go. |\n| Left | With the caret at the start of the text, moves to the last token's remove button. Right on a right-to-left page. |\n| Left, Right on a token | Move between the tokens, and past the last back to the text. |\n| Delete, Backspace on a token | Asks the token to go. |\n\n**Typed filters.** The field parses only the fields you declare. Write\n`FilterField` elements, usually inside the `FilterMenu` slotted into `start`,\nso the picker and the text share one set. On Enter, the field reads the text\nagainst them, and a paste is read the same way as soon as it lands.\n`disposition:refunded,settled` and `-disposition:refunded` fire\n`helix-facet` exactly as ticking those values in the picker would, and the\nparsed text is removed. Everything else stays, so `refund tuesday\ndisposition:settled` is a filter and a search at once. Helix defines the\npunctuation and you define every word. `grammar.ts` has the full rule, so\nread it before you rely on it. A field with no `FilterField` in it parses\nnothing.\n\nA field whose values cannot be listed, such as `assignee:ada`, goes directly\ninside this element, outside the menu. It is not assigned to a slot, so\nnothing draws it and the menu has no page for it, and the grammar still reads\nit.\n\n**The picker has an entry of its own.** `FilterMenu` draws its pages with\n`Menu`, which a field without a picker does not need, so this family's entry\nleaves it out. A page that writes one imports\n`@fusion.dev/helix/filter-input/menu` as well, and a picker written without it\nis reported once the page has loaded, with the entry to add.\n\n**Suggestions.** Slot options into `suggestions` and the field shows them,\nmoves through them with the arrow keys, and presses one on Enter. The option\nfires its own `helix-select`, and you decide what choosing it means. Keys\nbefore a colon and values after it use the same panel with different\ncontents. `filter-suggestions` narrows the panel to the options whose words\nhold the term at the caret, after its colon, ignoring case and accents, and\nhides the rest. `readFilterText` is exported so you can narrow it yourself\nagainst partly typed text. While the panel is open, a reader hears how many\nsuggestions it offers. The panel opens when it has options and closes when it has\nnone, and a choice does not close it, so after picking a key you see its\nvalues next. Use `selectionStart` and `setSelectionRange` to write a\ncompletion back and put the caret after it, or the next parse reads the wrong\nterm.\n\n**State.** Three things have three different owners:\n\n- `value` is the text. The user types, the element applies it, and `input`\n  reports it. Setting `value` seeds or corrects the text, and the next\n  keystroke overwrites it, even in React. To control the value, cancel\n  `helix-before-change` and write the value you want, as with every field in\n  this library. `default-value` seeds the field.\n- `open` is the suggestions panel. Cancel `helix-before-open` or\n  `helix-before-close` to control it, and use `default-open` to seed it.\n- Tokens are your elements in a slot and hold no state. A token goes when you\n  remove it from your markup after `helix-dismiss`. A `FilterChip` naming a\n  declared field works differently, because the picker holds what is ticked\n  and removing the chip alone would leave its value ticked in the hidden\n  menu. Its dismissal is treated as the field being filtered by nothing, so\n  it fires `helix-facet` like every other change, and the chip goes when the\n  filter goes. Set `chips` and the field adds, updates, and removes those\n  chips itself, from every `helix-facet` you do not cancel.",
           "name": "HelixHeadlessFilterInput",
           "cssParts": [
             {
@@ -70964,7 +71018,7 @@
               "privacy": "private",
               "return": {
                 "type": {
-                  "text": "HelixHeadlessFilterMenu | null"
+                  "text": "FieldPicker | null"
                 }
               },
               "parameters": [
@@ -71027,7 +71081,7 @@
               "name": "handleDismiss",
               "privacy": "private",
               "readonly": true,
-              "description": "A chip asking to go, answered as the filter going.\n\n**Taken rather than passed on, and only for a chip naming a declared\nfield.** Left alone, a dismissed chip removed itself and told the picker\nnothing, so the menu went on showing the value ticked and the reader's next\npress on it read as *unticking*: they pressed `Refunded` and nothing came\nback. Turning the request into `apply(field, [])` puts it down the one road\nevery other filter takes, so the chip goes because the filter went. A\nconsumer refusing that `helix-facet` keeps both, which is the answer a\nrefusal should give.\n\nEverything else in the row is untouched: a plain `Tag`, or a chip for\nsomething no `FilterField` declares, is the consumer's to answer."
+              "description": "A chip asking to go, answered as the filter going.\n\n**Taken rather than passed on, and only for a chip naming a declared\nfield.** Left alone, a dismissed chip removed itself and told the picker\nnothing, so the menu went on showing the value ticked and the reader's next\npress on it read as *unticking*: they pressed `Refunded` and nothing came\nback. Turning the request into `apply(field, [])` puts it down the one road\nevery other filter takes, so the chip goes because the filter went. A\nconsumer refusing that `helix-facet` keeps both, which is the answer a\nrefusal should give.\n\nEverything else in the row is untouched: a plain `Tag`, or a chip for\nsomething no `FilterField` declares, is the consumer's to answer.\n\n**Heard on the way down, in the capture phase**, because the chip is a\nchild of this element and its request passes here before it reaches the\nchip's listeners or comes back up. Stopped there, no listener on the chip,\non this element or above it hears it. Heard on the way up, `stopPropagation`\nkept it from the ancestors and not from this element's other listeners, so a\nconsumer listening on the field heard `helix-dismiss` as well as the\n`helix-facet` that answered it."
             },
             {
               "kind": "method",
@@ -71169,6 +71223,17 @@
                 "module": "src/mixins/mixin-tokens/mixin-tokens.ts"
               }
             },
+            {
+              "kind": "method",
+              "name": "auditPicker",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "description": "Says so when a picker is written in the field and never registered.\n\nThe picker has an entry of its own, so a page that imports only the field\ngets an inert element there: a trigger that opens nothing. Asked once the\npage has loaded and painted, so an entry a later module imports is not\ntaken for a missing one."
+            },
             {
               "kind": "method",
               "name": "markActive",
@@ -81517,6 +81582,21 @@
         }
       ]
     },
+    {
+      "kind": "javascript-module",
+      "path": "src/icon/all/index.ts",
+      "declarations": [],
+      "exports": [
+        {
+          "kind": "js",
+          "name": "*",
+          "declaration": {
+            "name": "*",
+            "module": "src/icon/index.js"
+          }
+        }
+      ]
+    },
     {
       "kind": "javascript-module",
       "path": "src/icon/fetch.ts",
@@ -81823,7 +81903,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "The icons are Phosphor, drawn on a 256 box at stroke-width 16. Each glyph\nrenders its full inner markup, because most icons are several elements, each\nwith its own stroke and fill.\n\nThe markup is generated at build time from SVG files in this repository and\nnever comes from user input, so rendering it with `unsafeSVG` is safe.\n\nThe `<svg>` carries `fill=\"currentColor\"`. The generator keeps only the inner\nmarkup, and Phosphor sets its fill on the root tag that the generator\ndiscards. Without it, the 65 solid glyphs fall back to black and disappear on\na dark background. Shapes that set their own `fill` or `stroke` are\nunaffected.\n\n**A name is looked up in a registry.** The family's entry registers the\nwhole set, so any name in it draws. The element's own entry,\n`@fusion.dev/helix-headless/icon/root`, registers none: a page that imports\nit and calls `registerIcons` with the glyphs it names ships those and no\nothers. `registerIconLibrary` resolves names under a prefix of your own,\nsuch as `lucide:camera`, at once or later, and the element fires `load` when\na glyph that came later is drawn. A glyph registered after the element\nrendered is drawn then.\n\n**Or point `src` at an SVG file**, such as `src=\"/icons/rocket.svg\"`, and\nthe element fetches it and draws its shapes in `currentColor` where the file\ndoes not color them. A file is fetched once a page, however many icons name\nit, and `load` fires when it is drawn. Scripts, event handlers and\n`javascript:` links in the file are taken out before it is drawn. A server\nfetches nothing, so a served icon with a `src` is drawn once the script\nruns.\n\nA name with no match, or a `src` that is no SVG, renders nothing, and the\nelement fires `error`, so a typo in a name can be heard. It waits until the page has loaded and painted\nfirst, so a library a later module registers is not taken for a typo.\n\nAn icon is decorative by default and hidden from assistive technology. Set\n`label` only when the icon is the only carrier of meaning, such as in a\nbutton with no text. An `aria-label` on the element works too: the element\nis then an image with that name.\n\n**A decorative icon that is all a control holds is reported.** In a\ndevelopment build, a button or a link whose only content is an icon with no\n`label`, and which has no name of its own, warns `missing-name` once,\nthrough the runtime channel every Helix warning uses.",
+          "description": "The icons are Phosphor, drawn on a 256 box at stroke-width 16. Each glyph\nrenders its full inner markup, because most icons are several elements, each\nwith its own stroke and fill.\n\nThe markup is generated at build time from SVG files in this repository and\nnever comes from user input, so rendering it with `unsafeSVG` is safe.\n\nThe `<svg>` carries `fill=\"currentColor\"`. The generator keeps only the inner\nmarkup, and Phosphor sets its fill on the root tag that the generator\ndiscards. Without it, the 65 solid glyphs fall back to black and disappear on\na dark background. Shapes that set their own `fill` or `stroke` are\nunaffected.\n\n**A name is looked up in a registry.** The family's entry registers a small\nset: the four carets, `arrow-left`, `arrow-right`, `check`, `x`, `plus`,\n`minus`, `magnifying-glass`, `info` and `warning`. `icon/all` registers the\nwhole set, so any name in it draws, and a name that resolves to nothing\nsays to import it. The element's own entry,\n`@fusion.dev/helix-headless/icon/root`, registers none: a page that imports\nit and calls `registerIcons` with the glyphs it names ships those and no\nothers. `registerIconLibrary` resolves names under a prefix of your own,\nsuch as `lucide:camera`, at once or later, and the element fires `load` when\na glyph that came later is drawn. A glyph registered after the element\nrendered is drawn then.\n\n**Or point `src` at an SVG file**, such as `src=\"/icons/rocket.svg\"`, and\nthe element fetches it and draws its shapes in `currentColor` where the file\ndoes not color them. A file is fetched once a page, however many icons name\nit, and `load` fires when it is drawn. Scripts, event handlers and\n`javascript:` links in the file are taken out before it is drawn. A server\nfetches nothing, so a served icon with a `src` is drawn once the script\nruns.\n\nA name with no match, or a `src` that is no SVG, renders nothing, and the\nelement fires `error`, so a typo in a name can be heard. It waits until the page has loaded and painted\nfirst, so a library a later module registers is not taken for a typo.\n\nAn icon is decorative by default and hidden from assistive technology. Set\n`label` only when the icon is the only carrier of meaning, such as in a\nbutton with no text. An `aria-label` on the element works too: the element\nis then an image with that name.\n\n**A decorative icon that is all a control holds is reported.** In a\ndevelopment build, a button or a link whose only content is an icon with no\n`label`, and which has no name of its own, warns `missing-name` once,\nthrough the runtime channel every Helix warning uses.",
           "name": "HelixHeadlessIcon",
           "cssParts": [
             {
@@ -81867,7 +81947,7 @@
                 "text": "string"
               },
               "default": "''",
-              "description": "The name of the icon in the Helix set.\n\n**A lookup, and the reason both this and `icon` exist.** A name is a string,\nso it is what markup can carry, and resolving one means an index of the\nwhole set that no bundler can shake: 15 kB for a consumer who renders one\nmark. An attribute is the only thing an HTML author can write, and that is\nworth the index; a consumer who would rather not pay it imports the\nelement from `icon/root` and registers the glyphs it names, or hands over\nthe value instead.\n\nA name written `prefix:name` asks the library registered under that\nprefix.",
+              "description": "The name of the icon in the Helix set.\n\n**A lookup, and the reason both this and `icon` exist.** A name is a string,\nso it is what markup can carry, and resolving one means an index that no\nbundler can shake. The family's entry indexes a small set, `icon/all`\nindexes the whole set at 15 kB, and `icon/root` indexes nothing, for a\npage that registers the glyphs it names or hands over the value instead.\n\nA name written `prefix:name` asks the library registered under that\nprefix.",
               "attribute": "name"
             },
             {
@@ -82418,7 +82498,7 @@
                 "text": "string"
               },
               "default": "''",
-              "description": "The name of the icon in the Helix set.\n\n**A lookup, and the reason both this and `icon` exist.** A name is a string,\nso it is what markup can carry, and resolving one means an index of the\nwhole set that no bundler can shake: 15 kB for a consumer who renders one\nmark. An attribute is the only thing an HTML author can write, and that is\nworth the index; a consumer who would rather not pay it imports the\nelement from `icon/root` and registers the glyphs it names, or hands over\nthe value instead.\n\nA name written `prefix:name` asks the library registered under that\nprefix.",
+              "description": "The name of the icon in the Helix set.\n\n**A lookup, and the reason both this and `icon` exist.** A name is a string,\nso it is what markup can carry, and resolving one means an index that no\nbundler can shake. The family's entry indexes a small set, `icon/all`\nindexes the whole set at 15 kB, and `icon/root` indexes nothing, for a\npage that registers the glyphs it names or hands over the value instead.\n\nA name written `prefix:name` asks the library registered under that\nprefix.",
               "fieldName": "name"
             },
             {
@@ -83729,6 +83809,14 @@
             "module": "src/filter-input/index.js"
           }
         },
+        {
+          "kind": "js",
+          "name": "*",
+          "declaration": {
+            "name": "*",
+            "module": "src/filter-input/menu/index.js"
+          }
+        },
         {
           "kind": "js",
           "name": "*",
@@ -83758,7 +83846,7 @@
           "name": "*",
           "declaration": {
             "name": "*",
-            "module": "src/icon/index.js"
+            "module": "src/icon/all/index.js"
           }
         },
         {
@@ -88241,7 +88329,7 @@
                 "text": "string"
               },
               "default": "''",
-              "description": "The item's identifier. The root compares its `active` value against it.",
+              "description": "The item's identifier. The root compares its `active` value against it.\nWithout one, the item is named by its place in the set, counted from 1.",
               "attribute": "value"
             },
             {
@@ -88626,7 +88714,7 @@
                 "text": "string"
               },
               "default": "''",
-              "description": "The item's identifier. The root compares its `active` value against it.",
+              "description": "The item's identifier. The root compares its `active` value against it.\nWithout one, the item is named by its place in the set, counted from 1.",
               "fieldName": "value"
             }
           ],
@@ -88693,7 +88781,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "The frame around content you open, such as a picture, a video frame, or a\nchart. The lightbox draws no content of its own. It provides the frame, the\nkeyboard behavior, and text that states the current position in the set.\n\nThe modal behavior comes from a native `<dialog>` opened with `showModal()`,\nwhich provides the top layer, a backdrop, Escape to close, and `inert` on the\nrest of the document. Every way of closing goes through `requestOpen`, as in\n`Dialog` and `Drawer`.\n\nA lightbox shows one item at a time and has no scrolling track, so `active`\nholds the current item, as in `Tabs`. The arrow keys change the item while\nfocus stays in the dialog.\n\nSet `controls` for the viewer's own previous, next and close controls, named\nby `previous-label`, `next-label` and `dismiss-label`, whose glyphs you can\nreplace in the `previous-icon`, `next-icon` and `dismiss-icon` slots. Without\nit, compose the chrome yourself in the `header` and `footer` slots, with\nbuttons that send `--previous`, `--next` and `--close`.\n\n**Set `max-zoom` to let a reader zoom into the shown item**, such as `3`.\nTwo fingers pinch it, and so does a trackpad pinch or the wheel with Ctrl\nheld, about the point under the pointer. A double click or a double tap\nzooms all the way in about the point pressed and back out, and once zoomed\none pointer drags it about and the wheel moves it. `+` and `-` zoom in and out from the keyboard, and `0` puts it back.\nThe scale and the offset are on the `viewport` part as `--lightbox-zoom`,\n`--lightbox-pan-x` and `--lightbox-pan-y`, written only while zoomed, and a\nswipe moves to the next item only while the item is at its own size. With\n`controls`, the viewer also draws zoom-out and zoom-in controls, for a\npointer with no wheel and no second finger. Once a reader stops zooming, the\nlive region says the new scale in the words of `zoom-status-label`, such as\n\"Zoomed to 150%\".\n\nEach item is a slide: a `group` with the role description in\n`slide-role-label`, named by its `label` or by `slide-label`. A touch or a pen\nswiped across the picture shows the next or the previous item, the way the\nline of text runs.\n\nA press on the empty area around the item closes the viewer, as a press on\nthe backdrop does. Under `max-zoom`, a press beside the item zooms on a\ndouble press and closes nothing, and only the space outside the viewport\ncloses the viewer. A press that dragged closes nothing.\n\n**Keyboard.** Opening moves focus to the viewer itself, which a screen\nreader names.\n\n| Key | What it does |\n|---|---|\n| Right, Down | Shows the next item. On a right-to-left page, Left does. While the item is zoomed, the arrows move about it instead. |\n| Left, Up | Shows the previous item. |\n| Home, End | Shows the first or the last item. |\n| `+`, `-`, `0` | Zooms in, zooms out, and puts the item back at its own size, where `max-zoom` allows zooming. |\n| Tab, Shift+Tab | Moves through the controls in the viewer, from the last round to the first and from the first round to the last. |\n| Escape | Closes the viewer. A `helix-before-close` listener can refuse. |\n\nA development build warns when a viewer opens with no `label`.\n\nThe chrome hides when there is no input, through `IdleController`, and comes\nback on a pointer move, a key press, or a focus. It stays while focus is on a\ncontrol in the header or the footer, so a keyboard reader is never left on\na control that has gone. `fullscreen` uses `FullscreenController`, as `Video`\ndoes. While the viewer is open, the page behind it does not scroll.",
+          "description": "The frame around content you open, such as a picture, a video frame, or a\nchart. The lightbox draws no content of its own. It provides the frame, the\nkeyboard behavior, and text that states the current position in the set.\n\nThe modal behavior comes from a native `<dialog>` opened with `showModal()`,\nwhich provides the top layer, a backdrop, Escape to close, and `inert` on the\nrest of the document. Every way of closing goes through `requestOpen`, as in\n`Dialog` and `Drawer`.\n\nA lightbox shows one item at a time and has no scrolling track, so `active`\nholds the current item, as in `Tabs`. The arrow keys change the item while\nfocus stays in the dialog. `active` names an item by its `value`, and an\nitem with no `value` by its place, counted from 1, as in `Steps`, so a set\nwritten without values moves and `helix-activate` says `1`, `2` and so on.\n\nSet `controls` for the viewer's own previous, next and close controls, named\nby `previous-label`, `next-label` and `dismiss-label`, whose glyphs you can\nreplace in the `previous-icon`, `next-icon` and `dismiss-icon` slots. Without\nit, compose the chrome yourself in the `header` and `footer` slots, with\nbuttons that send `--previous`, `--next` and `--close`.\n\n**Set `max-zoom` to let a reader zoom into the shown item**, such as `3`.\nTwo fingers pinch it, and so does a trackpad pinch or the wheel with Ctrl\nheld, about the point under the pointer. A double click or a double tap\nzooms all the way in about the point pressed and back out, and once zoomed\none pointer drags it about and the wheel moves it. `+` and `-` zoom in and out from the keyboard, and `0` puts it back.\nThe scale and the offset are on the `viewport` part as `--lightbox-zoom`,\n`--lightbox-pan-x` and `--lightbox-pan-y`, written only while zoomed, and a\nswipe moves to the next item only while the item is at its own size. With\n`controls`, the viewer also draws zoom-out and zoom-in controls, for a\npointer with no wheel and no second finger. Once a reader stops zooming, and\nat once for a key or a zoom control, the live region says the new scale in\nthe words of `zoom-status-label`, such as \"Zoomed to 150%\".\n\nEach item is a slide: a `group` with the role description in\n`slide-role-label`, named by its `label` or by `slide-label`. A touch or a pen\nswiped across the picture shows the next or the previous item, the way the\nline of text runs.\n\nA press on the empty area around the item closes the viewer, as a press on\nthe backdrop does. Under `max-zoom`, a press beside the item zooms on a\ndouble press and closes nothing, and only the space outside the viewport\ncloses the viewer. A press that dragged closes nothing.\n\n**Keyboard.** Opening moves focus to the viewer itself, which a screen\nreader names.\n\n| Key | What it does |\n|---|---|\n| Right, Down | Shows the next item. On a right-to-left page, Left does. While the item is zoomed, the arrows move about it instead. |\n| Left, Up | Shows the previous item. |\n| Home, End | Shows the first or the last item. |\n| `+`, `-`, `0` | Zooms in, zooms out, and puts the item back at its own size, where `max-zoom` allows zooming. |\n| Tab, Shift+Tab | Moves through the controls in the viewer, from the last round to the first and from the first round to the last. |\n| Escape | Closes the viewer. A `helix-before-close` listener can refuse. |\n\nA development build warns when a viewer opens with no `label`.\n\nThe chrome hides when there is no input, through `IdleController`, and comes\nback on a pointer move, a key press, or a focus. It stays while focus is on a\ncontrol in the header or the footer, so a keyboard reader is never left on\na control that has gone. `fullscreen` uses `FullscreenController`, as `Video`\ndoes. While the viewer is open, the page behind it does not scroll.",
           "name": "HelixHeadlessLightbox",
           "cssProperties": [
             {
@@ -89123,6 +89211,16 @@
               ],
               "description": "Writes the zoom on the viewport, and nothing at the item's own size."
             },
+            {
+              "kind": "field",
+              "name": "zoomStep",
+              "type": {
+                "text": "boolean"
+              },
+              "privacy": "private",
+              "default": "false",
+              "description": "Whether the zoom is changing by one discrete step, a key or a control, which is said at once."
+            },
             {
               "kind": "method",
               "name": "sayZoom",
@@ -89132,7 +89230,7 @@
                   "text": "void"
                 }
               },
-              "description": "Says the new scale in the live region, a moment after the last change."
+              "description": "Says the new scale in the live region: a moment after the last change of\na pinch, a drag or the wheel, and at once for a key or a zoom control,\nwhich is one change a reader is waiting to hear. Said only after the\npause, a reader pressing `+` heard nothing until it ended."
             },
             {
               "kind": "method",
@@ -89389,6 +89487,25 @@
               },
               "description": "Zooms out by as much, as `-` and the zoom-out control do."
             },
+            {
+              "kind": "method",
+              "name": "stepZoom",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "change",
+                  "type": {
+                    "text": "() => void"
+                  }
+                }
+              ],
+              "description": "Changes the zoom by one discrete step, which `sayZoom` says at once."
+            },
             {
               "kind": "method",
               "name": "toEnd",
@@ -89421,10 +89538,64 @@
             {
               "kind": "field",
               "name": "shown",
+              "type": {
+                "text": "HelixHeadlessLightboxItem | undefined"
+              },
               "privacy": "private",
               "description": "The item on screen: the one `active` names, or the first where it names none.",
               "readonly": true
             },
+            {
+              "kind": "method",
+              "name": "named",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "HelixHeadlessLightboxItem | undefined"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "items",
+                  "type": {
+                    "text": "HelixHeadlessLightboxItem[]"
+                  }
+                }
+              ],
+              "description": "The item `active` names, by `value` or by place, or the first where it names none."
+            },
+            {
+              "kind": "method",
+              "name": "requestActive",
+              "return": {
+                "type": {
+                  "text": "boolean"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "next",
+                  "type": {
+                    "text": "string"
+                  }
+                },
+                {
+                  "name": "cause",
+                  "optional": true,
+                  "type": {
+                    "text": "string"
+                  }
+                }
+              ],
+              "description": "Requests a new shown item, and returns whether it moved.\n\nWhere `active` names nothing, it is first written with the item on\nscreen, so `helix-activate` names the item you saw as `previous`.",
+              "inheritedFrom": {
+                "name": "MixinControllerActive",
+                "module": "src/mixins/mixin-controller-active/mixin-controller-active.ts"
+              },
+              "type": {
+                "text": "requestActive(next: string, cause?: string) => boolean"
+              }
+            },
             {
               "kind": "field",
               "name": "handleBackdrop",
@@ -89608,38 +89779,6 @@
                 "module": "src/mixins/mixin-controller-active/mixin-controller-active.ts"
               }
             },
-            {
-              "kind": "method",
-              "name": "requestActive",
-              "return": {
-                "type": {
-                  "text": "boolean"
-                }
-              },
-              "parameters": [
-                {
-                  "name": "next",
-                  "type": {
-                    "text": "string"
-                  }
-                },
-                {
-                  "name": "cause",
-                  "optional": true,
-                  "type": {
-                    "text": "string"
-                  }
-                }
-              ],
-              "description": "Requests a new current item, and returns whether the change was applied.\n\nAnnounces before it acts, so `preventDefault()` on the `helix-before-activate` is\na refusal and nothing moves. Unlike a native control, nothing has moved\nby the time this runs, so refusing is simply not writing: there is\nnothing to put back. Nobody refusing means the set updates itself,\nwhether or not a consumer declared `active`, a declared property being a\nseed and a correction. `cause` says why, where the family names its\ncauses, and reaches the event as `detail.cause`.",
-              "inheritedFrom": {
-                "name": "MixinControllerActive",
-                "module": "src/mixins/mixin-controller-active/mixin-controller-active.ts"
-              },
-              "type": {
-                "text": "requestActive(next: string, cause?: string) => boolean"
-              }
-            },
             {
               "kind": "method",
               "name": "announceActivated",
@@ -116316,7 +116455,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "Notifications are slotted children. Each one is your own markup, with an\navatar, a link, or a button in it. Feeds usually hold tens of items, so\nwriting them out lets an item hold anything.\n\nThe list does not virtualize. Windowing needs the list to own the data, and\nhere you own it, so N notifications are N elements. For a feed of thousands,\nuse a data table with a custom cell.\n\nRead state is reported to you. Marking read goes from the root to the item\nand from the item to you, so a canceled `helix-read` changes nothing, and if\nyou own `read`, nothing changes until you set it. `unread` is derived from\nthe items and written to an attribute, so a stylesheet and a badge can both\nuse it without counting.\n\n**The feed is one `Tab` stop for its rows.** Each row takes focus itself and\nis read by its label. `ArrowDown` and `ArrowUp` move to the next and the\nprevious row, `Home` and `End` to the first and the last, and `PageDown` and\n`PageUp` move a row on or back from anywhere inside one, as in the APG feed\npattern. The controls inside a row stay in the `Tab` order. Set `total` when\nthe feed holds one page of a longer list, and each row says its place in the\nwhole of it.\n\n**Keyboard.**\n\n| Key | What it does |\n|---|---|\n| Down, Up | On a row, moves to the next or the previous row. |\n| Home, End | On a row, moves to the first or the last row. |\n| Page Down, Page Up | From anywhere in a row, moves to the next or the previous row. |\n| Control+End | From anywhere in the feed, moves to the first control after it on the page. |\n| Control+Home | From anywhere in the feed, moves to the nearest control before it on the page. |\n| Tab | Moves through the controls in a row, and on out of the feed. |\n\n**A notification that arrives says so.** Unread rows added above the rows\nthere were are counted in the live region,\n\"1 new notification\", in `arrived-label`. Rows that arrive while `loading`\nis set say nothing, so set it while a page is on its way.\n\n**`load-more` adds a button after the list** that sends `helix-load-more`,\nfor a feed that holds one page of a longer list. Append the next page, set\n`loading` while it is on its way, and take `load-more` off once there is\nnothing more. While the feed is loading the button stays, so focus stays on\nit, and it is `aria-disabled` and sends nothing.\n\n**`load-error` says a page could not be fetched**, such as \"Could not load\nnotifications\": it shows under the rows there are, in the `error` part, in\nplace of the empty and loading lines, and a screen reader hears it. Clear it\nwhen you ask again.",
+          "description": "Notifications are slotted children. Each one is your own markup, with an\navatar, a link, or a button in it. Feeds usually hold tens of items, so\nwriting them out lets an item hold anything.\n\nThe list does not virtualize. Windowing needs the list to own the data, and\nhere you own it, so N notifications are N elements. For a feed of thousands,\nuse a data table with a custom cell.\n\nRead state is reported to you. Marking read goes from the root to the item\nand from the item to you, so a canceled `helix-read` changes nothing, and if\nyou own `read`, nothing changes until you set it. `unread` is derived from\nthe items and written to an attribute, so a stylesheet and a badge can both\nuse it without counting.\n\n**The feed is one `Tab` stop for its rows.** It is an APG feed: the list is\na `feed`, busy while `loading` is set, and each row is an `article` that\ntakes focus itself and is read by its label. `ArrowDown` and `ArrowUp` move to the next and the\nprevious row, `Home` and `End` to the first and the last, and `PageDown` and\n`PageUp` move a row on or back from anywhere inside one, as in the APG feed\npattern. The controls inside a row stay in the `Tab` order. Set `total` when\nthe feed holds one page of a longer list, and each row says its place in the\nwhole of it.\n\n**Keyboard.**\n\n| Key | What it does |\n|---|---|\n| Down, Up | On a row, moves to the next or the previous row. |\n| Home, End | On a row, moves to the first or the last row. |\n| Page Down, Page Up | From anywhere in a row, moves to the next or the previous row. |\n| Control+End | From anywhere in the feed, moves to the first control after it on the page. |\n| Control+Home | From anywhere in the feed, moves to the nearest control before it on the page. |\n| Tab | Moves through the controls in a row, and on out of the feed. |\n\n**A notification that arrives says so.** Unread rows added above the rows\nthere were are counted in the live region,\n\"1 new notification\", in `arrived-label`. Rows that arrive while `loading`\nis set say nothing, so set it while a page is on its way.\n\n**`load-more` adds a button after the list** that sends `helix-load-more`,\nfor a feed that holds one page of a longer list. Append the next page, set\n`loading` while it is on its way, and take `load-more` off once there is\nnothing more. While the feed is loading the button stays, so focus stays on\nit, and it is `aria-disabled` and sends nothing.\n\n**`load-error` says a page could not be fetched**, such as \"Could not load\nnotifications\": it shows under the rows there are, in the `error` part, in\nplace of the empty and loading lines, and a screen reader hears it. Clear it\nwhen you ask again.",
           "name": "HelixHeadlessNotifications",
           "cssParts": [
             {
@@ -116336,7 +116475,7 @@
               "name": "header"
             },
             {
-              "description": "The list itself.",
+              "description": "The list itself, a `feed` whose rows are its articles.",
               "name": "list"
             },
             {
@@ -182544,7 +182683,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "The trigger stays your own element. The bubble renders in the\ntop layer through the popover API, so an ancestor with `overflow: hidden`\ndoes not clip it and no `z-index` is needed. `FloatingController` positions\nit and flips it to another side when the preferred side does not fit.\n\n**Place the tooltip beside its trigger, name the trigger with `for`, and\nname the tooltip in the trigger's `aria-describedby`.** The description is\nthen in your own markup, so it is in the server's HTML and in the\naccessibility tree at rest, in every browser, before anyone points at the\ntrigger or focuses it:\n\n```html\n<helix-headless-button aria-describedby=\"save-tip\" id=\"save\">Save</helix-headless-button>\n<helix-headless-tooltip content=\"Save your work\" for=\"save\" id=\"save-tip\"></helix-headless-tooltip>\n```\n\nWithout the attribute, the tooltip links itself through an element reference\non the control that takes focus, and it never writes into your markup before\nyou act, so hydration stays intact. A trigger that is a Helix component is\ndescribed at once, inside its own shadow root. A plain element in your\nmarkup is described when you first point at it or focus it, so a screen\nreader in reading mode meets it with no description until then. Where the\nbrowser has no element references, nothing links the two, and the tooltip\nwarns once on first open. The tooltip can also wrap its trigger, which\ndescribes a Helix component and leaves a plain element undescribed. In the\n`for` form the tooltip itself is out of the accessibility tree while its\nbubble is down, so you meet its words once, as the trigger's description.\nA trigger whose name is already the tooltip's words, such as an icon button\nnamed Settings under a tooltip reading Settings, is not described by them\nagain.\n\nThe tooltip shows on hover and on focus. It hides on pointer leave, on blur,\non Escape, and when the trigger is activated. The pointer can move from the\ntrigger onto the bubble and the bubble stays, unless you set\n`hoverable=\"false\"`. `delay` is how long the pointer rests before it shows,\nand `delay-out` how long it stays once the pointer leaves.\n\nOnce one tooltip is showing, moving to another trigger shows its tooltip\nwith no `delay`, and the first one hides. The same holds for `skip-delay`\nmilliseconds after a tooltip hides, 300 unless you set it. `show-on=\"focus\"`\nshows the tooltip on keyboard focus only, for a hint a pointer does not need.",
+          "description": "The trigger stays your own element. The bubble renders in the\ntop layer through the popover API, so an ancestor with `overflow: hidden`\ndoes not clip it and no `z-index` is needed. `FloatingController` positions\nit and flips it to another side when the preferred side does not fit.\n\n**Place the tooltip beside its trigger, name the trigger with `for`, and\nname the tooltip in the trigger's `aria-describedby`.** The description is\nthen in your own markup, so it is in the server's HTML and in the\naccessibility tree at rest, in every browser, before anyone points at the\ntrigger or focuses it:\n\n```html\n<helix-headless-button aria-describedby=\"save-tip\" id=\"save\">Save</helix-headless-button>\n<helix-headless-tooltip content=\"Save your work\" for=\"save\" id=\"save-tip\"></helix-headless-tooltip>\n```\n\nWithout the attribute, the tooltip links itself through an element reference\non the control that takes focus, and it never writes into your markup before\nyou act, so hydration stays intact. A trigger that is a Helix component is\ndescribed at once, inside its own shadow root. A plain element in your\nmarkup is described when you first point at it or focus it, so a screen\nreader in reading mode meets it with no description until then. Where the\nbrowser has no element references, nothing links the two, and the tooltip\nwarns once on first open. The tooltip can also wrap its trigger. A Helix\ncomponent inside is described at once, and a plain element as in the `for`\nform: when you first point at it or focus it, or at rest where it names the\ntooltip's `id` in its own `aria-describedby`, which a reference to the\nelement around it allows. In the\n`for` form the tooltip itself is out of the accessibility tree while its\nbubble is down, so you meet its words once, as the trigger's description.\nA trigger whose name is already the tooltip's words, such as an icon button\nnamed Settings under a tooltip reading Settings, is not described by them\nagain.\n\nThe tooltip shows on hover and on focus. It hides on pointer leave, on blur,\non Escape, and when the trigger is activated. The pointer can move from the\ntrigger onto the bubble and the bubble stays, unless you set\n`hoverable=\"false\"`. `delay` is how long the pointer rests before it shows,\nand `delay-out` how long it stays once the pointer leaves.\n\nOnce one tooltip is showing, moving to another trigger shows its tooltip\nwith no `delay`, and the first one hides. The same holds for `skip-delay`\nmilliseconds after a tooltip hides, 300 unless you set it. `show-on=\"focus\"`\nshows the tooltip on keyboard focus only, for a hint a pointer does not need.",
           "name": "HelixHeadlessTooltip",
           "cssParts": [
             {
@@ -198176,6 +198315,6 @@
   ],
   "helix": {
     "package": "@fusion.dev/helix-headless",
-    "version": "0.174.0"
+    "version": "0.176.0"
   }
 }

package/dist/app-header/root/app-header-root.d.ts

@@ -1,5 +1,5 @@
 import { HelixElement } from '@fusion.dev/helix-core';
-import { type PropertyValues, type TemplateResult } from 'lit';
+import { type CSSResultGroup, type PropertyValues, type TemplateResult } from 'lit';
 declare const HelixHeadlessAppHeader_base: (new (...args: any[]) => import("@fusion.dev/helix-core").MixinControllerOpenInterface) & typeof HelixElement;
 /**
  * @summary Page-level banner holding brand, navigation, and actions.
@@ -90,6 +90,7 @@ export declare class HelixHeadlessAppHeader extends HelixHeadlessAppHeader_base
      * `registerWords('de', { 'helix-app-header': { menuLabel: 'Menü' } })`.
      */
     static words: string;
+    static styles: CSSResultGroup;
     /**
      * Where the middle region sits in the bar.
      *

package/dist/app-header/root/app-header-root.js

@@ -6,7 +6,7 @@ var __decorate = (this && this.__decorate) || function (decorators, target, key,
 };
 import { customElement, deepActiveElement, deepContains, elementById, HelixElement, HelixScrolledEvent, hostAria, MixinControllerOpen, words, } from '@fusion.dev/helix-core';
 import { list } from '@fusion.dev/helix-icons';
-import { html, nothing } from 'lit';
+import { css, html, nothing, } from 'lit';
 import { property, state } from 'lit/decorators.js';
 import { unsafeSVG } from 'lit/directives/unsafe-svg.js';
 import { inSectioningContent } from '../sectioning.js';
@@ -61,6 +61,11 @@ let HelixHeadlessAppHeader = class HelixHeadlessAppHeader extends MixinControlle
         };
     }
     static { this.words = 'helix-app-header'; }
+    static { this.styles = css `
+    :host {
+      display: block;
+    }
+  `; }
     get unfolded() {
         return this.folded && this.open;
     }

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

@@ -327,7 +327,12 @@ export declare class HelixHeadlessButton extends HelixFormElement {
     protected updated(changed: PropertyValues): void;
     /** @internal A submit button is what its form's implicit submission presses. */
     protected get submitsForm(): boolean;
-    /** @internal Pressed as the form's default button, through the inner control. */
+    /**
+     * @internal Pressed as the form's default button, through the inner control.
+     *
+     * Only Enter in a field of the form presses it this way, so `helix-press`
+     * says `keyboard`, where the script click it makes read as `virtual`.
+     */
     protected activate(): void;
     /** The form whose Enter key this button listens to, as its default button. */
     private watched;

package/dist/button/root/button-root.js

@@ -153,6 +153,7 @@ let HelixHeadlessButton = class HelixHeadlessButton extends HelixFormElement {
         return this.type === 'submit';
     }
     activate() {
+        this.recent = { key: true };
         this.partNamed('button')?.click();
     }
     watchForm(form) {

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

@@ -47,8 +47,10 @@ declare const HelixHeadlessCommand_base: (new (...args: any[]) => import("@fusio
  * the full list. Combobox and Select do the same. As typing narrows the list, a
  * screen reader hears how many commands are left, such as "3 commands".
  *
- * **Keyboard.** Focus goes to the filter field as the palette opens, and the
- * highlight moves through the commands while you type.
+ * **Keyboard.** Focus goes to the filter field as the palette opens, with no
+ * command highlighted, as in React Aria's Autocomplete, so Enter runs nothing
+ * until you type or press Down. Typing highlights the first command left, and
+ * the highlight moves through the commands while you type.
  *
  * | Key | What it does |
  * |---|---|