@fusion.dev/helix-headless 0.156.0 → 0.158.0

package/custom-elements.json

@@ -1707,7 +1707,7 @@
                   "text": "HTMLElement | undefined"
                 }
               },
-              "description": "The tab stop after this element on the page, or the one before it at the\nend, for a lone element whose removal would drop focus to the body.\n\n**A lone Callout or Announcement had nowhere to hand focus**, so a\nkeyboard reader who dismissed one started again from the top of the\npage. React Aria's Toast hands focus on the same way. Read before the\nevent, in the order Tab reaches the stops, while this element's own are\nstill among them.",
+              "description": "The tab stop after this element on the page, or the one before it at the\nend, for an element whose removal would drop focus to the body because\nno neighbor of its kind has a control to take it.\n\n**A lone Callout or Announcement had nowhere to hand focus**, so a\nkeyboard reader who dismissed one started again from the top of the\npage. React Aria's Toast hands focus on the same way. Read before the\nevent, in the order Tab reaches the stops, while this element's own are\nstill among them.",
               "inheritedFrom": {
                 "name": "MixinDismissible",
                 "module": "src/mixins/mixin-dismissible/mixin-dismissible.ts"
@@ -12691,7 +12691,7 @@
                   "text": "HTMLElement | undefined"
                 }
               },
-              "description": "The tab stop after this element on the page, or the one before it at the\nend, for a lone element whose removal would drop focus to the body.\n\n**A lone Callout or Announcement had nowhere to hand focus**, so a\nkeyboard reader who dismissed one started again from the top of the\npage. React Aria's Toast hands focus on the same way. Read before the\nevent, in the order Tab reaches the stops, while this element's own are\nstill among them.",
+              "description": "The tab stop after this element on the page, or the one before it at the\nend, for an element whose removal would drop focus to the body because\nno neighbor of its kind has a control to take it.\n\n**A lone Callout or Announcement had nowhere to hand focus**, so a\nkeyboard reader who dismissed one started again from the top of the\npage. React Aria's Toast hands focus on the same way. Read before the\nevent, in the order Tab reaches the stops, while this element's own are\nstill among them.",
               "inheritedFrom": {
                 "name": "MixinDismissible",
                 "module": "src/mixins/mixin-dismissible/mixin-dismissible.ts"
@@ -40391,7 +40391,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 Backspace in an empty filter goes back. `page` says\nwhich 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, 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 `combobox` with\n`aria-activedescendant` on the highlighted command, and the commands are a\n`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, 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, 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": [
             {
@@ -40473,6 +40473,10 @@
             {
               "description": "The filter field.",
               "name": "listbox-search-field"
+            },
+            {
+              "description": "The region a screen reader announces the page shown from, by the words of the command that opens it, drawn once there is one to say. Visually hidden in the styled tier.",
+              "name": "live"
             }
           ],
           "slots": [
@@ -40543,6 +40547,14 @@
               "description": "How long typing rests before the commands are filtered, in milliseconds,\nso a palette filtered on a server sends one `helix-filter` for a word.\n`0` filters on every keystroke. See Listbox's `filter-delay`.",
               "attribute": "filter-delay"
             },
+            {
+              "kind": "field",
+              "name": "filterMatch",
+              "type": {
+                "text": "((text: string, filter: string) => boolean) | undefined | undefined"
+              },
+              "description": "Whether a command is kept by the filter: a function given the command's\nwords and the filter, trimmed, that returns `true` to keep it showing, as\nReact Aria's `Autocomplete` takes `filter`. See Listbox's `filterMatch`.\n\nAbsent, a command is kept where its words hold the filter, in any case. A\nproperty only, there being no way to write a function in markup."
+            },
             {
               "kind": "field",
               "name": "hotkey",
@@ -40752,6 +40764,14 @@
               ],
               "description": "Shows a page of commands, with the trail that leads back from it. The\nfilter starts empty, as it does on opening, and the field keeps focus."
             },
+            {
+              "kind": "field",
+              "name": "status",
+              "privacy": "private",
+              "readonly": true,
+              "default": "new StatusController(this)",
+              "description": "The region the page shown is said from as it changes."
+            },
             {
               "kind": "field",
               "name": "handleBack",
@@ -45597,6 +45617,13 @@
                   "type": {
                     "text": "boolean"
                   }
+                },
+                {
+                  "name": "id",
+                  "optional": true,
+                  "type": {
+                    "text": "string"
+                  }
                 }
               ],
               "description": "One cell, carrying its column's edge as a fact rather than as a decision.\n\n**A fact published rather than a property chosen**, which is what `Table`\ndoes with the same attribute: what lining up *means*, a `justify-content`\nfor a value that fits or a `text-align` for one that wraps, belongs to\nwhoever draws the cell. Written here as an inline `text-align` it was this\ntier choosing, in the tier that ships no CSS, and a consumer could not\noverrule it either, an inline declaration beating any `::part(cell)` rule\nthey wrote.\n\nOnly the three edges reach it, `text-align` being a string anybody can write and\nthis being a style attribute: `edgeOf` is that guard, and `Table` holds the\nsame value to the same three."
@@ -59512,11 +59539,11 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "A row that opens a page contains that page: the page's rows are this row's\nown children, assigned to the `page` slot. There are no ids to wire, and\nmoving a row moves its page with it.\n\nWhat the item renders depends on the stack:\n\n- On the page that is showing, it renders its row.\n- When its own page is showing, it renders only that page's rows. Its row\n  belongs to the page above.\n- When a page further down its own is showing, it renders its page's slot\n  alone, so the rows below reach the page.\n- Otherwise it renders nothing. The rows stay in the light DOM untouched, so\n  there is no state to keep.\n\nChoosing a row dispatches an event, and the stack decides whether that drills\nin or runs a command.\n\nA row that opens a page shows a caret after its text and sets\n`aria-haspopup`, the same way `Menu` marks a row with a submenu. The server\nrender leaves both out, because the server cannot see the children.\n\nThe row is named by its label alone. Words in `description`, a line under\nthe label, and in `end` describe it instead, through `aria-describedby`, as\n`Menu.Item` does: a reader hears \"Theme\", then \"Dark\".",
+          "description": "A row that opens a page contains that page: the page's rows are this row's\nown children, assigned to the `page` slot. There are no ids to wire, and\nmoving a row moves its page with it.\n\nWhat the item renders depends on the stack:\n\n- On the page that is showing, it renders its row.\n- When its own page is showing, it renders only that page's rows. Its row\n  belongs to the page above.\n- When a page further down its own is showing, it renders its page's slot\n  alone, so the rows below reach the page.\n- Otherwise it renders nothing. The rows stay in the light DOM untouched, so\n  there is no state to keep.\n\nChoosing a row dispatches an event, and the stack decides whether that drills\nin or runs a command.\n\nA row that opens a page shows a caret after its text and sets\n`aria-haspopup`, the same way `Menu` marks a row with a submenu. The server\nrender leaves both out, because the server cannot see the children.\n\n**A row with an `href` is a link.** The row itself renders as an `<a>`\ncarrying `menuitem`, as `Menu.Item` does, so a middle click, a modified\nclick and the status bar keep working. Enter follows it, and Space does too.\nChoosing it fires `helix-select` first: cancel the event and the link is not\nfollowed, so a router can take the navigation. A row that opens a page, or a\ndisabled row, renders no link.\n\nA development build warns when a row has no words to be named by, such as a\nrow holding only an icon with no label.\n\nThe row is named by its label alone. Words in `description`, a line under\nthe label, and in `end` describe it instead, through `aria-describedby`, as\n`Menu.Item` does: a reader hears \"Theme\", then \"Dark\".",
           "name": "HelixHeadlessDrilldownItem",
           "cssParts": [
             {
-              "description": "The row itself.",
+              "description": "The row itself, which is an `<a>` where `href` is set.",
               "name": "item"
             },
             {
@@ -59566,6 +59593,16 @@
               "attribute": "disabled",
               "reflects": true
             },
+            {
+              "kind": "field",
+              "name": "download",
+              "type": {
+                "text": "boolean"
+              },
+              "default": "false",
+              "description": "Whether the link downloads the file when the row is chosen. Only\nmeaningful beside an `href`, and only for a file served from this origin.",
+              "attribute": "download"
+            },
             {
               "kind": "field",
               "name": "focusable",
@@ -59575,6 +59612,36 @@
               "default": "false",
               "description": "Whether this row holds the region's tab stop. Set by the drill-down.\n\nA drill-down keeps one stop and moves within it on the arrows, so every\nother row is at `-1`. Leave it off every row, including the first, and\nnothing in the region is tab-reachable: the keyboard cannot get in without\nfirst clicking something with a pointer.\n\nNo attribute, the same as `Button`'s: this is coordination between\nelements, and writing `tabindex` onto a host the consumer rendered is a\nchange a React consumer's hydration reports and does not patch up. The stop\nlands inside this shadow root instead."
             },
+            {
+              "kind": "field",
+              "name": "href",
+              "type": {
+                "text": "string"
+              },
+              "default": "''",
+              "description": "The URL the row links to. Setting it renders the row as a link, unless the\nrow opens a page or is disabled.",
+              "attribute": "href"
+            },
+            {
+              "kind": "field",
+              "name": "rel",
+              "type": {
+                "text": "string"
+              },
+              "default": "''",
+              "description": "The link's `rel`. Set it whenever you set `target=\"_blank\"`.",
+              "attribute": "rel"
+            },
+            {
+              "kind": "field",
+              "name": "target",
+              "type": {
+                "text": "string"
+              },
+              "default": "''",
+              "description": "Where the link opens, for rows that should open outside the current page.",
+              "attribute": "target"
+            },
             {
               "kind": "field",
               "name": "value",
@@ -59683,6 +59750,41 @@
                 "text": "select() => void"
               }
             },
+            {
+              "kind": "method",
+              "name": "choose",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "boolean"
+                }
+              },
+              "description": "Fires `helix-select`, and returns whether the choice stood."
+            },
+            {
+              "kind": "field",
+              "name": "handleClick",
+              "privacy": "private",
+              "readonly": true,
+              "description": "A press on the row. On a link, a refused `helix-select` stops the link\nfrom being followed, so a router can take the navigation."
+            },
+            {
+              "kind": "field",
+              "name": "handleLinkKeydown",
+              "privacy": "private",
+              "readonly": true,
+              "description": "Space on a link presses it, which an anchor does not do on its own. Enter\nis the anchor's, which fires a click and follows the link."
+            },
+            {
+              "kind": "field",
+              "name": "linked",
+              "type": {
+                "text": "boolean"
+              },
+              "privacy": "private",
+              "description": "Whether the row renders as a link.",
+              "readonly": true
+            },
             {
               "kind": "method",
               "name": "renderMark",
@@ -60054,6 +60156,42 @@
               "description": "Whether the row can be reached at all.",
               "fieldName": "disabled"
             },
+            {
+              "name": "download",
+              "type": {
+                "text": "boolean"
+              },
+              "default": "false",
+              "description": "Whether the link downloads the file when the row is chosen. Only\nmeaningful beside an `href`, and only for a file served from this origin.",
+              "fieldName": "download"
+            },
+            {
+              "name": "href",
+              "type": {
+                "text": "string"
+              },
+              "default": "''",
+              "description": "The URL the row links to. Setting it renders the row as a link, unless the\nrow opens a page or is disabled.",
+              "fieldName": "href"
+            },
+            {
+              "name": "rel",
+              "type": {
+                "text": "string"
+              },
+              "default": "''",
+              "description": "The link's `rel`. Set it whenever you set `target=\"_blank\"`.",
+              "fieldName": "rel"
+            },
+            {
+              "name": "target",
+              "type": {
+                "text": "string"
+              },
+              "default": "''",
+              "description": "Where the link opens, for rows that should open outside the current page.",
+              "fieldName": "target"
+            },
             {
               "name": "value",
               "type": {
@@ -60122,7 +60260,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "One panel whose content changes as you move between pages. Use it where there\nis no room for a second column, such as on a phone, or on a touch screen with\nno hover to open one.\n\nIt is a region that stays where you put it, such as inside a drawer, a\nsidebar, or a settings panel. A `Menu` opens from a trigger and closes when\nyou are done. `Menu` can drill into pages too, through the same controller.\n\nRows are places to go and commands to run. Nothing here is form-associated\nand nothing is submitted. To choose a value, use a `Listbox`.\n\nA row that opens a page contains that page, so the stack holds one reference\nand reads the rest from the DOM. The behavior lives in `DrilldownController`,\nwhich `Menu` shares.\n\nAfter each move the host carries `data-direction`, `forward` into a page or\n`back` out of one, and records `:state(forward)` or `:state(back)`, so a\nstylesheet can slide the new page in from the side the reader is going. Both\nare written again on every move, so an animation keyed on them runs for each\npage, two moves the same way included. The styled tier slides the page and\nswaps it at once under `prefers-reduced-motion`.\n\nKeys, on a row: Up and Down Arrow move between the rows, Home and End go to\nthe first and the last, and a typed letter moves to the next row whose name\nstarts with it. Enter, Space, or Right Arrow opens a row's page, and Left\nArrow or Escape goes back, the two arrows swapping on a right-to-left page.\n\nThe rows of the page showing are a `menu`, named by `label` on the top page\nand by the page's title below it. The back button and the title sit above\nthe menu. Disabled rows stay reachable with the arrow keys, and typing a\nletter moves to the next row whose name starts with it.",
+          "description": "One panel whose content changes as you move between pages. Use it where there\nis no room for a second column, such as on a phone, or on a touch screen with\nno hover to open one.\n\nIt is a region that stays where you put it, such as inside a drawer, a\nsidebar, or a settings panel. A `Menu` opens from a trigger and closes when\nyou are done. `Menu` can drill into pages too, through the same controller.\n\nRows are places to go and commands to run. Nothing here is form-associated\nand nothing is submitted. To choose a value, use a `Listbox`.\n\nA row that opens a page contains that page, so the stack holds one reference\nand reads the rest from the DOM. The behavior lives in `DrilldownController`,\nwhich `Menu` shares.\n\n**`page` is the page showing**, as the `value` of the row that opens it,\nand empty on the top page. Set it to show a page, such as one a link to a\nsettings screen names. A reader's move updates it, and `helix-navigate`\ncomes first, so you can refuse the move or take it yourself.\n\nAfter each move the host carries `data-direction`, `forward` into a page or\n`back` out of one, and records `:state(forward)` or `:state(back)`, so a\nstylesheet can slide the new page in from the side the reader is going. Both\nare written again on every move, so an animation keyed on them runs for each\npage, two moves the same way included. The styled tier slides the page and\nswaps it at once under `prefers-reduced-motion`.\n\n**Keyboard.** The drilldown is one tab stop, on the row last focused.\n\n| Key | What it does |\n|---|---|\n| Down Arrow, Up Arrow | Moves to the next or the previous row. |\n| Home, End | Moves to the first or the last row. |\n| A letter | Moves to the next row whose name starts with it. |\n| Enter, Space | Chooses the row: opens its page, follows its link, or sends `helix-select`. |\n| Right Arrow | Opens the row's page. Left Arrow on a right-to-left page. |\n| Left Arrow, Escape | Goes back one page, with focus on the row that opened it. Right Arrow on a right-to-left page. |\n\nThe rows of the page showing are a `menu`, named by `label` on the top page\nand by the page's title below it.\n\n**`navigation` makes it a site's navigation.** The host is a `navigation`\nlandmark named by `label`, each page is a list, and each row is a list item\nholding a link or a button, as the APG's disclosure navigation is built,\nso a reader meets places to go in place of a menu of commands. The keys stay\nthe same. The back button and the title sit above\nthe menu. Disabled rows stay reachable with the arrow keys, and typing a\nletter moves to the next row whose name starts with it.",
           "name": "HelixHeadlessDrilldown",
           "cssParts": [
             {
@@ -60209,6 +60347,26 @@
                 "words": true
               }
             },
+            {
+              "kind": "field",
+              "name": "navigation",
+              "type": {
+                "text": "boolean"
+              },
+              "default": "false",
+              "description": "Whether the drilldown is a site's navigation: a `navigation` landmark\nnamed by `label`, whose pages are lists of links. Without it, each page is\na `menu`.",
+              "attribute": "navigation"
+            },
+            {
+              "kind": "field",
+              "name": "page",
+              "type": {
+                "text": "string"
+              },
+              "default": "''",
+              "description": "The page showing, as the `value` of the row that opens it. Empty is the\ntop page. Setting it shows that page, and a value no row with a page has\nshows the top page.",
+              "attribute": "page"
+            },
             {
               "kind": "field",
               "name": "direction",
@@ -60272,6 +60430,44 @@
               },
               "description": "Puts the region's one tab stop on the first row of the page showing.\n\nOne row holds the stop and the arrows move within, which is the roving\npattern the toolbar uses and the one a `menu` wants. Every row at `-1` is\na region the keyboard cannot get into at all without a pointer first.\n\nCalled after every update, because the set changes with the page: drilling\nin replaces the rows outright, and the stop has to land on rows that are\nactually showing."
             },
+            {
+              "kind": "method",
+              "name": "navigate",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "boolean"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "to",
+                  "type": {
+                    "text": "HelixHeadlessDrilldownItem | null"
+                  }
+                }
+              ],
+              "description": "Asks before a reader's move to a page, the row's or the top one, and\nreturns whether the move may go ahead."
+            },
+            {
+              "kind": "method",
+              "name": "holderOf",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "HelixHeadlessDrilldownItem | null"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "row",
+                  "type": {
+                    "text": "HelixHeadlessDrilldownItem"
+                  }
+                }
+              ],
+              "description": "The row whose page holds a row, or null for the top page."
+            },
             {
               "kind": "method",
               "name": "enter",
@@ -60304,6 +60500,25 @@
                 "text": "back() => boolean"
               }
             },
+            {
+              "kind": "method",
+              "name": "showPage",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "value",
+                  "type": {
+                    "text": "string"
+                  }
+                }
+              ],
+              "description": "Shows the page of the row with a value, or the top page where no row with a page has it."
+            },
             {
               "kind": "field",
               "name": "handleFocusIn",
@@ -60924,6 +61139,14 @@
             }
           ],
           "events": [
+            {
+              "type": {
+                "text": "HelixNavigateEvent"
+              },
+              "description": "Fired before a reader moves into a page or back out of one. `detail.value` is the `value` of the row whose page is about to show, empty for the top page. Cancelable: cancel it to stay on the page showing.",
+              "name": "helix-navigate",
+              "reactProp": "onhelix-navigate"
+            },
             {
               "type": {
                 "text": "HelixSelectEvent"
@@ -60952,6 +61175,24 @@
               "description": "The text of the back button.",
               "fieldName": "backLabel"
             },
+            {
+              "name": "navigation",
+              "type": {
+                "text": "boolean"
+              },
+              "default": "false",
+              "description": "Whether the drilldown is a site's navigation: a `navigation` landmark\nnamed by `label`, whose pages are lists of links. Without it, each page is\na `menu`.",
+              "fieldName": "navigation"
+            },
+            {
+              "name": "page",
+              "type": {
+                "text": "string"
+              },
+              "default": "''",
+              "description": "The page showing, as the `value` of the row that opens it. Empty is the\ntop page. Setting it shows that page, and a value no row with a page has\nshows the top page.",
+              "fieldName": "page"
+            },
             {
               "name": "empty-text",
               "type": {
@@ -64309,7 +64550,7 @@
                   "text": "HTMLElement | undefined"
                 }
               },
-              "description": "The tab stop after this element on the page, or the one before it at the\nend, for a lone element whose removal would drop focus to the body.\n\n**A lone Callout or Announcement had nowhere to hand focus**, so a\nkeyboard reader who dismissed one started again from the top of the\npage. React Aria's Toast hands focus on the same way. Read before the\nevent, in the order Tab reaches the stops, while this element's own are\nstill among them.",
+              "description": "The tab stop after this element on the page, or the one before it at the\nend, for an element whose removal would drop focus to the body because\nno neighbor of its kind has a control to take it.\n\n**A lone Callout or Announcement had nowhere to hand focus**, so a\nkeyboard reader who dismissed one started again from the top of the\npage. React Aria's Toast hands focus on the same way. Read before the\nevent, in the order Tab reaches the stops, while this element's own are\nstill among them.",
               "inheritedFrom": {
                 "name": "MixinDismissible",
                 "module": "src/mixins/mixin-dismissible/mixin-dismissible.ts"
@@ -65511,6 +65752,10 @@
               "description": "The leading column.",
               "name": "entry-start"
             },
+            {
+              "description": "The panel a row's submenu opens in beside it. The filter menu's rows have none.",
+              "name": "entry-surface"
+            },
             {
               "description": "The menu the fields are offered in.",
               "name": "menu"
@@ -88415,7 +88660,7 @@
                 "text": "boolean"
               },
               "default": "false",
-              "description": "Takes the row out of reach in a list with `selection-mode`: the arrow keys\npass over it and it cannot be selected or acted on.",
+              "description": "Takes the row out of reach in a list with `selection-mode`: the arrow keys\npass over it and it cannot be selected or acted on. In a list with\n`disabled-behavior=\"selection\"`, it cannot be selected and is reached and\nacted on as any row is.",
               "attribute": "disabled",
               "reflects": true
             },
@@ -88471,6 +88716,15 @@
               },
               "description": "Whether the row is selected, in a list that selects.\n\nWritten by the list from its own `value`, and unset where nothing can be\nselected, which keeps `aria-selected` off a list that does not select."
             },
+            {
+              "kind": "field",
+              "name": "selectionOnly",
+              "type": {
+                "text": "boolean"
+              },
+              "default": "false",
+              "description": "Whether `disabled` takes the row out of selection alone, written by a list\nwith `disabled-behavior=\"selection\"`. No attribute: it is coordination\nbetween elements, as `focusable` is."
+            },
             {
               "kind": "field",
               "name": "target",
@@ -88520,6 +88774,13 @@
               "description": "Whether a list with `selection-mode` holds this row, which makes it a row of a grid.",
               "readonly": true
             },
+            {
+              "kind": "field",
+              "name": "handleCellFocus",
+              "privacy": "private",
+              "readonly": true,
+              "description": "Says whether the cell shows keyboard focus, as `:focus-visible` does, so a\nsheet outside can draw the ring on the row by the host."
+            },
             {
               "kind": "method",
               "name": "focusItem",
@@ -88920,7 +89181,7 @@
                 "text": "boolean"
               },
               "default": "false",
-              "description": "Takes the row out of reach in a list with `selection-mode`: the arrow keys\npass over it and it cannot be selected or acted on.",
+              "description": "Takes the row out of reach in a list with `selection-mode`: the arrow keys\npass over it and it cannot be selected or acted on. In a list with\n`disabled-behavior=\"selection\"`, it cannot be selected and is reached and\nacted on as any row is.",
               "fieldName": "disabled"
             },
             {
@@ -88973,6 +89234,10 @@
               "description": "The row being moved goes before this one when it is dropped.",
               "name": "drop-before"
             },
+            {
+              "description": "The row's cell has keyboard focus that the browser shows, in a list with `selection-mode`.",
+              "name": "focus-visible"
+            },
             {
               "description": "The row is selected, in a list that selects.",
               "name": "selected"
@@ -89080,7 +89345,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "Sets `role=\"list\"` on the host, so a screen reader counts the rows and\nannounces each one's position, such as \"1 of 7\".\n\n**`selection-mode` makes the list interactive**, in the way of a grid list:\na grid of rows that is one tab stop. `single` selects one row at a time and\n`multiple` any number, and `value` holds the selected rows' values,\nseparated by commas. A change asks with `helix-before-change` and tells\nwith `change`. `none` selects nothing, so a press acts on the row. A\n`disabled` row is passed over. Each row is named by its label and described\nby its description, so the words of the controls in `end` are not read as\npart of its name.\n\n`selection-behavior` says what a press does to the rows already selected.\n`toggle`, the default, adds or takes out the row. `replace` selects the row\nalone, as a file list does, and the arrow keys carry the selection with\nthem. Control or Command with a press then adds or takes out one row.\n\n| Key | What it does |\n|---|---|\n| Down, Up | Moves to the next or the previous row. Under `replace`, selects it. |\n| Home, End | Moves to the first or the last row. Under `replace`, selects it. |\n| Page Down, Page Up | Moves a box's height of rows, so the row at one edge lands at the other. Under `replace`, selects the row it lands on. |\n| A letter or a word | Moves to the next row whose words start with what you typed. |\n| Left, Right | Moves between the row and the controls in its `end` slot. |\n| Space | Selects the row, or lets it go. |\n| Shift with Down, Up, Home, End, Page Down, Page Up or Space | Selects every row from the last one pressed, in `multiple`. |\n| Control or Command with Down, Up, Home, End, Page Down or Page Up | Moves without selecting, under `replace`. |\n| Control or Command with A | Selects every row, in `multiple`. |\n| Escape | Lets go of every selected row, asking first, and keeps the key from the dialog or menu around the list. With nothing selected, the key goes on to them. |\n| Enter | Acts on the row: follows its link, or sends `helix-action` from it. |\n\nA press with Shift selects every row from the last one pressed, and a press\nwith Control or Command adds or takes out one row under `replace`.\n\n**Leave `selection-mode` unset for a list a reader reads**, and set it for\none a reader chooses from or acts on. The rows of an interactive list are\ngrid rows, which hold controls as a list box option cannot. Give a control\nin `end` `tabindex=\"-1\"` to leave it to the arrow keys and out of the tab\norder.\n\n**`reorderable` lets you move rows.** Each row gets a grip after its `end`\nslot, named by `move-label`. Drag a grip to move its row, and the list\nscrolls near an edge. Or press a grip with Space, Enter, or a click to pick\nup its row, move it with the arrow keys, and press the grip again to drop\nit. A click on another row drops it there, and Escape puts it back. The list\nsays each step in its `live` region. A drop sends `helix-before-reorder`,\nwhich you can refuse, and then `helix-reorder`, whose `keys` hold every\nrow's value in the new order. **You move the rows**: the list moves no\nelement of yours, so your framework keeps the order it rendered.\n\n| Key, on a held row's grip | What it does |\n|---|---|\n| Down, Up | Moves the row one place. |\n| Home, End | Moves the row to the top or the bottom. |\n| Space, Enter | Drops the row. |\n| Escape | Puts the row back where it was. |\n\n`start` and `reversed` number an ordered list as `<ol>` does. The list\nwrites where the numbers start and which way they run as `--list-first` and\n`--list-step` on its slot, which the styled tier counts from. Reversed with\nno `start` counts down from the number of rows, which a server cannot know,\nso served markup counts from one until the list runs.\n\n**An empty list.** Set `empty-label`, or put your own content in the `empty`\nslot, for a row shown while the list has no rows and none are loading, such\nas \"No files yet\" and a link to add one. Without either, an empty list shows\nnothing. The list takes the `empty` state while it has no rows, whatever it\nshows.\n\n**Loading more.** `load-more` sends `helix-load-more` once the end of the\nlist comes within a screen of view, in the box that scrolls it or the page,\nonce for each number of rows: add rows and it can send it again. While you\nfetch, set `loading`: the list is busy, and a row after the last says\n\"Loading more\" (`loading-label`, or your own content in the `loading`\nslot). The list asks for nothing while `loading` is set.\n\nAn interactive list with no name is reported once in a development build,\nsince a screen reader announces it as a grid and nothing more. Name it with\n`label` or `aria-label`.",
+          "description": "Sets `role=\"list\"` on the host, so a screen reader counts the rows and\nannounces each one's position, such as \"1 of 7\".\n\n**`selection-mode` makes the list interactive**, in the way of a grid list:\na grid of rows that is one tab stop. `single` selects one row at a time and\n`multiple` any number, and `value` holds the selected rows' values,\nseparated by commas. A change asks with `helix-before-change` and tells\nwith `change`. `none` selects nothing, so a press acts on the row. A\n`disabled` row is passed over. With `disabled-behavior=\"selection\"`, a\n`disabled` row cannot be selected, and is reached and acted on as any row\nis, as React Aria's GridList has it. Each row is named by its label and described\nby its description, so the words of the controls in `end` are not read as\npart of its name.\n\n`selection-behavior` says what a press does to the rows already selected.\n`toggle`, the default, adds or takes out the row. `replace` selects the row\nalone, as a file list does, and the arrow keys carry the selection with\nthem. Control or Command with a press then adds or takes out one row.\n\n| Key | What it does |\n|---|---|\n| Down, Up | Moves to the next or the previous row. Under `replace`, selects it. |\n| Home, End | Moves to the first or the last row. Under `replace`, selects it. |\n| Page Down, Page Up | Moves a box's height of rows, so the row at one edge lands at the other. Under `replace`, selects the row it lands on. |\n| A letter or a word | Moves to the next row whose words start with what you typed. |\n| Left, Right | Moves between the row and the controls in its `end` slot. |\n| Space | Selects the row, or lets it go. |\n| Shift with Down, Up, Home, End, Page Down, Page Up or Space | Selects every row from the last one pressed, in `multiple`. |\n| Control or Command with Down, Up, Home, End, Page Down or Page Up | Moves without selecting, under `replace`. |\n| Control or Command with A | Selects every row, in `multiple`. |\n| Escape | Lets go of every selected row, asking first, and keeps the key from the dialog or menu around the list. With nothing selected, the key goes on to them. |\n| Enter | Acts on the row: follows its link, or sends `helix-action` from it. |\n\nA press with Shift selects every row from the last one pressed, and a press\nwith Control or Command adds or takes out one row under `replace`.\n\n**Leave `selection-mode` unset for a list a reader reads**, and set it for\none a reader chooses from or acts on. The rows of an interactive list are\ngrid rows, which hold controls as a list box option cannot. Give a control\nin `end` `tabindex=\"-1\"` to leave it to the arrow keys and out of the tab\norder.\n\n**`reorderable` lets you move rows.** Each row gets a grip after its `end`\nslot, named by `move-label`. Drag a grip to move its row, and the list\nscrolls near an edge. Or press a grip with Space, Enter, or a click to pick\nup its row, move it with the arrow keys, and press the grip again to drop\nit. A click on another row drops it there, and Escape puts it back. The list\nsays each step in its `live` region. A drop sends `helix-before-reorder`,\nwhich you can refuse, and then `helix-reorder`, whose `keys` hold every\nrow's value in the new order. **You move the rows**: the list moves no\nelement of yours, so your framework keeps the order it rendered.\n\n| Key, on a held row's grip | What it does |\n|---|---|\n| Down, Up | Moves the row one place. |\n| Home, End | Moves the row to the top or the bottom. |\n| Space, Enter | Drops the row. |\n| Escape | Puts the row back where it was. |\n\n`start` and `reversed` number an ordered list as `<ol>` does. The list\nwrites where the numbers start and which way they run as `--list-first` and\n`--list-step` on its slot, which the styled tier counts from. Reversed with\nno `start` counts down from the number of rows, which a server cannot know,\nso served markup counts from one until the list runs.\n\n**An empty list.** Set `empty-label`, or put your own content in the `empty`\nslot, for a row shown while the list has no rows and none are loading, such\nas \"No files yet\" and a link to add one. Without either, an empty list shows\nnothing. The list takes the `empty` state while it has no rows, whatever it\nshows.\n\n**Loading more.** `load-more` sends `helix-load-more` once the end of the\nlist comes within a screen of view, in the box that scrolls it or the page,\nonce for each number of rows: add rows and it can send it again. While you\nfetch, set `loading`: the list is busy, and a row after the last says\n\"Loading more\" (`loading-label`, or your own content in the `loading`\nslot). The list asks for nothing while `loading` is set.\n\nAn interactive list with no name is reported once in a development build,\nsince a screen reader announces it as a grid and nothing more. Name it with\n`label` or `aria-label`.",
           "name": "HelixHeadlessList",
           "cssProperties": [
             {
@@ -89148,6 +89413,15 @@
                 "words": true
               }
             },
+            {
+              "kind": "field",
+              "name": "disabledBehavior",
+              "type": {
+                "text": "'all' | 'selection' | undefined | undefined"
+              },
+              "description": "What `disabled` takes from a row, in a list that selects: `all`, which\npasses over the row, or `selection`, which keeps the row out of the\nselection and lets the keys reach it and Enter or a press act on it, as\nReact Aria's GridList takes `disabledBehavior`.\n\nAbsent is `all`.",
+              "attribute": "disabled-behavior"
+            },
             {
               "kind": "field",
               "name": "droppedLabel",
@@ -89293,6 +89567,35 @@
               "description": "What a press does to the rows already selected, in a list that selects:\n`toggle` adds or takes out the row, and `replace` selects it alone and\nlets the arrow keys carry the selection.",
               "attribute": "selection-behavior"
             },
+            {
+              "kind": "method",
+              "name": "blocked",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "boolean"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "row",
+                  "type": {
+                    "text": "HelixHeadlessListItem"
+                  }
+                }
+              ],
+              "description": "Whether the row is out of reach of the keys and of actions, past selection."
+            },
+            {
+              "kind": "field",
+              "name": "selectable",
+              "type": {
+                "text": "HelixHeadlessListItem[]"
+              },
+              "privacy": "private",
+              "description": "The rows a key can land on that can also be selected.",
+              "readonly": true
+            },
             {
               "kind": "field",
               "name": "selectionMode",
@@ -89340,6 +89643,16 @@
               "privacy": "private",
               "description": "The row the reader was last on, which keeps the tab stop."
             },
+            {
+              "kind": "field",
+              "name": "placed",
+              "type": {
+                "text": "HelixHeadlessListItem[]"
+              },
+              "privacy": "private",
+              "default": "[]",
+              "description": "The rows in order on the last `sync`, so a removed row's place is known."
+            },
             {
               "kind": "field",
               "name": "anchor",
@@ -89539,6 +89852,25 @@
               },
               "description": "Tells every row its place: whether it holds the one tab stop and whether\nit is selected, or that it is a plain row. Through `whenHydrated`, so a\nrow a server rendered draws its served markup first."
             },
+            {
+              "kind": "method",
+              "name": "followRemoved",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "rows",
+                  "type": {
+                    "text": "HelixHeadlessListItem[]"
+                  }
+                }
+              ],
+              "description": "Moves the tab stop off a row the page removed, to the next row a key can\nreach or, at the end, the one before it, and moves focus there where\nremoving the row dropped it to the body.\n\n**Focus went to the body**, and the arrow keys did nothing until the\nreader tabbed back into the list. React Aria's GridList moves focus to a\nneighbor the same way. Focus anywhere but the body is where you put it,\nand is left there."
+            },
             {
               "kind": "method",
               "name": "rowOf",
@@ -90263,6 +90595,14 @@
               "description": "What screen readers hear when a held row is put back, or a move is\nrefused, in a `reorderable` list.",
               "fieldName": "canceledLabel"
             },
+            {
+              "name": "disabled-behavior",
+              "type": {
+                "text": "'all' | 'selection' | undefined | undefined"
+              },
+              "description": "What `disabled` takes from a row, in a list that selects: `all`, which\npasses over the row, or `selection`, which keeps the row out of the\nselection and lets the keys reach it and Enter or a press act on it, as\nReact Aria's GridList takes `disabledBehavior`.\n\nAbsent is `all`.",
+              "fieldName": "disabledBehavior"
+            },
             {
               "name": "dropped-label",
               "type": {
@@ -90858,7 +91198,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "The listbox is the control, and options are its items. A Select is a listbox\nwith a trigger in front of it, a Combobox is a listbox with a text input, and\na command palette is a listbox in a dialog. They differ only in what opens\nthe list and what filters it.\n\nWith `multiple` set, `value` is a comma-separated string, like\n`Checkbox.Group`'s, because `MixinControllerValue` holds a string. The form\nreceives one entry per selected option, as a native `<select multiple>` sends\nit, so your server does not split on commas.\n\nSelected and active are separate. The selected option is the value. The\nactive option is where the keyboard is: the arrow keys move it, and\n`aria-activedescendant` points to it while focus stays on the list.\n\n**Keyboard.** The list is one tab stop, or its filter field is where there\nis one. In a single-choice list the highlight is the choice unless `manual`\nis set; then Enter, Space or a click chooses.\n\n| Key | What it does |\n|---|---|\n| Down, Up | Moves the highlight to the next or the previous option, round from the last to the first. With `layout=\"grid\"`, to the option below or above, stopping at the edge. |\n| Right, Left | With `layout=\"grid\"`, moves to the next or the previous option, mirrored right to left. In a filter field, moves the caret. |\n| Home, End | Moves to the first or the last option. In a filter field, moves the caret. |\n| Page Down, Page Up | Moves by as many options as the list shows at once. |\n| A letter or a word | Moves to the next option whose words start with what you typed. In a filter field, types it. |\n| Enter | Chooses the highlighted option, or follows it where it is a link. |\n| Space | Chooses the highlighted option, or with `multiple` toggles it. In a filter field, types a space. |\n| Shift with Down or Up | With `multiple`, adds the option the highlight moves to. In a filter field, moves the highlight and leaves the value. |\n| Shift with Space | With `multiple`, adds every option from the one last chosen to the highlighted one. In a filter field, types a space. |\n| Shift with Home or End | With `multiple`, adds every option from the highlight to that end. In a filter field, hold Control as well. |\n| Control or Command with A | With `multiple`, chooses every option, or none where all are chosen. In a filter field, selects the text. |\n| Escape | In a filter field, clears the filter. |\n| Alt with Up or Down | In a `reorderable` list, moves the highlighted option a place. Alt with Home or End moves it to either end. |\n\n**ARIA.** The `items` part is the `listbox`, named by the label and\ndescribed by the hint and the message, with `aria-multiselectable` under\n`multiple`, `aria-required`, `aria-invalid`, and `aria-busy` while loading.\nEach option is an `option` with `aria-selected`. The list, or its filter\nfield, points `aria-activedescendant` at the highlighted option; the field\nis `aria-autocomplete=\"list\"` and controls the list.\n\nAn option with `href` is a link: Enter or a press follows it and selects\nnothing, and moving onto it with the arrows does not follow it.\n\nAs a filter narrows the list, a screen reader hears how many options are\nleft, such as \"3 results\", from `result-label` and `results-label`. A filter\nthat leaves none says `empty-text`.\n\n**Moving options** is a separate import, `@fusion.dev/helix/listbox/reorder`,\nso a list that never moves options carries none of its code. With it\nimported, `reorderable` lets a reader move options:\n\n- Alt with Up or Down moves the highlighted option a place, and Alt with\n  Home or End moves it to either end, as the APG's rearrangeable listbox\n  does. The highlight stays on it.\n- A pointer drags an option, with a drop indicator, and the list scrolls near\n  an edge. A press that does not travel still chooses the option.\n- A drop sends `helix-before-reorder`, which you can refuse, and then\n  `helix-reorder`, whose `keys` hold every value in the new order. **You\n  move the options**, or set `items` in the new order: the list moves no\n  element of yours.\n- The list says each move in its `live` region. The words are the\n  `moved-label`, `canceled-label`, `dropped-label`, and `picked-up-label`\n  attributes, which the import reads.\n- An option in a group moves within its group. Options do not move while a\n  filter narrows the list, under `layout=\"grid\"`, or while the list is\n  disabled.",
+          "description": "The listbox is the control, and options are its items. A Select is a listbox\nwith a trigger in front of it, a Combobox is a listbox with a text input, and\na command palette is a listbox in a dialog. They differ only in what opens\nthe list and what filters it.\n\nWith `multiple` set, `value` is a comma-separated string, like\n`Checkbox.Group`'s, because `MixinControllerValue` holds a string. The form\nreceives one entry per selected option, as a native `<select multiple>` sends\nit, so your server does not split on commas. An option's value may hold a\ncomma: a run of the string that is an option's value is read as that one\nvalue, and the form sends it as one entry.\n\nSelected and active are separate. The selected option is the value. The\nactive option is where the keyboard is: the arrow keys move it, and\n`aria-activedescendant` points to it while focus stays on the list.\n\n**Keyboard.** The list is one tab stop, or its filter field is where there\nis one. In a single-choice list the highlight is the choice unless `manual`\nis set; then Enter, Space or a click chooses.\n\n| Key | What it does |\n|---|---|\n| Down, Up | Moves the highlight to the next or the previous option, round from the last to the first. With `layout=\"grid\"`, to the option below or above, stopping at the edge. |\n| Right, Left | With `layout=\"grid\"`, moves to the next or the previous option, mirrored right to left. In a filter field, moves the caret. |\n| Home, End | Moves to the first or the last option. In a filter field, moves the caret. |\n| Page Down, Page Up | Moves by as many options as the list shows at once. |\n| A letter or a word | Moves to the next option whose words start with what you typed. In a filter field, types it. |\n| Enter | Chooses the highlighted option, or follows it where it is a link. |\n| Space | Chooses the highlighted option, or with `multiple` toggles it. In a filter field, types a space. |\n| Shift with Down or Up | With `multiple`, adds the option the highlight moves to. In a filter field, moves the highlight and leaves the value. |\n| Shift with Space | With `multiple`, adds every option from the one last chosen to the highlighted one. In a filter field, types a space. |\n| Shift with Home or End | With `multiple`, adds every option from the highlight to that end. In a filter field, hold Control as well. |\n| Control or Command with A | With `multiple`, chooses every option, or none where all are chosen. In a filter field, selects the text. |\n| Escape | In a filter field, clears the filter. |\n| Alt with Up or Down | In a `reorderable` list, moves the highlighted option a place. Alt with Home or End moves it to either end. |\n\n**ARIA.** The `items` part is the `listbox`, named by the label and\ndescribed by the hint and the message, with `aria-multiselectable` under\n`multiple`, `aria-required`, `aria-invalid`, and `aria-busy` while loading.\nEach option is an `option` with `aria-selected`. The list, or its filter\nfield, points `aria-activedescendant` at the highlighted option; the field\nis `aria-autocomplete=\"list\"` and controls the list.\n\nAn option with `href` is a link: Enter or a press follows it and selects\nnothing, and moving onto it with the arrows does not follow it.\n\nAs a filter narrows the list, a screen reader hears how many options are\nleft, such as \"3 results\", from `result-label` and `results-label`. A filter\nthat leaves none says `empty-text`.\n\n**Moving options** is a separate import, `@fusion.dev/helix/listbox/reorder`,\nso a list that never moves options carries none of its code. With it\nimported, `reorderable` lets a reader move options:\n\n- Alt with Up or Down moves the highlighted option a place, and Alt with\n  Home or End moves it to either end, as the APG's rearrangeable listbox\n  does. The highlight stays on it.\n- A pointer drags an option, with a drop indicator, and the list scrolls near\n  an edge. A press that does not travel still chooses the option.\n- A drop sends `helix-before-reorder`, which you can refuse, and then\n  `helix-reorder`, whose `keys` hold every value in the new order. **You\n  move the options**, or set `items` in the new order: the list moves no\n  element of yours.\n- The list says each move in its `live` region. The words are the\n  `moved-label`, `canceled-label`, `dropped-label`, and `picked-up-label`\n  attributes, which the import reads.\n- An option in a group moves within its group. Options do not move while a\n  filter narrows the list, under `layout=\"grid\"`, or while the list is\n  disabled.",
           "name": "HelixHeadlessListbox",
           "cssParts": [
             {
@@ -91060,6 +91400,14 @@
                 "words": true
               }
             },
+            {
+              "kind": "field",
+              "name": "filterMatch",
+              "type": {
+                "text": "((text: string, filter: string) => boolean) | undefined | undefined"
+              },
+              "description": "Whether an option is kept by the filter: a function given the option's\nwords and the filter, trimmed, that returns `true` to keep it showing, as\nReact Aria's `Autocomplete` takes `filter`. For matching that ignores\naccents, matches the start of each word, or matches out of order.\n\nAbsent, an option is kept where its words hold the filter, in any case. A\nproperty only, there being no way to write a function in markup."
+            },
             {
               "kind": "field",
               "name": "items",
@@ -91416,7 +91764,7 @@
               "type": {
                 "text": "string[]"
               },
-              "description": "The chosen values, as an array whether or not `multiple` is set.",
+              "description": "The chosen values, as an array whether or not `multiple` is set.\n\nRead against the options' values, so an option whose value holds a comma\nis one value. See `chosenValues`.",
               "readonly": true
             },
             {
@@ -100272,7 +100620,7 @@
               "name": "handlePartChange",
               "privacy": "private",
               "readonly": true,
-              "description": "A route or area renamed, or its description changed, which the list says\nand a slot change does not report."
+              "description": "A route or area renamed, or its description changed, which the list says\nand a slot change does not report.\n\nNot the map's own `gestures` news, which it sends from `updated` and which\nchanges nothing it draws: an update asked for there ran every map's\nupdate twice, and Lit's development build warned about it."
             },
             {
               "kind": "field",
@@ -103676,7 +104024,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "A disclosure: a button that shows and hides a region of your own links. It\ndoes not use `role=\"menu\"` or `menuitem`, which are for application commands.\nThose roles take over the arrow keys, announce \"menu\" to someone looking for\nnavigation, and put every link inside a role that is not a link. As a\ndisclosure, middle clicks, modified clicks, and the status bar keep working.\nUse `Menu` for a row of commands.\n\nIt renders no links. A router renders its own anchors and cannot render them\ninside this shadow root, so the panel is a slot for the lists and headings\nyou write.\n\nIt opens on hover by default, and a press always opens it too. `open-on` sets\nwhich. Hover is the default because in a navigation bar people expect to move\nalong the row and see each section.\n\nWhen one panel opens in place of another, each says which way the reader\nmoved, as Radix's `data-motion` does. Moving toward the end of the bar, the\none opening is `:state(from-end)` and the one closing is `:state(to-start)`;\nmoving back, they are `:state(from-start)` and `:state(to-end)`. A\nstylesheet slides them on that. Start and end follow the reading direction,\nso on a right-to-left page the end is on the left. A panel that opens or\ncloses on its own carries none of the four. A press on another megamenu's\ntrigger hands over the same way as hovering it.\n\nWhile a panel is open its surface carries its own size, as\n`--megamenu-surface-inline-size` and `--megamenu-surface-block-size`, and a\npanel that took over from another also carries that one's size, as\n`--megamenu-from-inline-size` and `--megamenu-from-block-size`. Radix's\nnavigation menu publishes the same pair from its shared viewport, so a\nstylesheet can grow or shrink one panel into the next.\n\nThe panel's default slot is the `columns` part and draws no box, so a sheet\ncan give the columns one of their own. While a panel is open, an\n`indicator` slot is rendered beside its trigger, as Radix's indicator\nmarks the open one: slot a mark of your own, such as a bar or an arrow\npointing at the panel, and it shows only while the panel is open. The styled\ntier rests it on the trigger's bottom edge.\n\nLeft and Right Arrow move between the triggers of the megamenus beside this\none, and Home and End go to the first and the last, as Radix's navigation\nmenu does. In a `Navigation`, which holds them in a slot, the arrows are the\nnavigation's, and move between its destinations under its `arrows`. Down Arrow on the trigger of an open panel moves\nfocus to the panel's first link, Escape closes the panel and returns focus\nto its trigger, and Tab moves through the panel's links and closes it on the\nway out. The trigger says `aria-expanded`, and the panel is a group named by\n`label`.",
+          "description": "A disclosure: a button that shows and hides a region of your own links. It\ndoes not use `role=\"menu\"` or `menuitem`, which are for application commands.\nThose roles take over the arrow keys, announce \"menu\" to someone looking for\nnavigation, and put every link inside a role that is not a link. As a\ndisclosure, middle clicks, modified clicks, and the status bar keep working.\nUse `Menu` for a row of commands.\n\nIt renders no links. A router renders its own anchors and cannot render them\ninside this shadow root, so the panel is a slot for the lists and headings\nyou write.\n\nIt opens on hover by default, and a press always opens it too. `open-on` sets\nwhich. Hover is the default because in a navigation bar people expect to move\nalong the row and see each section. A pointer resting on the trigger opens\nthe panel after `open-delay`, and leaving closes it after `close-delay`. Moving\nfrom one open panel's trigger to another's opens the next at once, as Radix's\n`skipDelayDuration` does.\n\nWhen one panel opens in place of another, each says which way the reader\nmoved, as Radix's `data-motion` does. Moving toward the end of the bar, the\none opening is `:state(from-end)` and the one closing is `:state(to-start)`;\nmoving back, they are `:state(from-start)` and `:state(to-end)`. A\nstylesheet slides them on that. Start and end follow the reading direction,\nso on a right-to-left page the end is on the left. A panel that opens or\ncloses on its own carries none of the four. A press on another megamenu's\ntrigger hands over the same way as hovering it.\n\nWhile a panel is open its surface carries its own size, as\n`--megamenu-surface-inline-size` and `--megamenu-surface-block-size`, and a\npanel that took over from another also carries that one's size, as\n`--megamenu-from-inline-size` and `--megamenu-from-block-size`. Radix's\nnavigation menu publishes the same pair from its shared viewport, so a\nstylesheet can grow or shrink one panel into the next.\n\nWhile a link in the panel carries `aria-current=\"page\"`, the host has\n`:state(current)`, so the trigger of the section holding the page you are\non can say so, as Radix's navigation menu marks its active link.\n\nThe panel's default slot is the `columns` part and draws no box, so a sheet\ncan give the columns one of their own. While a panel is open, an\n`indicator` slot is rendered beside its trigger, as Radix's indicator\nmarks the open one: slot a mark of your own, such as a bar or an arrow\npointing at the panel, and it shows only while the panel is open. The styled\ntier rests it on the trigger's bottom edge.\n\nLeft and Right Arrow move between the triggers of the megamenus beside this\none, and Home and End go to the first and the last, as Radix's navigation\nmenu does. In a `Navigation`, which holds them in a slot, the arrows are the\nnavigation's, and move between its destinations under its `arrows`. Down Arrow on the trigger of an open panel moves\nfocus to the panel's first link, Escape closes the panel and returns focus\nto its trigger, and Tab moves through the panel's links and closes it on the\nway out. The trigger says `aria-expanded`, and the panel is a group named by\n`label`.\n\nA Helix trigger, such as `helix-button`, is told whether the panel is open\ninside its own shadow root. On a plain element, such as a `<button>`, the\nmegamenu writes `aria-expanded`, from a frame after its own first render, so\na server's markup is never changed while a framework hydrates it. It never\nwrites it where you wrote `aria-expanded` yourself.",
           "name": "HelixHeadlessMegamenu",
           "cssProperties": [
             {
@@ -103752,6 +104100,16 @@
               "description": "The page width, in pixels, below which a card panel is shown as a band. At\nzero, it never is.\n\nA card is a panel hung off one word, and there is no room to hang anything\noff a word on a phone: the columns do not shrink past\n`--megamenu-column-size`, so four of them stay four of them and the panel\nruns off the side of the screen rather than reflowing. Below this it takes\nthe whole width and its columns stack, which is the only arrangement that\nfits.\n\n**In script rather than a media query, and only once.** Whether the panel is\na band is not a question of paint: a band is not placed against the trigger,\nso the controller has to be told not to measure, and that decision is here\nwhatever the stylesheet says. Writing the width in both places would be one\nnumber in two languages, drifting the first time either moved. This records\n`:state(narrow)` on the host and the stylesheet arranges itself off that.\n\n**A custom state and never `data-narrow`, which is what it was.** The width\nis read in `connectedCallback`, so on a phone this is true on the very first\nupdate: an attribute written there is markup a consumer's server never sent,\nwhich React reports as a mismatch and answers by rebuilding the subtree. The\nnarrow exception the server specs describe covers a mirror that can only\nbecome true long after hydration, and a viewport measured before the first\npaint is the opposite case. See `MixinControllerOpen` on `open`.",
               "attribute": "band-below"
             },
+            {
+              "kind": "field",
+              "name": "closeDelay",
+              "type": {
+                "text": "number"
+              },
+              "default": "220",
+              "description": "How long a pointer leaving the trigger and the panel waits before the panel\ncloses, in milliseconds. The pointer needs the time to cross from the\ntrigger to the panel.",
+              "attribute": "close-delay"
+            },
             {
               "kind": "field",
               "name": "label",
@@ -103762,6 +104120,16 @@
               "description": "The section's name, used for the default trigger and the panel.",
               "attribute": "label"
             },
+            {
+              "kind": "field",
+              "name": "openDelay",
+              "type": {
+                "text": "number"
+              },
+              "default": "120",
+              "description": "How long a pointer rests on the trigger before the panel opens, in\nmilliseconds, under `open-on=\"hover\"`. A pointer crossing the bar on its\nway somewhere else opens nothing.",
+              "attribute": "open-delay"
+            },
             {
               "kind": "field",
               "name": "openOn",
@@ -103772,6 +104140,16 @@
               "description": "Whether hovering over the trigger opens the panel (`hover`), or only a press\ndoes (`click`).\n\nA press always works. This says whether a mouse also opens it by resting on\nthe trigger, and it is the default because that is what a navigation bar\ndoes. `click` is for a trigger that does something else as well, or a panel\nheavy enough that opening it on the way past is rude.",
               "attribute": "open-on"
             },
+            {
+              "kind": "field",
+              "name": "placement",
+              "type": {
+                "text": "'bottom' | 'bottom-end' | 'bottom-start' | 'left' | 'left-end' | 'left-start' | 'right' | 'right-end' | 'right-start' | 'top' | 'top-end' | 'top-start'"
+              },
+              "default": "'bottom-start'",
+              "description": "The side of the trigger a card panel opens on, when there is room. It\nmoves if that side does not fit. A band ignores it, since a band spans the\npage under its bar.",
+              "attribute": "placement"
+            },
             {
               "kind": "field",
               "name": "variant",
@@ -103830,7 +104208,7 @@
               "name": "panel",
               "privacy": "protected",
               "readonly": true,
-              "default": "new PopoverController(this, { anchor: () => this.trigger, /* The host, not the panel. A press on the trigger is a press on this element, and counting it as outside would close the panel on the way to the click that toggles it. `Menu` says the same about its own. Every other megamenu too: a press on one of them opens it, and opening it closes this one with a direction. */ boundary: () => [...HelixHeadlessMegamenu.bar.connected], onDismiss: () => this.close(), open: () => this.open, place: () => !this.banded, placement: () => 'bottom-start', surface: () => this.partNamed('surface'), })"
+              "default": "new PopoverController(this, { anchor: () => this.trigger, /* The host, not the panel. A press on the trigger is a press on this element, and counting it as outside would close the panel on the way to the click that toggles it. `Menu` says the same about its own. Every other megamenu too: a press on one of them opens it, and opening it closes this one with a direction. */ boundary: () => [...HelixHeadlessMegamenu.bar.connected], onDismiss: () => this.close(), open: () => this.open, place: () => !this.banded, placement: () => this.placement, surface: () => this.partNamed('surface'), })"
             },
             {
               "kind": "method",
@@ -103841,7 +104219,26 @@
                   "text": "void"
                 }
               },
-              "description": "Tells a slotted trigger the disclosure state, by property. See `tellDisclosure`."
+              "description": "Tells a slotted trigger the disclosure state.\n\nA Helix trigger by property, through `tellDisclosure`. A plain element,\nwhich has no shadow root to keep the state out of the markup, by\n`aria-expanded`, from a frame after the first render, as `Popover` writes\nit. One that already carries `aria-expanded` is the consumer's to keep."
+            },
+            {
+              "kind": "field",
+              "name": "settledOnce",
+              "type": {
+                "text": "boolean"
+              },
+              "privacy": "private",
+              "default": "false",
+              "description": "Whether a frame has passed since the first render, after which a plain trigger may be told."
+            },
+            {
+              "kind": "field",
+              "name": "told",
+              "type": {
+                "text": "Element | undefined"
+              },
+              "privacy": "private",
+              "description": "The plain trigger this megamenu writes `aria-expanded` on."
             },
             {
               "kind": "field",
@@ -103878,6 +104275,26 @@
               "readonly": true,
               "description": "Down Arrow on the trigger of an open panel moves focus to the panel's first\nlink or control, as Radix's navigation menu does."
             },
+            {
+              "kind": "field",
+              "name": "currentWatch",
+              "type": {
+                "text": "MutationObserver | undefined"
+              },
+              "privacy": "private",
+              "description": "Watches the panel's links for the one that is the page you are on."
+            },
+            {
+              "kind": "method",
+              "name": "markCurrent",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "description": "Records whether a link in the panel is the page you are on."
+            },
             {
               "kind": "method",
               "name": "close",
@@ -103911,29 +104328,6 @@
               },
               "description": "The bottom edge of the bar this hangs from.\n\nThe trigger's own bottom is the obvious answer and is the wrong one: a\nheader is taller than the word inside it, so a band starting at the word\nstarts partway up the header, over its lower padding and its border.\nMeasured: trigger bottom 44, header bottom 57, thirteen pixels of header\nwith a band drawn across it.\n\n**The first ancestor as wide as the window, which is a fact and not a tag\nname.** A band spans the viewport, so what it should hang from is whatever\nelse does: that is what makes something a bar. Asking for `AppHeader` by\nname would make this element know about that one, which is the coupling\n`Menu` is careful not to have with `Drilldown`, and would leave a consumer\nwho wrote their own header with a band across it.\n\n`body` ends the walk. It is as wide as the window and is not a bar, and its\nbottom is the foot of the page: without the guard a megamenu on a plain page\nwould put its band down there. Nothing found means nothing to hang from, and\nthe trigger is the honest answer again."
             },
-            {
-              "kind": "field",
-              "name": "OPEN_DELAY",
-              "type": {
-                "text": "number"
-              },
-              "privacy": "private",
-              "static": true,
-              "readonly": true,
-              "default": "120",
-              "description": "How long a pointer has to mean it, in milliseconds.\n\nOpening is the shorter wait: too long and the panel feels stuck, too short\nand crossing the bar opens things. Closing is longer because the pointer\nhas to get from the trigger to the panel, and the straight line between\nthem is not the line anybody moves along."
-            },
-            {
-              "kind": "field",
-              "name": "CLOSE_DELAY",
-              "type": {
-                "text": "number"
-              },
-              "privacy": "private",
-              "static": true,
-              "readonly": true,
-              "default": "220"
-            },
             {
               "kind": "field",
               "name": "timer",
@@ -104599,6 +104993,15 @@
               "description": "The page width, in pixels, below which a card panel is shown as a band. At\nzero, it never is.\n\nA card is a panel hung off one word, and there is no room to hang anything\noff a word on a phone: the columns do not shrink past\n`--megamenu-column-size`, so four of them stay four of them and the panel\nruns off the side of the screen rather than reflowing. Below this it takes\nthe whole width and its columns stack, which is the only arrangement that\nfits.\n\n**In script rather than a media query, and only once.** Whether the panel is\na band is not a question of paint: a band is not placed against the trigger,\nso the controller has to be told not to measure, and that decision is here\nwhatever the stylesheet says. Writing the width in both places would be one\nnumber in two languages, drifting the first time either moved. This records\n`:state(narrow)` on the host and the stylesheet arranges itself off that.\n\n**A custom state and never `data-narrow`, which is what it was.** The width\nis read in `connectedCallback`, so on a phone this is true on the very first\nupdate: an attribute written there is markup a consumer's server never sent,\nwhich React reports as a mismatch and answers by rebuilding the subtree. The\nnarrow exception the server specs describe covers a mirror that can only\nbecome true long after hydration, and a viewport measured before the first\npaint is the opposite case. See `MixinControllerOpen` on `open`.",
               "fieldName": "bandBelow"
             },
+            {
+              "name": "close-delay",
+              "type": {
+                "text": "number"
+              },
+              "default": "220",
+              "description": "How long a pointer leaving the trigger and the panel waits before the panel\ncloses, in milliseconds. The pointer needs the time to cross from the\ntrigger to the panel.",
+              "fieldName": "closeDelay"
+            },
             {
               "name": "label",
               "type": {
@@ -104608,6 +105011,15 @@
               "description": "The section's name, used for the default trigger and the panel.",
               "fieldName": "label"
             },
+            {
+              "name": "open-delay",
+              "type": {
+                "text": "number"
+              },
+              "default": "120",
+              "description": "How long a pointer rests on the trigger before the panel opens, in\nmilliseconds, under `open-on=\"hover\"`. A pointer crossing the bar on its\nway somewhere else opens nothing.",
+              "fieldName": "openDelay"
+            },
             {
               "name": "open-on",
               "type": {
@@ -104617,6 +105029,15 @@
               "description": "Whether hovering over the trigger opens the panel (`hover`), or only a press\ndoes (`click`).\n\nA press always works. This says whether a mouse also opens it by resting on\nthe trigger, and it is the default because that is what a navigation bar\ndoes. `click` is for a trigger that does something else as well, or a panel\nheavy enough that opening it on the way past is rude.",
               "fieldName": "openOn"
             },
+            {
+              "name": "placement",
+              "type": {
+                "text": "'bottom' | 'bottom-end' | 'bottom-start' | 'left' | 'left-end' | 'left-start' | 'right' | 'right-end' | 'right-start' | 'top' | 'top-end' | 'top-start'"
+              },
+              "default": "'bottom-start'",
+              "description": "The side of the trigger a card panel opens on, when there is room. It\nmoves if that side does not fit. A band ignores it, since a band spans the\npage under its bar.",
+              "fieldName": "placement"
+            },
             {
               "name": "variant",
               "type": {
@@ -104652,6 +105073,10 @@
             }
           ],
           "cssStates": [
+            {
+              "description": "A link in the panel carries `aria-current=\"page\"`, so the trigger can show the section you are in.",
+              "name": "current"
+            },
             {
               "description": "The panel opened in place of one earlier in the bar, so it can enter from the end side.",
               "name": "from-end"
@@ -104781,7 +105206,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "One element covers three kinds of row, and what you give it decides which:\n- Content in the `submenu` slot makes the row open a submenu page.\n- `checked` makes the row a choice.\n- With neither, the row is a command.\n\nThe role follows the kind. A row with `checked` is `menuitemcheckbox` with\n`aria-checked`, and `exclusive` makes it `menuitemradio`, for a set where\nonly one can be on. A row that opens a page keeps `menuitem` and sets\n`aria-haspopup`.\n\nChoosing a choice row checks or unchecks it before `helix-select` is sent,\nso a listener reads the new `checked`. An `exclusive` row turns on and turns\noff the `exclusive` rows next to it. Cancel `helix-before-toggle` to keep a\nrow as it is and set `checked` yourself.\n\nThe menu sets whether the row's page is showing as a property, never as an\nattribute. An attribute written onto your element after it upgrades causes a\nhydration mismatch.\n\n`shortcut` shows a row's keyboard shortcut after its label, drawn by `Kbd`\nin the platform's glyphs, and gives the row `aria-keyshortcuts`. It binds\nnothing: the shortcut is the page's to bind. Other trailing words, such as a\ncount, go in the `end` slot.\n\nThe row is named by its label alone. Words in `description`, a line under the\nlabel, and in `end` describe it instead, through `aria-describedby`, as\nReact Aria's menu item does with its description: a reader hears \"Copy\",\nthen \"Copies the selection\".\n\nThe check mark and the caret are the fallbacks of the `check` and `chevron`\nslots, so a mark of your own replaces either by being slotted. Neither is\nread as part of the row's name.",
+          "description": "One element covers three kinds of row, and what you give it decides which:\n- Content in the `submenu` slot makes the row open a submenu page.\n- `checked` makes the row a choice.\n- With neither, the row is a command.\n\nThe role follows the kind. A row with `checked` is `menuitemcheckbox` with\n`aria-checked`, and `exclusive` makes it `menuitemradio`, for a set where\nonly one can be on. A row that opens a page keeps `menuitem` and sets\n`aria-haspopup`.\n\nChoosing a choice row checks or unchecks it before `helix-select` is sent,\nso a listener reads the new `checked`. An `exclusive` row turns on and turns\noff the `exclusive` rows next to it. Cancel `helix-before-toggle` to keep a\nrow as it is and set `checked` yourself.\n\nThe menu sets whether the row's page is showing as a property, never as an\nattribute. An attribute written onto your element after it upgrades causes a\nhydration mismatch.\n\n`shortcut` shows a row's keyboard shortcut after its label, drawn by `Kbd`\nin the platform's glyphs, and gives the row `aria-keyshortcuts`. It binds\nnothing: the shortcut is the page's to bind. Other trailing words, such as a\ncount, go in the `end` slot.\n\nThe row is named by its label alone. Words in `description`, a line under the\nlabel, and in `end` describe it instead, through `aria-describedby`, as\nReact Aria's menu item does with its description: a reader hears \"Copy\",\nthen \"Copies the selection\".\n\nA development build warns when a row has no words to be named by, such as a\nrow holding only an icon with no label.\n\nThe check mark and the caret are the fallbacks of the `check` and `chevron`\nslots, so a mark of your own replaces either by being slotted. Neither is\nread as part of the row's name.",
           "name": "HelixHeadlessMenuItem",
           "cssParts": [
             {
@@ -104815,6 +105240,10 @@
             {
               "description": "The leading column that holds the `start` slot. It is always rendered.",
               "name": "start"
+            },
+            {
+              "description": "The panel a submenu opens in beside the row, under the menu's `submenus=\"flyout\"`.",
+              "name": "surface"
             }
           ],
           "slots": [
@@ -105086,6 +105515,14 @@
                 "text": "focusItem() => void"
               }
             },
+            {
+              "kind": "field",
+              "name": "flyoutPanel",
+              "privacy": "protected",
+              "readonly": true,
+              "default": "new PopoverController(this, { anchor: () => this.partNamed('item'), boundary: () => this, onDismiss: () => {}, open: () => this.flyout && this.expanded && this.onPage && this.submenu, placement: () => (isRtl(this) ? 'left-start' : 'right-start'), surface: () => (this.flyout ? this.partNamed('surface') : null), })",
+              "description": "The panel a flyout submenu opens in, beside the row and in the top layer.\nThe menu around it says when, and answers a press outside and Escape, so\nits own dismissal does nothing."
+            },
             {
               "kind": "method",
               "name": "select",
@@ -105636,6 +106073,14 @@
               "description": "The row is checked.",
               "name": "checked"
             },
+            {
+              "description": "Under `submenus=\"flyout\"`, a row in this row's submenu can be ticked or opens a submenu, so the submenu keeps its trailing column.",
+              "name": "submenu-mark"
+            },
+            {
+              "description": "Under `submenus=\"flyout\"`, a row in this row's submenu has content before its label, so the submenu keeps its leading column.",
+              "name": "submenu-start"
+            },
             {
               "description": "Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.",
               "name": "settled",
@@ -105696,7 +106141,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "The trigger is slotted and stays your own element, as with the tooltip. The\nmenu renders its surface in the top layer with the popover API, so an\nancestor with `overflow: hidden` does not clip it and it needs no `z-index`.\n\nSlot a `helix-button` or `helix-icon-button` as the trigger, and the menu\ntells it that it opens a menu and whether the menu is open. A plain\n`<button>` can only be told by writing attributes onto your markup, which\nthe menu does not do, so give it `aria-haspopup=\"menu\"` and set its\n`aria-expanded` from the `toggle` event.\n\nSubmenus drill down. A submenu replaces the panel's content, and a back row\nreturns to the previous page. One panel avoids the diagonal pointer path that\nside-by-side panels need, stays inside a narrow window, and works on touch\nscreens, which have no hover.\n\nThe root holds which page is open, because only one page shows at a time. It\nsets this on items as a property, never as an attribute. An attribute written\nonto your element after it upgrades causes a hydration mismatch.\n\nGroup rows under a heading with `Menu.Section`, which is a `group` named by\nits heading. Between runs of rows, a `<helix-divider>` is a separator a\nscreen reader announces.\n\nKeys: Enter, Space or Down Arrow on the trigger opens the menu on its first\nrow, and Up Arrow on its last. In the menu, Up and Down Arrow move between\nrows, Home and End go to the first and the last, a typed letter moves to\nthe next row whose name starts with it, Enter and Space choose, Right Arrow\nopens a row's submenu and Left Arrow goes back, the two swapping on a\nright-to-left page, and Escape closes the menu and returns focus to the\ntrigger. Tab closes it and moves on.\n\nWhile it is open, the surface carries the trigger's width as\n`--floating-anchor-inline-size` and the room left below it as\n`--floating-available-block-size`, as Radix's dropdown menu publishes its\ntrigger's width, for a menu as wide as its trigger:\n`helix-menu::part(surface) { min-inline-size: var(--floating-anchor-inline-size) }`.\n\nWith `context`, the trigger is an area and the menu is its context menu: a\nright-click, a long press, Shift+F10 or the menu key over the area opens it\nat the pointer, or at the area's corner from the keyboard, as Radix's context\nmenu does. A press on the area does not open it, and closing it returns focus\nto where it was.",
+          "description": "The trigger is slotted and stays your own element, as with the tooltip. The\nmenu renders its surface in the top layer with the popover API, so an\nancestor with `overflow: hidden` does not clip it and it needs no `z-index`.\n\nSlot a `helix-button` or `helix-icon-button` as the trigger, and the menu\ntells it that it opens a menu and whether the menu is open, inside its own\nshadow root. On a plain element, such as a `<button>`, the menu writes\n`aria-haspopup=\"menu\"` and `aria-expanded`, from a frame after its own first\nrender, so a server's markup is never changed while a framework hydrates it.\nIt never writes `aria-expanded` where you wrote it yourself.\n\nSubmenus drill down by default. A submenu replaces the panel's content, and a\nback row returns to the previous page. One panel stays inside a narrow\nwindow, and works on touch screens, which have no hover.\n\n**`submenus=\"flyout\"` opens each submenu in a panel of its own beside its\nrow**, as React Aria's `SubmenuTrigger` and Radix's `Sub` do. Resting the\npointer on the row opens it, and a pointer crossing toward the open panel\nover the rows between keeps it open, as Radix's grace area does. Right Arrow\nopens a row's submenu on its first row, and Left Arrow or Escape closes it\nand returns focus to the row, the two arrows swapping on a right-to-left\npage. The row says `aria-expanded`, and the panel is a `menu` named by the\nrow.\n\nThe root holds which page is open, because only one page shows at a time. It\nsets this on items as a property, never as an attribute. An attribute written\nonto your element after it upgrades causes a hydration mismatch.\n\nGroup rows under a heading with `Menu.Section`, which is a `group` named by\nits heading. Between runs of rows, a `<helix-divider>` is a separator a\nscreen reader announces.\n\nKeys: Enter, Space or Down Arrow on the trigger opens the menu on its first\nrow, and Up Arrow on its last. In the menu, Up and Down Arrow move between\nrows, Home and End go to the first and the last, a typed letter moves to\nthe next row whose name starts with it, Enter and Space choose, Right Arrow\nopens a row's submenu and Left Arrow goes back, the two swapping on a\nright-to-left page. Left Arrow on the top page does nothing. Escape closes\nthe menu and returns focus to the trigger. Tab closes it and moves on.\n\nWhile it is open, the surface carries the trigger's width as\n`--floating-anchor-inline-size` and the room left below it as\n`--floating-available-block-size`, as Radix's dropdown menu publishes its\ntrigger's width, for a menu as wide as its trigger:\n`helix-menu::part(surface) { min-inline-size: var(--floating-anchor-inline-size) }`.\n\nWith `context`, the trigger is an area and the menu is its context menu: a\nright-click, a long press, Shift+F10 or the menu key over the area opens it\nat the pointer, or at the area's corner from the keyboard, as Radix's context\nmenu does. A press on the area does not open it, and closing it returns focus\nto where it was. A touch or a pen held still on the area opens it too, on\nevery browser, since iOS sends no `contextmenu` for one.\n\n**A trigger with its own action.** With `open-on=\"long-press\"`, a press on\nthe trigger is the trigger's own, and a press held for half a second opens\nthe menu, as React Aria's `trigger=\"longPress\"` does. Alt+Down or Alt+Up\nopens it from the keyboard, and the trigger is described by\n`long-press-label`, which says so.",
           "name": "HelixHeadlessMenu",
           "cssProperties": [
             {
@@ -105801,6 +106246,116 @@
               "description": "Accessible name for the surface.\n\nEmpty by default, which names the surface by its trigger, so a menu opened\nfrom \"Actions\" is announced as \"Actions\". An `aria-label` or\n`aria-labelledby` on the host names it too, and wins over both.",
               "attribute": "label"
             },
+            {
+              "kind": "field",
+              "name": "flies",
+              "type": {
+                "text": "boolean"
+              },
+              "privacy": "private",
+              "description": "Whether submenus open beside their rows.",
+              "readonly": true
+            },
+            {
+              "kind": "field",
+              "name": "topRows",
+              "type": {
+                "text": "HelixHeadlessMenuItem[]"
+              },
+              "privacy": "private",
+              "description": "The rows of the top page, read through each section.",
+              "readonly": true
+            },
+            {
+              "kind": "method",
+              "name": "rowsOf",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "HelixHeadlessMenuItem[]"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "holder",
+                  "type": {
+                    "text": "HelixHeadlessMenuItem | null"
+                  }
+                }
+              ],
+              "description": "The rows of a submenu, or of the top page for null."
+            },
+            {
+              "kind": "method",
+              "name": "holderOf",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "HelixHeadlessMenuItem | null"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "row",
+                  "type": {
+                    "text": "HelixHeadlessMenuItem"
+                  }
+                }
+              ],
+              "description": "The row whose submenu holds a row, or null for a row of the top page."
+            },
+            {
+              "kind": "field",
+              "name": "openPages",
+              "type": {
+                "text": "(HelixHeadlessMenuItem | null)[]"
+              },
+              "privacy": "private",
+              "description": "The submenus open, from the top page down to the deepest.",
+              "readonly": true
+            },
+            {
+              "kind": "field",
+              "name": "keyPage",
+              "type": {
+                "text": "HelixHeadlessMenuItem | null"
+              },
+              "privacy": "private",
+              "description": "The submenu the keys move in under `flyout`: the one holding the row with\nfocus, or the deepest open one.",
+              "readonly": true
+            },
+            {
+              "kind": "method",
+              "name": "openPage",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "holder",
+                  "type": {
+                    "text": "HelixHeadlessMenuItem | null"
+                  }
+                }
+              ],
+              "description": "Opens a submenu and closes the ones below it, or closes them all for null."
+            },
+            {
+              "kind": "field",
+              "name": "longPressLabel",
+              "type": {
+                "text": "string"
+              },
+              "default": "'Long press or press Alt+Down to show the menu'",
+              "description": "The description a trigger gives under `open-on=\"long-press\"`, saying how\nto open the menu. Translate it with the rest of your interface.",
+              "attribute": "long-press-label",
+              "helix": {
+                "words": true
+              }
+            },
             {
               "kind": "field",
               "name": "offset",
@@ -105811,6 +106366,43 @@
               "description": "Space between the trigger and the surface, in pixels.",
               "attribute": "offset"
             },
+            {
+              "kind": "field",
+              "name": "pressHeld",
+              "type": {
+                "text": "boolean"
+              },
+              "privacy": "private",
+              "description": "Whether the trigger opens the menu only on a held press.",
+              "readonly": true
+            },
+            {
+              "kind": "field",
+              "name": "longPress",
+              "privacy": "private",
+              "readonly": true,
+              "default": "new LongPress(this, { onLongPress: () => { if (this.context) { const at = this.heldAt if (at) { this.openContextAt(at) } return } if (!this.open) { this.show() } }, })",
+              "description": "Watches the trigger for a held press: under `open-on=\"long-press\"`, and\nfor a touch or a pen on a context menu's area."
+            },
+            {
+              "kind": "field",
+              "name": "heldAt",
+              "type": {
+                "text": "{ x: number; y: number } | undefined"
+              },
+              "privacy": "private",
+              "description": "Where a held press on a context menu's area is, to open the menu there."
+            },
+            {
+              "kind": "field",
+              "name": "openOn",
+              "type": {
+                "text": "'click' | 'long-press'"
+              },
+              "default": "'click'",
+              "description": "What opens the menu from its trigger. `long-press` leaves a press to the\ntrigger's own action and opens the menu on a press held for half a second,\nor on Alt+Down or Alt+Up.",
+              "attribute": "open-on"
+            },
             {
               "kind": "field",
               "name": "placement",
@@ -105821,6 +106413,16 @@
               "description": "The side the menu opens on, when there is room.\n\nIt moves if that side does not fit.",
               "attribute": "placement"
             },
+            {
+              "kind": "field",
+              "name": "submenus",
+              "type": {
+                "text": "'drill' | 'flyout'"
+              },
+              "default": "'drill'",
+              "description": "How a submenu opens. `drill` shows it in place of the page showing, with\na way back. `flyout` opens it in a panel of its own beside its row.",
+              "attribute": "submenus"
+            },
             {
               "kind": "field",
               "name": "drilldown",
@@ -105868,7 +106470,7 @@
               "name": "panel",
               "privacy": "private",
               "readonly": true,
-              "default": "new PopoverController(this, { anchor: () => this.context && this.point ? this.renderRoot?.querySelector<HTMLElement>('#point') : this.trigger, // The host is `display: contents`, so it has no box a press can land in. // What counts as inside is the surface, plus the trigger, whose own click // handler decides what a press there means. boundary: () => this, offset: () => this.offset, onDismiss: () => this.hide(), open: () => this.open, placement: () => this.placement, surface: () => this.partNamed('surface'), })"
+              "default": "new PopoverController(this, { anchor: () => this.context && this.point ? this.renderRoot?.querySelector<HTMLElement>('#point') : this.trigger, // The host is `display: contents`, so it has no box a press can land in. // What counts as inside is the surface, plus the trigger, whose own click // handler decides what a press there means. boundary: () => this, offset: () => this.offset, onDismiss: () => this.hide(), /* The side the panel landed on, for a sheet outside that draws by side, as Popover says it. */ onPlace: (placement) => { const side = sideOf(placement) this.toggleState('placed-bottom', side === 'bottom') this.toggleState('placed-left', side === 'left') this.toggleState('placed-right', side === 'right') this.toggleState('placed-top', side === 'top') }, open: () => this.open, placement: () => this.placement, surface: () => this.partNamed('surface'), })"
             },
             {
               "kind": "method",
@@ -105881,6 +106483,25 @@
               },
               "description": "Tells a slotted trigger the disclosure state, by property.\n\nA control that opens a menu has to say so. By property rather than by\nattribute, which is the class note's rule about items applied one level up:\nan attribute written onto a consumer's element after it upgrades is a\nhydration mismatch waiting to happen."
             },
+            {
+              "kind": "field",
+              "name": "settledOnce",
+              "type": {
+                "text": "boolean"
+              },
+              "privacy": "private",
+              "default": "false",
+              "description": "Whether a frame has passed since the first render, after which a plain trigger may be told."
+            },
+            {
+              "kind": "field",
+              "name": "told",
+              "type": {
+                "text": "Element | undefined"
+              },
+              "privacy": "private",
+              "description": "The plain trigger this menu writes `aria-expanded` on."
+            },
             {
               "kind": "field",
               "name": "trigger",
@@ -105953,6 +106574,25 @@
               "readonly": true,
               "description": "Opens a context menu where the reader asked for it: at the pointer, or at\nthe area's corner where the keyboard asked and the event has no position."
             },
+            {
+              "kind": "method",
+              "name": "openContextAt",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "point",
+                  "type": {
+                    "text": "{ x: number; y: number }"
+                  }
+                }
+              ],
+              "description": "Opens a context menu at a point in the viewport, or moves an open one there."
+            },
             {
               "kind": "method",
               "name": "enter",
@@ -106027,6 +106667,160 @@
               "privacy": "private",
               "readonly": true
             },
+            {
+              "kind": "method",
+              "name": "fromTrigger",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "boolean"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "event",
+                  "type": {
+                    "text": "Event"
+                  }
+                }
+              ],
+              "description": "Whether an event came from the slotted trigger, or the area of a context menu."
+            },
+            {
+              "kind": "field",
+              "name": "handlePointerDown",
+              "privacy": "private",
+              "readonly": true,
+              "description": "A press on the trigger starting: the start of a held one under\n`open-on=\"long-press\"`, or a touch or a pen held on a context menu's area."
+            },
+            {
+              "kind": "field",
+              "name": "handlePointerMove",
+              "privacy": "private",
+              "readonly": true
+            },
+            {
+              "kind": "field",
+              "name": "handlePointerUp",
+              "privacy": "private",
+              "readonly": true
+            },
+            {
+              "kind": "field",
+              "name": "handlePointerCancel",
+              "privacy": "private",
+              "readonly": true
+            },
+            {
+              "kind": "field",
+              "name": "handleHeldClick",
+              "privacy": "private",
+              "readonly": true,
+              "description": "Takes the click a held press ends in, ahead of the trigger's own\nlisteners, so a press that opened the menu does not also do the trigger's\naction. In capture, on the host, which is above a slotted trigger."
+            },
+            {
+              "kind": "field",
+              "name": "described",
+              "type": {
+                "text": "Element | undefined"
+              },
+              "privacy": "private",
+              "description": "The control the menu has described, so the description can be taken back."
+            },
+            {
+              "kind": "method",
+              "name": "describeTrigger",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "light",
+                  "default": "false"
+                }
+              ],
+              "description": "Describes the trigger by `long-press-label` under `open-on=\"long-press\"`,\nor takes it back, by the host, which carries the words as its label, as\n`SpeedDial` does. On the consumer's own element only once a reader has\nreached it, which is after hydration."
+            },
+            {
+              "kind": "field",
+              "name": "handleTriggerFocusIn",
+              "privacy": "private",
+              "readonly": true,
+              "description": "A reader reaching the trigger, which is late enough to describe a plain one."
+            },
+            {
+              "kind": "field",
+              "name": "hovered",
+              "type": {
+                "text": "HelixHeadlessMenuItem | undefined"
+              },
+              "privacy": "private",
+              "description": "The row the pointer last rested on, under `flyout`."
+            },
+            {
+              "kind": "field",
+              "name": "hoverTimer",
+              "type": {
+                "text": "ReturnType<typeof setTimeout> | undefined"
+              },
+              "privacy": "private",
+              "description": "The wait before a rested-on row opens or closes a submenu."
+            },
+            {
+              "kind": "field",
+              "name": "grace",
+              "type": {
+                "text": "{ points: [number, number][]; until: number } | undefined"
+              },
+              "privacy": "private",
+              "description": "The triangle from where the pointer left a row with an open submenu to the\nnear edge of that submenu, and until when it holds."
+            },
+            {
+              "kind": "method",
+              "name": "stopHover",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              }
+            },
+            {
+              "kind": "field",
+              "name": "handleHover",
+              "privacy": "private",
+              "readonly": true,
+              "description": "A mouse resting on a row, under `flyout`: focus follows it, and after a\nmoment the row's submenu opens, or the submenus below the row's own page\nclose. Not while the pointer is crossing toward an open submenu."
+            },
+            {
+              "kind": "field",
+              "name": "handleRowOut",
+              "privacy": "private",
+              "readonly": true,
+              "description": "The pointer leaving a row whose submenu is open, which starts the grace area."
+            },
+            {
+              "kind": "method",
+              "name": "inGrace",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "boolean"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "event",
+                  "type": {
+                    "text": "PointerEvent"
+                  }
+                }
+              ],
+              "description": "Whether the pointer is inside the grace area, while it holds."
+            },
             {
               "kind": "method",
               "name": "nameSurface",
@@ -106808,6 +107602,15 @@
               "description": "Accessible name for the surface.\n\nEmpty by default, which names the surface by its trigger, so a menu opened\nfrom \"Actions\" is announced as \"Actions\". An `aria-label` or\n`aria-labelledby` on the host names it too, and wins over both.",
               "fieldName": "label"
             },
+            {
+              "name": "long-press-label",
+              "type": {
+                "text": "string"
+              },
+              "default": "'Long press or press Alt+Down to show the menu'",
+              "description": "The description a trigger gives under `open-on=\"long-press\"`, saying how\nto open the menu. Translate it with the rest of your interface.",
+              "fieldName": "longPressLabel"
+            },
             {
               "name": "offset",
               "type": {
@@ -106817,6 +107620,15 @@
               "description": "Space between the trigger and the surface, in pixels.",
               "fieldName": "offset"
             },
+            {
+              "name": "open-on",
+              "type": {
+                "text": "'click' | 'long-press'"
+              },
+              "default": "'click'",
+              "description": "What opens the menu from its trigger. `long-press` leaves a press to the\ntrigger's own action and opens the menu on a press held for half a second,\nor on Alt+Down or Alt+Up.",
+              "fieldName": "openOn"
+            },
             {
               "name": "placement",
               "type": {
@@ -106826,6 +107638,15 @@
               "description": "The side the menu opens on, when there is room.\n\nIt moves if that side does not fit.",
               "fieldName": "placement"
             },
+            {
+              "name": "submenus",
+              "type": {
+                "text": "'drill' | 'flyout'"
+              },
+              "default": "'drill'",
+              "description": "How a submenu opens. `drill` shows it in place of the page showing, with\na way back. `flyout` opens it in a panel of its own beside its row.",
+              "fieldName": "submenus"
+            },
             {
               "name": "empty-text",
               "type": {
@@ -106904,6 +107725,22 @@
               "description": "While the menu is open.",
               "name": "open"
             },
+            {
+              "description": "While the open panel sits below its trigger.",
+              "name": "placed-bottom"
+            },
+            {
+              "description": "While the open panel sits to the left of its trigger.",
+              "name": "placed-left"
+            },
+            {
+              "description": "While the open panel sits to the right of its trigger.",
+              "name": "placed-right"
+            },
+            {
+              "description": "While the open panel sits above its trigger.",
+              "name": "placed-top"
+            },
             {
               "description": "A row on the current page has content in its leading column, so every row keeps that column.",
               "name": "start"
@@ -110204,7 +111041,7 @@
                   "text": "HTMLElement | undefined"
                 }
               },
-              "description": "The tab stop after this element on the page, or the one before it at the\nend, for a lone element whose removal would drop focus to the body.\n\n**A lone Callout or Announcement had nowhere to hand focus**, so a\nkeyboard reader who dismissed one started again from the top of the\npage. React Aria's Toast hands focus on the same way. Read before the\nevent, in the order Tab reaches the stops, while this element's own are\nstill among them.",
+              "description": "The tab stop after this element on the page, or the one before it at the\nend, for an element whose removal would drop focus to the body because\nno neighbor of its kind has a control to take it.\n\n**A lone Callout or Announcement had nowhere to hand focus**, so a\nkeyboard reader who dismissed one started again from the top of the\npage. React Aria's Toast hands focus on the same way. Read before the\nevent, in the order Tab reaches the stops, while this element's own are\nstill among them.",
               "inheritedFrom": {
                 "name": "MixinDismissible",
                 "module": "src/mixins/mixin-dismissible/mixin-dismissible.ts"
@@ -110793,7 +111630,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**`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.** 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.",
           "name": "HelixHeadlessNotifications",
           "cssParts": [
             {
@@ -110884,6 +111721,19 @@
                 "module": "src/mixins/mixin-collection/mixin-collection.ts"
               }
             },
+            {
+              "kind": "field",
+              "name": "arrivedLabel",
+              "type": {
+                "text": "string"
+              },
+              "default": "'{count, plural, one {# new notification} other {# new notifications}}'",
+              "description": "What the feed says when unread notifications arrive, with `{count}` the\nnumber of them. Empty it to say nothing.",
+              "attribute": "arrived-label",
+              "helix": {
+                "words": true
+              }
+            },
             {
               "kind": "field",
               "name": "fallbackLabel",
@@ -111154,6 +112004,34 @@
               },
               "description": "Tells each row whether it is the stop, and where it sits in the feed.\n\nThrough each row's own properties, written once it has hydrated, so a\nserver's markup stays the server's: every row is a stop until this runs."
             },
+            {
+              "kind": "field",
+              "name": "seen",
+              "type": {
+                "text": "WeakSet<Element> | undefined"
+              },
+              "privacy": "private",
+              "description": "The rows the feed has met, so a row that arrives later is told apart."
+            },
+            {
+              "kind": "field",
+              "name": "hush",
+              "privacy": "private",
+              "readonly": true,
+              "default": "new DelayController(this, { renders: false })",
+              "description": "Empties the arrival a moment after it is said, so the next one is news."
+            },
+            {
+              "kind": "method",
+              "name": "noteArrivals",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "description": "Counts the unread rows that arrived above the rows there were, and says\nhow many. Rows that fill an empty feed are a page, which says nothing. The rows there are at the first update are\nthe feed's to begin with, and say nothing."
+            },
             {
               "kind": "method",
               "name": "renderStatus",
@@ -111768,6 +112646,15 @@
             }
           ],
           "attributes": [
+            {
+              "name": "arrived-label",
+              "type": {
+                "text": "string"
+              },
+              "default": "'{count, plural, one {# new notification} other {# new notifications}}'",
+              "description": "What the feed says when unread notifications arrive, with `{count}` the\nnumber of them. Empty it to say nothing.",
+              "fieldName": "arrivedLabel"
+            },
             {
               "name": "fallback-label",
               "type": {
@@ -112075,7 +112962,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "A separate family from `Input`'s `type=\"number\"`. It renders two buttons,\nbinds four keys `Input` does not, and handles clamping and stepping.\n\nThe field is `type=\"text\"` with `inputmode=\"decimal\"`. Tested in a real\nbrowser, `type=\"number\"` fails in three ways:\n- Typing `12e` gives a `.value` of `\"\"`, so the element cannot see what you\n  typed. A `type=\"text\"` field keeps `\"12e\"`.\n- The mouse wheel over a focused field changes the value, for example from 5\n  to 4, when you only meant to scroll the page.\n- `selectionStart` is `null`, so the caret cannot be managed.\n\n`inputmode=\"decimal\"` keeps the numeric keypad on phones.\n\n`format-options` shows the number with `Intl.NumberFormat` in `locale`, as a\ncurrency, a percent or a unit, while the field is not being edited. Focus\nshows the number itself, and a typed `$1,200` or `25%` is read back with the\nsame options. The value stays the plain number: `1200`, or `0.25` for 25%.\nThe locale's group separators are read in every field, so `1,234` is a\nnumber in `en-US`.\n\nThe field and its two buttons sit in a `role=\"group\"`, and the field carries\n`role-label`, \"number field\" in English, as its `aria-roledescription`, as\nReact Aria's NumberField does. On iOS and iPadOS the field is a plain text\nfield, with no `role=\"spinbutton\"`, which VoiceOver reads as a slider you\ncannot type in, and no role description, so VoiceOver says the field is\nrequired. React Aria's NumberField does the same.\n\nValidity follows the platform's rules: `min`, `max`, and `step` are checked\nand reported through the host's own `setValidity`, under the platform's flag\nnames.\n\nStepping is separate from typing, so a number is not corrected while you type\nit. While you type, the form holds the number the text reads as, so a field\nshowing `$2,500.50` gives the form 2500.5, and text that is not a number\ngives it nothing, as a native number field does.\n\nHolding a stepper button down steps once, then again after 400 milliseconds,\nthen every 60 milliseconds until you let go, as React Aria's NumberField does.\n\n**Keyboard.** The field is one tab stop, and the stepper buttons are not in\nthe tab order.\n\n| Key | What it does |\n|---|---|\n| Up, Down | Steps the value up or down by `step`. |\n| Page Up, Page Down | Steps by `large-step` steps, ten by default. |\n| Home, End | Goes to `min` or `max`, where there is one. Without one, moves the caret. |\n| Enter | Commits the typed number and submits the form, as a native field does. |\n\nThe field has `role=\"spinbutton\"` with `aria-valuenow`, `aria-valuemin`,\n`aria-valuemax`, and the formatted text in `aria-valuetext`.",
+          "description": "A separate family from `Input`'s `type=\"number\"`. It renders two buttons,\nbinds four keys `Input` does not, and handles clamping and stepping.\n\nThe field is `type=\"text\"` with `inputmode=\"decimal\"`. Tested in a real\nbrowser, `type=\"number\"` fails in three ways:\n- Typing `12e` gives a `.value` of `\"\"`, so the element cannot see what you\n  typed. A `type=\"text\"` field keeps `\"12e\"`.\n- The mouse wheel over a focused field changes the value, for example from 5\n  to 4, when you only meant to scroll the page.\n- `selectionStart` is `null`, so the caret cannot be managed.\n\n`inputmode=\"decimal\"` keeps the numeric keypad on phones.\n\n`format-options` shows the number with `Intl.NumberFormat` in `locale`, as a\ncurrency, a percent or a unit, while the field is not being edited. Focus\nshows the number itself, and a typed `$1,200` or `25%` is read back with the\nsame options. The value stays the plain number: `1200`, or `0.25` for 25%.\nThe locale's group separators are read in every field, so `1,234` is a\nnumber in `en-US`.\n\nThe field and its two buttons sit in a `role=\"group\"` named by the label,\nand the field carries `role-label`, \"number field\" in English, as its\n`aria-roledescription`, as React Aria's NumberField does. On iOS and iPadOS the field is a plain text\nfield, with no `role=\"spinbutton\"`, which VoiceOver reads as a slider you\ncannot type in, and no role description, so VoiceOver says the field is\nrequired. React Aria's NumberField does the same.\n\nValidity follows the platform's rules: `min`, `max`, and `step` are checked\nand reported through the host's own `setValidity`, under the platform's flag\nnames.\n\nStepping is separate from typing, so a number is not corrected while you type\nit. While you type, the form holds the number the text reads as, so a field\nshowing `$2,500.50` gives the form 2500.5, and text that is not a number\ngives it nothing, as a native number field does.\n\nHolding a stepper button down steps once, then again after 400 milliseconds,\nthen every 60 milliseconds until you let go, as React Aria's NumberField does.\n\n**Keyboard.** The field is one tab stop, and the stepper buttons are not in\nthe tab order.\n\n| Key | What it does |\n|---|---|\n| Up, Down | Steps the value up or down by `step`. |\n| Page Up, Page Down | Steps by `large-step` steps, ten by default. |\n| Home, End | Goes to `min` or `max`, where there is one. Without one, moves the caret. |\n| Enter | Commits the typed number and submits the form, as a native field does. |\n\nThe field has `role=\"spinbutton\"` with `aria-valuenow`, `aria-valuemin`,\n`aria-valuemax`, and the formatted text in `aria-valuetext`.",
           "name": "HelixHeadlessNumberInput",
           "cssParts": [
             {
@@ -112872,7 +113759,7 @@
               "type": {
                 "text": "number"
               },
-              "description": "The value as a number, or `NaN` while the control is empty.\n\n`NaN` and not zero, which is the trap the platform already avoids: `Number('')`\nis zero, so an empty control would report a number it does not hold and a\nform would submit it."
+              "description": "The value as a number, or `NaN` while the control is empty or does not\nhold a number.\n\nRead in the locale and the format, as the form reads it, so `1,5` typed\nin a locale with a decimal comma is 1.5 here while the form holds 1.5.\n`NaN` and not zero, which is the trap the platform already avoids: `Number('')`\nis zero, so an empty control would report a number it does not hold and a\nform would submit it."
             },
             {
               "kind": "field",
@@ -135330,7 +136217,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "A trigger that opens a `Listbox`. The list is the same element you can use on\nits own, with the same keyboard behavior, filtering, and multi-select rules.\nSelect adds a trigger that shows what is chosen, a floating surface, and a\nplace for focus to return to when the list closes.\n\nYour options stay in your light DOM and are slotted through into the listbox,\nso the listbox looks through slots to find them. For a list too long to draw\nwhole, set `items` instead: the list draws only the options in sight, as\nListbox's `items` does, and the trigger, its keys and the form read the\nwhole set.\n\n`Select` owns the value, passes it down to the listbox, and takes changes\nback, so the value lives in one place.\n\nSet `valueContent` to draw the trigger's content from the chosen options,\nand several chosen options are written as a list in the reader's language.\n\n**Keyboard.** On the closed trigger:\n\n| Key | What it does |\n|---|---|\n| Down, Enter, Space | Opens the list on the chosen option, or the first. |\n| Up | Opens the list on the chosen option, or the last. |\n| Home, End | Opens the list on the first or the last option. |\n| Left, Right | Chooses the option before or after the chosen one without opening, as React Aria's Select does, in either direction of text. |\n| A letter or a word | Chooses the option whose words start with what you typed, as a native `<select>` does. With `multiple`, opens the list on it. |\n\nIn the open list, which is a `Listbox`:\n\n| Key | What it does |\n|---|---|\n| Down, Up, Home, End, Page Down, Page Up | Moves the highlight. |\n| A letter or a word | Moves the highlight to the next option whose words start with what you typed. |\n| Enter, Space | Chooses the highlighted option and closes the list. With `multiple`, toggles it and leaves the list open. |\n| Escape | Closes the list and puts focus back on the trigger. |\n| Tab | Closes the list and moves on. |\n\nA choice made on the closed trigger is said aloud on Apple devices, where\nVoiceOver does not read the trigger's new name.\n\n**ARIA.** The trigger is a `button` with `aria-haspopup=\"listbox\"` and\n`aria-expanded`, named by the label and then the chosen words, as a native\n`<select>` is. The list is the listbox `Listbox` describes, named by the\nlabel, or by `list-label` where there is none.\n\nSet `autocomplete` to let a browser's autofill choose, as a native `<select>`\nwith the same attribute would.",
+          "description": "A trigger that opens a `Listbox`. The list is the same element you can use on\nits own, with the same keyboard behavior, filtering, and multi-select rules.\nSelect adds a trigger that shows what is chosen, a floating surface, and a\nplace for focus to return to when the list closes.\n\nYour options stay in your light DOM and are slotted through into the listbox,\nso the listbox looks through slots to find them. For a list too long to draw\nwhole, set `items` instead: the list draws only the options in sight, as\nListbox's `items` does, and the trigger, its keys and the form read the\nwhole set.\n\n`Select` owns the value, passes it down to the listbox, and takes changes\nback, so the value lives in one place. With `multiple`, the value is the\nchosen values joined with commas, and the form receives one entry for each.\nAn option's value may hold a comma, and it is read as one value.\n\nSet `valueContent` to draw the trigger's content from the chosen options,\nand several chosen options are written as a list in the reader's language.\n\n**Keyboard.** On the closed trigger:\n\n| Key | What it does |\n|---|---|\n| Down, Enter, Space | Opens the list on the chosen option, or the first. |\n| Up | Opens the list on the chosen option, or the last. |\n| Home, End | Opens the list on the first or the last option. |\n| Left, Right | Chooses the option before or after the chosen one without opening, as React Aria's Select does, in either direction of text. |\n| A letter or a word | Chooses the option whose words start with what you typed, as a native `<select>` does. With `multiple`, opens the list on it. |\n\nIn the open list, which is a `Listbox`:\n\n| Key | What it does |\n|---|---|\n| Down, Up, Home, End, Page Down, Page Up | Moves the highlight. |\n| A letter or a word | Moves the highlight to the next option whose words start with what you typed. |\n| Enter, Space | Chooses the highlighted option and closes the list. With `multiple`, toggles it and leaves the list open. |\n| Escape | Closes the list and puts focus back on the trigger. |\n| Tab | Closes the list and moves on. |\n\nA choice made on the closed trigger is said aloud on Apple devices, where\nVoiceOver does not read the trigger's new name.\n\n**ARIA.** The trigger is a `button` with `aria-haspopup=\"listbox\"` and\n`aria-expanded`, named by the label and then the chosen words, as a native\n`<select>` is. The list is the listbox `Listbox` describes, named by the\nlabel, or by `list-label` where there is none.\n\nSet `autocomplete` to let a browser's autofill choose, as a native `<select>`\nwith the same attribute would.",
           "name": "HelixHeadlessSelect",
           "cssProperties": [
             {
@@ -135686,6 +136573,16 @@
               "description": "The chosen options, in the order they appear. None on a server or while hydrating, and none for `items`.",
               "readonly": true
             },
+            {
+              "kind": "field",
+              "name": "chosen",
+              "type": {
+                "text": "string[]"
+              },
+              "privacy": "private",
+              "description": "The chosen values, read against the options' values, so an option whose\nvalue holds a comma is one value. See `chosenValues`.",
+              "readonly": true
+            },
             {
               "kind": "field",
               "name": "data",
@@ -137770,7 +138667,7 @@
                 "text": "string"
               },
               "default": "''",
-              "description": "What is loading, read out as the placeholder's name, such as \"Loading\nprofile\".\n\nAbsent hides the placeholder from screen readers.",
+              "description": "What is loading, read out as the placeholder's name, such as \"Loading\nprofile\".\n\nAbsent hides the placeholder from screen readers. Around content, the name\nis read while `loading` is set, and the loaded content is read as it is.",
               "attribute": "label"
             },
             {
@@ -138152,7 +139049,7 @@
                 "text": "string"
               },
               "default": "''",
-              "description": "What is loading, read out as the placeholder's name, such as \"Loading\nprofile\".\n\nAbsent hides the placeholder from screen readers.",
+              "description": "What is loading, read out as the placeholder's name, such as \"Loading\nprofile\".\n\nAbsent hides the placeholder from screen readers. Around content, the name\nis read while `loading` is set, and the loaded content is read as it is.",
               "fieldName": "label"
             },
             {
@@ -156546,7 +157443,7 @@
                   "text": "HTMLElement | undefined"
                 }
               },
-              "description": "The tab stop after this element on the page, or the one before it at the\nend, for a lone element whose removal would drop focus to the body.\n\n**A lone Callout or Announcement had nowhere to hand focus**, so a\nkeyboard reader who dismissed one started again from the top of the\npage. React Aria's Toast hands focus on the same way. Read before the\nevent, in the order Tab reaches the stops, while this element's own are\nstill among them.",
+              "description": "The tab stop after this element on the page, or the one before it at the\nend, for an element whose removal would drop focus to the body because\nno neighbor of its kind has a control to take it.\n\n**A lone Callout or Announcement had nowhere to hand focus**, so a\nkeyboard reader who dismissed one started again from the top of the\npage. React Aria's Toast hands focus on the same way. Read before the\nevent, in the order Tab reaches the stops, while this element's own are\nstill among them.",
               "inheritedFrom": {
                 "name": "MixinDismissible",
                 "module": "src/mixins/mixin-dismissible/mixin-dismissible.ts"
@@ -158367,7 +159264,7 @@
                   "text": "HTMLElement | undefined"
                 }
               },
-              "description": "The tab stop after this element on the page, or the one before it at the\nend, for a lone element whose removal would drop focus to the body.\n\n**A lone Callout or Announcement had nowhere to hand focus**, so a\nkeyboard reader who dismissed one started again from the top of the\npage. React Aria's Toast hands focus on the same way. Read before the\nevent, in the order Tab reaches the stops, while this element's own are\nstill among them.",
+              "description": "The tab stop after this element on the page, or the one before it at the\nend, for an element whose removal would drop focus to the body because\nno neighbor of its kind has a control to take it.\n\n**A lone Callout or Announcement had nowhere to hand focus**, so a\nkeyboard reader who dismissed one started again from the top of the\npage. React Aria's Toast hands focus on the same way. Read before the\nevent, in the order Tab reaches the stops, while this element's own are\nstill among them.",
               "inheritedFrom": {
                 "name": "MixinDismissible",
                 "module": "src/mixins/mixin-dismissible/mixin-dismissible.ts"
@@ -168761,7 +169658,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "Each message is an element because it has a timeout, a tone, a dismiss\ncontrol, and a lifetime that pauses.\n\n**Each item runs its own timer.** A timer held by the region would restart\nwith each new message, and the last of three messages would stay for nine\nseconds. It pauses while the pointer or focus is on the message, and while\nthe page is hidden, so a message is not spent in a background tab.\n\n**Each message is an `alertdialog` named by its words**, which is how a reader\nwho moves into the stack hears which message they are on. Give it a\n`heading` and a `description`, and the heading names it and the description\ndescribes it, for a message with a title and a line of detail. The region\nsays each message once as it arrives, a `danger` one assertively, so a\nmessage is never a live region of its own.\n\nA touch or a pen swipes a message toward the end of the line, and past\nhalfway, or quickly, dismisses it through the same `helix-dismiss` as its\ncontrol. While it moves, the distance is on the `item` part as\n`--toast-swipe-x`.\n\n**Messages are inverted by default.** The item flips `color-scheme`, so a new\nmessage stands out from the page without using a color that carries meaning.",
+          "description": "Each message is an element because it has a timeout, a tone, a dismiss\ncontrol, and a lifetime that pauses.\n\n**Each item runs its own timer.** A timer held by the region would restart\nwith each new message, and the last of three messages would stay for nine\nseconds. It pauses while the pointer or focus is on the message, and while\nthe page is hidden, so a message is not spent in a background tab.\n\n**Each message is an `alertdialog` named by its words**, which is how a reader\nwho moves into the stack hears which message they are on. Give it a\n`heading` and a `description`, and the heading names it and the description\ndescribes it, for a message with a title and a line of detail. The region\nsays each message once as it arrives, a `danger` one assertively, so a\nmessage is never a live region of its own.\n\nA touch or a pen swipes a message toward the end of the line, and past\nhalfway, or quickly, dismisses it through the same `helix-dismiss` as its\ncontrol. While it moves, the distance is on the `item` part as\n`--toast-swipe-x`.\n\n**Escape dismisses the message holding focus**, through the same\n`helix-dismiss`, and focus moves to the next message.\n\n**Messages are inverted by default.** The item flips `color-scheme`, so a new\nmessage stands out from the page without using a color that carries meaning.",
           "name": "HelixHeadlessToastItem",
           "cssProperties": [
             {
@@ -168905,7 +169802,7 @@
               "name": "countdown",
               "privacy": "private",
               "readonly": true,
-              "default": "new CountdownController(this, { done: () => { this.dismiss() }, holdWhileHidden: true, paused: (paused) => { this.toggleAttribute('data-paused', paused) }, })",
+              "default": "new CountdownController(this, { done: () => { this.dismiss() }, holdWhileHidden: true, paused: (paused) => { this.toggleAttribute('data-paused', paused) this.toggleState('paused', paused) }, })",
               "description": "The dismiss timer, which pauses while a reader is on the message, and\nwhile the page is hidden, and continues from what was left. A message that\narrives in a background tab waits for the reader to come back, as React\nAria's toast queue does.\n\nPaused is said on the host so the indicator can freeze with the clock. A\n`data-` attribute rather than a property, because it is written after\nupgrade from a pointer moving: nothing declares it and no server rendered\nit, which is the same reason `Carousel` names its slides from here."
             },
             {
@@ -168918,6 +169815,54 @@
               "attribute": "tone",
               "reflects": true
             },
+            {
+              "kind": "field",
+              "name": "waiting",
+              "type": {
+                "text": "boolean"
+              },
+              "default": "false",
+              "description": "Whether the region holds the message back, because more messages are\nshowing than its `max-visible`. The region sets it. A waiting message is\nhidden, its timer has not started, and it is said once it shows."
+            },
+            {
+              "kind": "field",
+              "name": "started",
+              "type": {
+                "text": "boolean"
+              },
+              "privacy": "private",
+              "default": "false",
+              "description": "Whether the dismiss timer has started, which it does once the message first shows."
+            },
+            {
+              "kind": "field",
+              "name": "holding",
+              "type": {
+                "text": "boolean"
+              },
+              "privacy": "private",
+              "default": "false",
+              "description": "Whether the timer is held for `waiting`, so the hold is let go once."
+            },
+            {
+              "kind": "method",
+              "name": "wait",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "waiting",
+                  "type": {
+                    "text": "boolean"
+                  }
+                }
+              ],
+              "description": "Starts the timer when the message first shows, and holds it while it waits again."
+            },
             {
               "kind": "field",
               "name": "openState",
@@ -168983,6 +169928,13 @@
               "privacy": "private",
               "readonly": true
             },
+            {
+              "kind": "field",
+              "name": "handleKeydown",
+              "privacy": "private",
+              "readonly": true,
+              "description": "Escape dismisses the message holding focus, as Radix's toast does. Taken\nonly when the dismissal goes ahead, so a refused one leaves the key to\nthe page."
+            },
             {
               "kind": "method",
               "name": "assigned",
@@ -169109,7 +170061,7 @@
                   "text": "HTMLElement | undefined"
                 }
               },
-              "description": "The tab stop after this element on the page, or the one before it at the\nend, for a lone element whose removal would drop focus to the body.\n\n**A lone Callout or Announcement had nowhere to hand focus**, so a\nkeyboard reader who dismissed one started again from the top of the\npage. React Aria's Toast hands focus on the same way. Read before the\nevent, in the order Tab reaches the stops, while this element's own are\nstill among them.",
+              "description": "The tab stop after this element on the page, or the one before it at the\nend, for an element whose removal would drop focus to the body because\nno neighbor of its kind has a control to take it.\n\n**A lone Callout or Announcement had nowhere to hand focus**, so a\nkeyboard reader who dismissed one started again from the top of the\npage. React Aria's Toast hands focus on the same way. Read before the\nevent, in the order Tab reaches the stops, while this element's own are\nstill among them.",
               "inheritedFrom": {
                 "name": "MixinDismissible",
                 "module": "src/mixins/mixin-dismissible/mixin-dismissible.ts"
@@ -169590,6 +170542,28 @@
               }
             }
           ],
+          "cssStates": [
+            {
+              "description": "The message has been dismissed and is hidden, or leaving.",
+              "name": "closed"
+            },
+            {
+              "description": "The dismiss timer is paused, while a pointer or focus is on the message, or while the page is hidden.",
+              "name": "paused"
+            },
+            {
+              "description": "The region holds the message back, past its `max-visible`, until a message before it goes.",
+              "name": "waiting"
+            },
+            {
+              "description": "Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.",
+              "name": "settled",
+              "inheritedFrom": {
+                "name": "HelixElement",
+                "module": "src/helix-element/helix-element.ts"
+              }
+            }
+          ],
           "mixins": [
             {
               "name": "MixinDismissible",
@@ -169611,16 +170585,6 @@
           },
           "tagName": "helix-headless-toast-item",
           "customElement": true,
-          "cssStates": [
-            {
-              "description": "Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.",
-              "name": "settled",
-              "inheritedFrom": {
-                "name": "HelixElement",
-                "module": "src/helix-element/helix-element.ts"
-              }
-            }
-          ],
           "modulePath": "src/toast/item/toast-item.ts",
           "definitionPath": "src/toast/item/toast-item.ts"
         }
@@ -169650,7 +170614,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "The region and its items are one family because a live region must be in the\ndocument before a message is added to it. Assistive technology often does not\nannounce a region that arrives already holding its message. `Radio.Group` is\npart of its family for the same reason.\n\n**The region is a landmark named by `label`, and it says each message once\nas it arrives**: a `danger` message assertively, and every other one\npolitely. It says the word for the tone, the heading, the description and\nthe text, and not the actions, through two live regions of its own, the\n`live` parts, which it empties again a moment later. The stack itself is not\na live region, so a message is never said twice, and changing the words of a\nmessage already showing says nothing. Each message is an `alertdialog` named\nby its words, so a reader who moves into the stack hears which message they\nare on.\n\n**`hotkey` takes focus to the stack and back**, F8 unless you set it, and\n`label` says which key: `{hotkey}` in it is filled in, so the default name\nis \"Notifications (F8)\". Pressed while focus is in the stack, it gives focus\nback to where it was.\n\n**The region never creates or removes items.** You render items and remove\nthem. An item requests closing with a cancelable `helix-dismiss` event. A\ndismissed item hides itself and stays in the DOM, so your framework's state\nand the DOM stay in sync. It hides on its own unless you set `open`, which\nmakes the state yours.\n\n**`add()` shows a message from script**, for a page with no framework state\nto render them from: it appends a message of the region's own tier and\nremoves it once it has been dismissed and has finished leaving. Messages\nyou render yourself stay yours, and the region never removes them. A touch\nor a pen swipes a message away toward the end of the line.\n\n**The stack is in the top layer.** The `region` part is a `popover=\"manual\"`\nshown while a message is showing, and shown again above a modal dialog that\nopened after it. Position the `region` part, which is the box in the top\nlayer. While a modal `Dialog`, `Drawer` or `Lightbox` is open, the browser\nmakes everything outside it inert, the stack included, so a message stays\nvisible and its actions cannot be pressed. Where the browser has\n`ariaNotify`, a message that arrives then is announced through it. For a\nmessage with an action, render a second region inside the dialog.\n\nWhen a message with focus inside it is dismissed, focus moves to the next\nmessage, then the one before it, then back to where it was before it entered\nthe stack.",
+          "description": "The region and its items are one family because a live region must be in the\ndocument before a message is added to it. Assistive technology often does not\nannounce a region that arrives already holding its message. `Radio.Group` is\npart of its family for the same reason.\n\n**The region is a landmark named by `label`, and it says each message once\nas it arrives**: a `danger` message assertively, and every other one\npolitely. It says the word for the tone, the heading, the description and\nthe text, and not the actions, through two live regions of its own, the\n`live` parts, which it empties again a moment later. The stack itself is not\na live region, so a message is never said twice, and changing the words of a\nmessage already showing says nothing. Each message is an `alertdialog` named\nby its words, so a reader who moves into the stack hears which message they\nare on.\n\n**`hotkey` takes focus to the stack and back**, F8 unless you set it, and\n`label` says which key: `{hotkey}` in it is filled in, so the default name\nis \"Notifications (F8)\". Pressed while focus is in the stack, it gives focus\nback to where it was.\n\n**The region never creates or removes items.** You render items and remove\nthem. An item requests closing with a cancelable `helix-dismiss` event. A\ndismissed item hides itself and stays in the DOM, so your framework's state\nand the DOM stay in sync. It hides on its own unless you set `open`, which\nmakes the state yours.\n\n**`add()` shows a message from script**, for a page with no framework state\nto render them from: it appends a message of the region's own tier and\nremoves it once it has been dismissed and has finished leaving. Messages\nyou render yourself stay yours, and the region never removes them. A touch\nor a pen swipes a message away toward the end of the line.\n\n**The stack is in the top layer.** The `region` part is a `popover=\"manual\"`\nshown while a message is showing, and shown again above a modal dialog that\nopened after it. Position the `region` part, which is the box in the top\nlayer. While a modal `Dialog`, `Drawer` or `Lightbox` is open, the browser\nmakes everything outside it inert, the stack included, so a message stays\nvisible and its actions cannot be pressed. Where the browser has\n`ariaNotify`, a message that arrives then is announced through it. For a\nmessage with an action, render a second region inside the dialog.\n\nWhen a message with focus inside it is dismissed, focus moves to the next\nmessage, then the one before it, then back to where it was before it entered\nthe stack.\n\n**`max-visible` limits how many messages show at once**, as Zag's `max`\ndoes. The messages after that many, in document order, wait: each is hidden,\nits timer has not started, and the region says it once it shows, when a\nmessage before it goes. A waiting message has `:state(waiting)`.\n\n**Keyboard.**\n\n| Key | What it does |\n|---|---|\n| F8, or your `hotkey` | Moves focus to the first control in the stack, and back to where it was when pressed in the stack. |\n| Tab, Shift+Tab | Moves between the controls of the messages. |\n| Escape | Dismisses the message holding focus. Focus moves to the next message, then the one before it, then back to where it was. |",
           "name": "HelixHeadlessToast",
           "cssParts": [
             {
@@ -169702,6 +170666,15 @@
                 "words": true
               }
             },
+            {
+              "kind": "field",
+              "name": "maxVisible",
+              "type": {
+                "text": "number | undefined"
+              },
+              "description": "How many messages show at once. The messages after that many wait, hidden\nand with their timers stopped, until a message before them goes. Unset,\nevery message shows.",
+              "attribute": "max-visible"
+            },
             {
               "kind": "field",
               "name": "placement",
@@ -169887,6 +170860,36 @@
               "description": "The messages that are showing, in order.",
               "readonly": true
             },
+            {
+              "kind": "field",
+              "name": "held",
+              "privacy": "private",
+              "readonly": true,
+              "default": "new WeakSet<Element>()",
+              "description": "The messages `max-visible` holds back."
+            },
+            {
+              "kind": "method",
+              "name": "queue",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "HTMLElement[]"
+                }
+              },
+              "description": "Holds back the messages past `max-visible`, and returns the ones it has\njust let go. A message that has been dismissed takes no place in the line."
+            },
+            {
+              "kind": "method",
+              "name": "restack",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "description": "Lets go of the messages past `max-visible` that now have room, raises the\nstack and says them, once each has shown."
+            },
             {
               "kind": "field",
               "name": "region",
@@ -170348,6 +171351,14 @@
               "description": "Accessible name for the region, with `{hotkey}` filled in. Translate it with\nthe rest of your interface.",
               "fieldName": "label"
             },
+            {
+              "name": "max-visible",
+              "type": {
+                "text": "number | undefined"
+              },
+              "description": "How many messages show at once. The messages after that many wait, hidden\nand with their timers stopped, until a message before them goes. Unset,\nevery message shows.",
+              "fieldName": "maxVisible"
+            },
             {
               "name": "placement",
               "type": {
@@ -181373,6 +182384,10 @@
               "description": "The column at the start of an entry. It is a slot and is always present.",
               "name": "entry-start"
             },
+            {
+              "description": "The panel an entry's submenu opens in beside it. The playlist's entries have none.",
+              "name": "entry-surface"
+            },
             {
               "description": "The menu that holds the entries.",
               "name": "menu"
@@ -183442,6 +184457,10 @@
               "description": "The leading column that holds the `start` slot. It is always rendered.",
               "name": "entry-start"
             },
+            {
+              "description": "The panel a row's submenu opens in beside it. The player's rows have none.",
+              "name": "entry-surface"
+            },
             {
               "description": "The message shown when the source cannot be played.",
               "name": "failure"
@@ -187865,6 +188884,6 @@
   ],
   "helix": {
     "package": "@fusion.dev/helix-headless",
-    "version": "0.156.0"
+    "version": "0.158.0"
   }
 }