@fusion.dev/helix-headless 0.46.1 → 0.47.1

package/custom-elements.json

@@ -9611,6 +9611,10 @@
               "description": "The size one pane is laid out at. A sheet sets it and the component measures the run with it.",
               "name": "--carousel-pane"
             },
+            {
+              "description": "How many slides go across, written onto the track by the component so a sheet divides the track by the same number the positions are counted from. Read it rather than selecting on `per-view`, which cannot be enumerated without a ceiling. See `perView`.",
+              "name": "--carousel-per-view"
+            },
             {
               "description": "How far short of a whole pixel the run ends, on the last slide alone, for a sheet to take up as `margin-inline-end`. See `runEnd`.",
               "name": "--carousel-run-end"
@@ -9806,10 +9810,20 @@
               "type": {
                 "text": "number | undefined"
               },
-              "description": "How many slides are shown across the track at once. Absent shows one.\n\n**Here rather than on the styled tier, because it decides how many places\nthe track can stop.** From the stylesheet it looks like a width, one rule\nper value setting a custom property that the slides divide the track by.\nBut a carousel showing four of six slides has three positions, not six, and\neverything that counts positions is in this file. Declared up there, `goTo`\nclamps to the last *slide*, so three of the six indicators point at an\noffset the track has already reached: pressing next walks the dots to the\nend while the slides stop moving a third of the way through.\n\nNo default, because it reflects. A reflected property with a value writes\nits attribute on upgrade, and the host then carries something a consumer's\nserver markup never had, which React reports as a mismatch. The one-across\ncase is the absent attribute, and the styles read it that way.",
+              "description": "How many slides are shown across the track at once. Absent shows one.\n\n**Here rather than on the styled tier, because it decides how many places\nthe track can stop.** From the stylesheet it looks like a width, one rule\nper value setting a custom property that the slides divide the track by.\nBut a carousel showing four of six slides has three positions, not six, and\neverything that counts positions is in this file. Declared up there, `goTo`\nclamps to the last *slide*, so three of the six indicators point at an\noffset the track has already reached: pressing next walks the dots to the\nend while the slides stop moving a third of the way through.\n\n**The number is published to the styles rather than enumerated by them**,\nas `--carousel-per-view` on the track, which is what keeps a width and a\ncount from disagreeing. A sheet can only name a value it wrote a rule for,\nso the styled tier enumerated `per-view=\"2\"` through `5` and called five a\njudgment; above it the pane fell back to one across while this file went on\ncounting positions. Measured in Chromium over eight slides, six across gave\nthree dots, a pane taking the whole track and five slides reachable only by\ndragging. Written from here there is no ceiling to exceed, and a consumer's\nown sheet reads the same declaration the styled one does. `runEnd` publishes\nits correction the same way and for the same reason.\n\n**On the track and not on the host.** A custom property on the host is a\nreflected attribute by another name: it would arrive on upgrade, and a\nconsumer's server markup never had it. Inside the component's own shadow\nroot it serializes with the rest of the template on the server, and the\ntrack's own declaration beats anything a consumer inherits in, so the\nattribute is the one answer to how wide a pane is.\n\nA value the track cannot honor is taken to the nearest one it can, by\n`across`, and both tiers read that rather than this.\n\nNo default, because it reflects. A reflected property with a value writes\nits attribute on upgrade, and the host then carries something a consumer's\nserver markup never had, which React reports as a mismatch. The one-across\ncase is the absent attribute, and the styles read it that way.",
               "attribute": "per-view",
               "reflects": true
             },
+            {
+              "kind": "field",
+              "name": "across",
+              "type": {
+                "text": "number"
+              },
+              "privacy": "private",
+              "description": "`perView` as both tiers use it: a whole number of slides, one at least.\n\n**The clamp is here because the arithmetic is here**, and the two readers\nof this number have to be given the same one. A fraction is floored, since\na position is a whole slide along: one and a half across leaves a last\nposition the track runs out before reaching, which is the fault `goTo`\nalready carries a comment about. Zero and a negative divide the track into\nnothing and into a pane facing the wrong way, and a non-numeric attribute\nparses to `NaN`, which `Math.max` propagates: it counted `NaN` positions,\ndrew no indicators at all and left `index` at `NaN`. All of them read as\none across, which is what a carousel with nothing sayable asked for.\n\nNot clamped to the number of slides. Six across four slides is four panes\nat a sixth of the track each and the one place to stand, which is what was\nasked for as nearly as it can be had, and the slide count is a fact the\nserver does not have: clamping to it would draw one width there and another\non upgrade.",
+              "readonly": true
+            },
             {
               "kind": "field",
               "name": "positions",
@@ -10477,7 +10491,7 @@
               "type": {
                 "text": "number | undefined"
               },
-              "description": "How many slides are shown across the track at once. Absent shows one.\n\n**Here rather than on the styled tier, because it decides how many places\nthe track can stop.** From the stylesheet it looks like a width, one rule\nper value setting a custom property that the slides divide the track by.\nBut a carousel showing four of six slides has three positions, not six, and\neverything that counts positions is in this file. Declared up there, `goTo`\nclamps to the last *slide*, so three of the six indicators point at an\noffset the track has already reached: pressing next walks the dots to the\nend while the slides stop moving a third of the way through.\n\nNo default, because it reflects. A reflected property with a value writes\nits attribute on upgrade, and the host then carries something a consumer's\nserver markup never had, which React reports as a mismatch. The one-across\ncase is the absent attribute, and the styles read it that way.",
+              "description": "How many slides are shown across the track at once. Absent shows one.\n\n**Here rather than on the styled tier, because it decides how many places\nthe track can stop.** From the stylesheet it looks like a width, one rule\nper value setting a custom property that the slides divide the track by.\nBut a carousel showing four of six slides has three positions, not six, and\neverything that counts positions is in this file. Declared up there, `goTo`\nclamps to the last *slide*, so three of the six indicators point at an\noffset the track has already reached: pressing next walks the dots to the\nend while the slides stop moving a third of the way through.\n\n**The number is published to the styles rather than enumerated by them**,\nas `--carousel-per-view` on the track, which is what keeps a width and a\ncount from disagreeing. A sheet can only name a value it wrote a rule for,\nso the styled tier enumerated `per-view=\"2\"` through `5` and called five a\njudgment; above it the pane fell back to one across while this file went on\ncounting positions. Measured in Chromium over eight slides, six across gave\nthree dots, a pane taking the whole track and five slides reachable only by\ndragging. Written from here there is no ceiling to exceed, and a consumer's\nown sheet reads the same declaration the styled one does. `runEnd` publishes\nits correction the same way and for the same reason.\n\n**On the track and not on the host.** A custom property on the host is a\nreflected attribute by another name: it would arrive on upgrade, and a\nconsumer's server markup never had it. Inside the component's own shadow\nroot it serializes with the rest of the template on the server, and the\ntrack's own declaration beats anything a consumer inherits in, so the\nattribute is the one answer to how wide a pane is.\n\nA value the track cannot honor is taken to the nearest one it can, by\n`across`, and both tiers read that rather than this.\n\nNo default, because it reflects. A reflected property with a value writes\nits attribute on upgrade, and the host then carries something a consumer's\nserver markup never had, which React reports as a mismatch. The one-across\ncase is the absent attribute, and the styles read it that way.",
               "fieldName": "perView"
             }
           ],
@@ -24494,7 +24508,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "**The schema is markup and the data is a property.** Columns are declared as\n`helix-table-column` children, because a schema is small and something a\nreader should see in the HTML; rows are handed over as an array, because a\ntable that draws ten thousand elements cannot window them.\n\n```html\n<helix-data-table .rows=${rows} sort=\"name:asc\" page-size=\"20\">\n  <helix-table-column field=\"name\" sortable>Name</helix-table-column>\n  <helix-table-column field=\"size\" align=\"end\" sortable .cell=${bytes}>Size</helix-table-column>\n</helix-data-table>\n```\n\n`helix-table` takes rows as markup and is the right component for a table of\ntwelve things a person wrote out.\n\n**Sort and filter apply to the whole set, never the page.** Sorting the drawn\nwindow is correct on the first screen and wrong on every other one.\n\n**The cell values do not server-render.** The headings do, and the row\nelements do, but reading a cell needs the columns, and the columns are markup\nchildren Lit SSR does not hand this element. So a crawler sees a table of the\nright shape with nothing in it. That is the cost of the first paragraph: use\n`helix-table` where the served HTML has to carry the values.\n\n**`selectable` adds a column of checkboxes, keyed on `row-key`.** A row is\nselected by its identity rather than its position, so a selection survives a\nsort, a filter and a page. `selected` is the chosen keys, comma separated, the\nshape Listbox uses for a multiple choice, and like `sort` it is controlled\nwhen set and seeded by `default-selected`. The box in the heading selects every\nrow in the result, across pages, and shows a dash while only some are chosen.\nChoosing one of many, rather than several, is opening a row, and that is a\nlink or a button in a cell rather than a selection.\n\n**A reader can size and order the columns.** `resizable` on a column puts a\nseparator on its edge; `reorderable` on the table puts a grip on each heading\nthat has a `field`, moved by dragging or with the arrow keys. The order lands\nin `order` as fields, and the consumer's own markup is never rewritten: the\ntable assigns the headings to its header in that order instead.\n\n**`csv()` hands back the result as text**: every row the filter lets through,\nin the order on screen, in the columns on screen. Saving it is the page's\nbusiness, the same as any other file.",
+          "description": "**The schema is markup and the data is a property.** Columns are declared as\n`helix-table-column` children, because a schema is small and something a\nreader should see in the HTML; rows are handed over as an array, because a\ntable that draws ten thousand elements cannot window them.\n\n```html\n<helix-data-table .rows=${rows} sort=\"name:asc\" page-size=\"20\">\n  <helix-table-column field=\"name\" sortable>Name</helix-table-column>\n  <helix-table-column field=\"size\" align=\"end\" sortable .cell=${bytes}>Size</helix-table-column>\n</helix-data-table>\n```\n\n`helix-table` takes rows as markup and is the right component for a table of\ntwelve things a person wrote out.\n\n**Sort and filter apply to the whole set, never the page.** Sorting the drawn\nwindow is correct on the first screen and wrong on every other one.\n\n**The cell values do not server-render.** The headings do, and the row\nelements do, but reading a cell needs the columns, and the columns are markup\nchildren Lit SSR does not hand this element. So a crawler sees a table of the\nright shape with nothing in it. That is the cost of the first paragraph: use\n`helix-table` where the served HTML has to carry the values.\n\n**`selectable` adds a column of checkboxes, keyed on `row-key`.** A row is\nselected by its identity rather than its position, so a selection survives a\nsort, a filter and a page. `selected` is the chosen keys, comma separated, the\nshape Listbox uses for a multiple choice, and like `sort` it is controlled\nwhen set and seeded by `default-selected`. The box in the heading selects every\nrow in the result, across pages, and shows a dash while only some are chosen.\nChoosing one of many, rather than several, is opening a row, and that is a\nlink or a button in a cell rather than a selection.\n\n**A reader can size and order the columns.** `resizable` on a column puts a\nseparator on its edge; `reorderable` on the table puts a grip on each heading\nthat has a `field`, moved by dragging or with the arrow keys. The order lands\nin `order` as fields, and the consumer's own markup is never rewritten: the\ntable assigns the headings to its header in that order instead.\n\n**`csv()` hands back the result as text**: every row the filter lets through,\nin the order on screen, in the columns on screen. Saving it is the page's\nbusiness, the same as any other file.\n\n**There is no `columns` attribute here, and `helix-table` has one.** The\ndifference is what a column is in each: here it is the schema, so a table\nwithout one has nothing to read a row with, and every column is a place to\nwrite a `width`. A `helix-table` holds cells a consumer wrote and can be\nwritten with no column at all, so its `columns` is where such a table is\nsized from. Written on this element the attribute is inert, which is the trap\nworth knowing when moving between the two. What both take is the CSS hook,\n`--data-table-columns` here and `--table-columns` there.",
           "name": "HelixHeadlessDataTable",
           "cssProperties": [
             {
@@ -85507,7 +85521,7 @@
           "summary": "One cell of a table.",
           "helix": {
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/table",
             "aliases": [
               "Cell",
@@ -85600,7 +85614,7 @@
         },
         {
           "kind": "class",
-          "description": "**The column is the source of both its heading and its track.** Add one and\nthe table has another track; remove one and it does not. Declaring the widths\nseparately, as a CSS track list on the table, leaves nothing tying the two\ntogether: a table with three headings and a two-track list renders without\ncomplaint, and a track list that is accidentally the headings is invalid CSS\nthe grid silently ignores, collapsing the whole table into one column.\n\n**It is also where every per-column fact goes**, which is the reason\n`helix-data-table` needs no column config object. `field` names the key the\ncell reads, `sortable` says a reader may reorder by it, `align` says which\nedge the values line up against, and `cell` takes a function for anything the\nfield alone cannot express. The schema is markup and the data is a property:\na schema is small, declarative, and something a reader should be able to see\nin the HTML, and data is large and windowed.\n\n**The same element serves both tables**, the markup one and the data one. It\nis identified by a flag rather than by `instanceof`, so a `helix-table-column`\nworks inside either without the two roots sharing anything else.\n\n**It generates no box of its own**, the same as a row: the heading is a grid\nitem of the table, so it lines up with the cells under it rather than sitting\nin a wrapper that has to be kept the same width.\n\n**`hidden` takes the column out of the grid**, its heading and its track\nboth, so the columns after it keep their own widths and every row keeps its\ncells under their headings. `hidden=\"until-found\"` keeps its track, the\nheading being left drawn, as every Helix element leaves one with that value.\n`helix-data-table` draws the cells, so it leaves out the ones under a hidden\ncolumn. A `helix-table`'s cells are markup the consumer wrote, so hide them\nwith the column, as removing a column means removing its cells: a row with a\ncell more than the table has tracks wraps into the next.\n\n**A heading that does something holds a control that does it.** The host is\nthe column header, and a header is not focusable, so a sortable heading is a\n`<button>` inside it: the pattern for a sortable table, and the only way a\nreader on a keyboard reaches the sort at all. A column a reader may resize\ncarries a `separator` on its end edge, moved by dragging it or with the arrow\nkeys, and a column in a table that lets a reader reorder its columns carries\na grip the table moves.",
+          "description": "**The column is the source of both its heading and its track.** Add one and\nthe table has another track; remove one and it does not. That is what ties\nthe two together, and a table-level track list on its own does not: a list\nthat is accidentally the headings is invalid CSS a grid ignores in silence,\ndrawing the whole table as one column. `helix-table`'s `columns` is dealt out\na track at a time against the columns declared under it, so a heading among\nthe widths costs its own column a width and no more, and a list longer or\nshorter than the columns is trimmed or shared rather than being a second\ncount of them. A column's own `width` wins over the track in its place.\n\n**It is also where every per-column fact goes**, which is the reason\n`helix-data-table` needs no column config object. `field` names the key the\ncell reads, `sortable` says a reader may reorder by it, `align` says which\nedge the values line up against, and `cell` takes a function for anything the\nfield alone cannot express. The schema is markup and the data is a property:\na schema is small, declarative, and something a reader should be able to see\nin the HTML, and data is large and windowed.\n\n**The same element serves both tables**, the markup one and the data one. It\nis identified by a flag rather than by `instanceof`, so a `helix-table-column`\nworks inside either without the two roots sharing anything else.\n\n**It generates no box of its own**, the same as a row: the heading is a grid\nitem of the table, so it lines up with the cells under it rather than sitting\nin a wrapper that has to be kept the same width.\n\n**`hidden` takes the column out of the grid**, its heading and its track\nboth, so the columns after it keep their own widths and every row keeps its\ncells under their headings. `hidden=\"until-found\"` keeps its track, the\nheading being left drawn, as every Helix element leaves one with that value.\n`helix-data-table` draws the cells, so it leaves out the ones under a hidden\ncolumn. A `helix-table`'s cells are markup the consumer wrote, so hide them\nwith the column, as removing a column means removing its cells: a row with a\ncell more than the table has tracks wraps into the next.\n\n**A heading that does something holds a control that does it.** The host is\nthe column header, and a header is not focusable, so a sortable heading is a\n`<button>` inside it: the pattern for a sortable table, and the only way a\nreader on a keyboard reaches the sort at all. A column a reader may resize\ncarries a `separator` on its end edge, moved by dragging it or with the arrow\nkeys, and a column in a table that lets a reader reorder its columns carries\na grip the table moves.",
           "name": "HelixHeadlessTableColumn",
           "cssParts": [
             {
@@ -86310,7 +86324,7 @@
           "summary": "One column of a table: its heading, how wide it is, and what it reads.",
           "helix": {
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/table",
             "aliases": [
               "Column header",
@@ -86409,10 +86423,6 @@
           "description": "A grid rather than a `<table>`, so every column lines up across rows while\neach row stays a real element that can be styled, hidden, or made\ninteractive. Table layout gives column alignment and takes away almost\neverything else; grid gives both.\n\nThe cost is that the roles have to be declared, since a grid of divs is not a\ntable to anyone reading it. `table`, `row`, `cell`, and `columnheader` are\nall set explicitly, and rows are `display: contents` so their cells become\nitems of the one grid that does the aligning.\n\nThe properties below are written by this component and read by whoever draws\nit. A consumer sets none of them: they carry a number this element computed\nand CSS cannot, which is what lets a stylesheet on this tier draw the thing\nwithout measuring anything itself.",
           "name": "HelixHeadlessTable",
           "cssProperties": [
-            {
-              "description": "Track list for the columns.",
-              "name": "--table-columns"
-            },
             {
               "description": "The column track list this element worked out from the columns declared in it. Written by the component, read by the sheet that paints: a stylesheet takes it to lay the grid out, and setting it does nothing, because the component writes it inline on the very element that reads it and an inline declaration beats any sheet. `--table-columns` is the one to set.",
               "name": "--table-template"
@@ -86450,7 +86460,7 @@
                 "text": "string"
               },
               "default": "''",
-              "description": "The column widths as one track list, written once on the table.\n\nWith `helix-table-column` children, each track sizes the column in its\nplace, a hidden column counted, so hiding one takes its track with it and\nthe rest keep theirs. The columns decide how many tracks there are and this\nlist only how wide: a track past the last column is dropped, and a column\npast the last track shares what is left. With no columns declared it is\nthe whole track list. Tracks count as the grid counts them, so\n`minmax(0, 1fr)` is one and `repeat(2, 8rem)` is two, and one the grid\nwould refuse leaves its column at the default rather than taking the table\ndown to one column.\n\n**A column's own `width` wins over its track here.** The width is written\non the column it sizes, which is the more particular statement, and it is\nwhere a resize lands: a reader dragging a column's edge writes `width`, so\nwere this list to win, the drag would move the separator and leave the\ntrack where the list put it. This is the table's default for its columns,\nand each column may say otherwise.",
+              "description": "The column widths as one track list, written once on the table.\n\nWith `helix-table-column` children, each track sizes the column in its\nplace, a hidden column counted, so hiding one takes its track with it and\nthe rest keep theirs. The columns decide how many tracks there are and this\nlist only how wide: a track past the last column is dropped, and a column\npast the last track shares what is left. With no columns declared it is\nthe whole track list. Tracks count as the grid counts them, so\n`minmax(0, 1fr)` is one and `repeat(2, 8rem)` is two, and one the grid\nwould refuse leaves its column at the default rather than taking the table\ndown to one column.\n\n**A column's own `width` wins over its track here.** The width is written\non the column it sizes, which is the more particular statement, and it is\nwhere a resize lands: a reader dragging a column's edge writes `width`, so\nwere this list to win, the drag would move the separator and leave the\ntrack where the list put it. This is the table's default for its columns,\nand each column may say otherwise.\n\n**It is also the only track list a server can send.** The shim has no tree\nto walk, so a render there knows of no columns and this attribute is the\nwhole answer: a table given one lays its grid out in the first paint, and a\ntable sized only by its columns is one track wide until it upgrades.\n\n**`helix-data-table` has none of this, and should not.** Its columns are\nits schema rather than an option, so there is always a column to write a\n`width` on and a list here would be a second way to say what that says.\nThis table's cells are markup, and a table written as rows of cells with no\n`helix-table-column` in it has nowhere else to be sized from. Both families\ntake the same CSS hook, `--table-columns` and `--data-table-columns`, which\nwins over whichever list the element worked out.",
               "attribute": "columns"
             },
             {
@@ -87025,7 +87035,7 @@
                 "text": "string"
               },
               "default": "''",
-              "description": "The column widths as one track list, written once on the table.\n\nWith `helix-table-column` children, each track sizes the column in its\nplace, a hidden column counted, so hiding one takes its track with it and\nthe rest keep theirs. The columns decide how many tracks there are and this\nlist only how wide: a track past the last column is dropped, and a column\npast the last track shares what is left. With no columns declared it is\nthe whole track list. Tracks count as the grid counts them, so\n`minmax(0, 1fr)` is one and `repeat(2, 8rem)` is two, and one the grid\nwould refuse leaves its column at the default rather than taking the table\ndown to one column.\n\n**A column's own `width` wins over its track here.** The width is written\non the column it sizes, which is the more particular statement, and it is\nwhere a resize lands: a reader dragging a column's edge writes `width`, so\nwere this list to win, the drag would move the separator and leave the\ntrack where the list put it. This is the table's default for its columns,\nand each column may say otherwise.",
+              "description": "The column widths as one track list, written once on the table.\n\nWith `helix-table-column` children, each track sizes the column in its\nplace, a hidden column counted, so hiding one takes its track with it and\nthe rest keep theirs. The columns decide how many tracks there are and this\nlist only how wide: a track past the last column is dropped, and a column\npast the last track shares what is left. With no columns declared it is\nthe whole track list. Tracks count as the grid counts them, so\n`minmax(0, 1fr)` is one and `repeat(2, 8rem)` is two, and one the grid\nwould refuse leaves its column at the default rather than taking the table\ndown to one column.\n\n**A column's own `width` wins over its track here.** The width is written\non the column it sizes, which is the more particular statement, and it is\nwhere a resize lands: a reader dragging a column's edge writes `width`, so\nwere this list to win, the drag would move the separator and leave the\ntrack where the list put it. This is the table's default for its columns,\nand each column may say otherwise.\n\n**It is also the only track list a server can send.** The shim has no tree\nto walk, so a render there knows of no columns and this attribute is the\nwhole answer: a table given one lays its grid out in the first paint, and a\ntable sized only by its columns is one track wide until it upgrades.\n\n**`helix-data-table` has none of this, and should not.** Its columns are\nits schema rather than an option, so there is always a column to write a\n`width` on and a list here would be a second way to say what that says.\nThis table's cells are markup, and a table written as rows of cells with no\n`helix-table-column` in it has nowhere else to be sized from. Both families\ntake the same CSS hook, `--table-columns` and `--data-table-columns`, which\nwins over whichever list the element worked out.",
               "fieldName": "columns"
             },
             {
@@ -87091,7 +87101,7 @@
           "helix": {
             "category": "data",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/table",
             "aliases": [
               "DataTable",
@@ -87500,7 +87510,7 @@
           "summary": "One row of a table.",
           "helix": {
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/table",
             "aliases": [
               "Row",
@@ -102191,8 +102201,7 @@
               "type": {
                 "text": "number | undefined"
               },
-              "description": "Depth from the root, set by the tree so indentation needs no CSS nesting.\n\nNot reflected. The tree assigns this after it upgrades, so an attribute\nhere would be a change to markup the consumer rendered and hydration would\nreport it. The indent it drives is written onto the row instead, inside the\nshadow root, which is not part of the tree React hydrates.",
-              "attribute": "level"
+              "description": "Depth from the root, counted by the tree so indentation needs no CSS nesting.\n\n**Read rather than written, and no attribute at all.** The tree counts the\nitems a row sits inside and assigns this on every sync, so a value declared\nhere is overwritten before the first paint: measured at `level=\"2\"` on three\nrows of a flat list, all three back to 1 with `--tree-level: 1` on every\nrow. It carried an attribute and a shipped example setting it for as long as\nboth existed, which is a depth a consumer could state and nothing would\nhonor. Depth in this tree is where a row is, not what it claims: a branch's\nchildren go in its `children` slot, and that nesting is also what decides\nwhich rows a shut branch hides and which row the outward arrow moves to.\n\nNot reflected either. The tree assigns this after it upgrades, so an\nattribute here would be a change to markup the consumer rendered and\nhydration would report it. The indent it drives is written onto the row\ninstead, inside the shadow root, which is not part of the tree React\nhydrates."
             },
             {
               "kind": "field",
@@ -102211,7 +102220,7 @@
                 "text": "boolean"
               },
               "default": "false",
-              "description": "Whether this item is the current one.\n\nNot reflected, for the reason `level` below gives in full: the tree assigns\nthis after it upgrades, so the attribute would be a change to markup the\nconsumer rendered and hydration would report it. Mirroring to\n`data-selected` on the host instead is the same fault under another name.\n\nThe stylesheet reads it from the row inside this shadow root, because the\nrow is not part of the tree React hydrates.",
+              "description": "Whether this item is the current one.\n\nNot reflected, for the reason `level` above gives in full: the tree assigns\nthis after it upgrades, so the attribute would be a change to markup the\nconsumer rendered and hydration would report it. Mirroring to\n`data-selected` on the host instead is the same fault under another name.\n\nThe stylesheet reads it from the row inside this shadow root, because the\nrow is not part of the tree React hydrates.",
               "attribute": "selected"
             },
             {
@@ -102801,14 +102810,6 @@
               "description": "Where this node goes, which makes its row a real link.\n\nUnset by default, and unreflected: a tree of choosable nodes is not a tree\nof links, and an empty `href` written onto every row would be a link to the\ncurrent page on every item a consumer never asked to be one.",
               "fieldName": "href"
             },
-            {
-              "name": "level",
-              "type": {
-                "text": "number | undefined"
-              },
-              "description": "Depth from the root, set by the tree so indentation needs no CSS nesting.\n\nNot reflected. The tree assigns this after it upgrades, so an attribute\nhere would be a change to markup the consumer rendered and hydration would\nreport it. The indent it drives is written onto the row instead, inside the\nshadow root, which is not part of the tree React hydrates.",
-              "fieldName": "level"
-            },
             {
               "name": "rel",
               "type": {
@@ -102824,7 +102825,7 @@
                 "text": "boolean"
               },
               "default": "false",
-              "description": "Whether this item is the current one.\n\nNot reflected, for the reason `level` below gives in full: the tree assigns\nthis after it upgrades, so the attribute would be a change to markup the\nconsumer rendered and hydration would report it. Mirroring to\n`data-selected` on the host instead is the same fault under another name.\n\nThe stylesheet reads it from the row inside this shadow root, because the\nrow is not part of the tree React hydrates.",
+              "description": "Whether this item is the current one.\n\nNot reflected, for the reason `level` above gives in full: the tree assigns\nthis after it upgrades, so the attribute would be a change to markup the\nconsumer rendered and hydration would report it. Mirroring to\n`data-selected` on the host instead is the same fault under another name.\n\nThe stylesheet reads it from the row inside this shadow root, because the\nrow is not part of the tree React hydrates.",
               "fieldName": "selected"
             },
             {
@@ -102902,7 +102903,7 @@
           "summary": "One node in a tree.",
           "helix": {
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/tree",
             "aliases": [
               "TreeNode",
@@ -103795,7 +103796,7 @@
           "helix": {
             "category": "navigation",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/tree",
             "aliases": [
               "FileTree",

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

@@ -44,6 +44,7 @@ import { type PropertyValues, type TemplateResult } from 'lit';
  *
  * @cssproperty --carousel-gap - Space between slides. A sheet sets it and the component measures the run with it.
  * @cssproperty --carousel-pane - The size one pane is laid out at. A sheet sets it and the component measures the run with it.
+ * @cssproperty --carousel-per-view - How many slides go across, written onto the track by the component so a sheet divides the track by the same number the positions are counted from. Read it rather than selecting on `per-view`, which cannot be enumerated without a ceiling. See `perView`.
  * @cssproperty --carousel-run-end - How far short of a whole pixel the run ends, on the last slide alone, for a sheet to take up as `margin-inline-end`. See `runEnd`.
  */
 export declare class HelixHeadlessCarousel extends HelixElement {
@@ -161,12 +162,53 @@ export declare class HelixHeadlessCarousel extends HelixElement {
      * offset the track has already reached: pressing next walks the dots to the
      * end while the slides stop moving a third of the way through.
      *
+     * **The number is published to the styles rather than enumerated by them**,
+     * as `--carousel-per-view` on the track, which is what keeps a width and a
+     * count from disagreeing. A sheet can only name a value it wrote a rule for,
+     * so the styled tier enumerated `per-view="2"` through `5` and called five a
+     * judgment; above it the pane fell back to one across while this file went on
+     * counting positions. Measured in Chromium over eight slides, six across gave
+     * three dots, a pane taking the whole track and five slides reachable only by
+     * dragging. Written from here there is no ceiling to exceed, and a consumer's
+     * own sheet reads the same declaration the styled one does. `runEnd` publishes
+     * its correction the same way and for the same reason.
+     *
+     * **On the track and not on the host.** A custom property on the host is a
+     * reflected attribute by another name: it would arrive on upgrade, and a
+     * consumer's server markup never had it. Inside the component's own shadow
+     * root it serializes with the rest of the template on the server, and the
+     * track's own declaration beats anything a consumer inherits in, so the
+     * attribute is the one answer to how wide a pane is.
+     *
+     * A value the track cannot honor is taken to the nearest one it can, by
+     * `across`, and both tiers read that rather than this.
+     *
      * No default, because it reflects. A reflected property with a value writes
      * its attribute on upgrade, and the host then carries something a consumer's
      * server markup never had, which React reports as a mismatch. The one-across
      * case is the absent attribute, and the styles read it that way.
      */
     perView?: number;
+    /**
+     * `perView` as both tiers use it: a whole number of slides, one at least.
+     *
+     * **The clamp is here because the arithmetic is here**, and the two readers
+     * of this number have to be given the same one. A fraction is floored, since
+     * a position is a whole slide along: one and a half across leaves a last
+     * position the track runs out before reaching, which is the fault `goTo`
+     * already carries a comment about. Zero and a negative divide the track into
+     * nothing and into a pane facing the wrong way, and a non-numeric attribute
+     * parses to `NaN`, which `Math.max` propagates: it counted `NaN` positions,
+     * drew no indicators at all and left `index` at `NaN`. All of them read as
+     * one across, which is what a carousel with nothing sayable asked for.
+     *
+     * Not clamped to the number of slides. Six across four slides is four panes
+     * at a sixth of the track each and the one place to stand, which is what was
+     * asked for as nearly as it can be had, and the slide count is a fact the
+     * server does not have: clamping to it would draw one width there and another
+     * on upgrade.
+     */
+    private get across();
     /**
      * How many distinct views the track holds, which is what the indicators count.
      *

package/dist/carousel/root/carousel-root.js

@@ -95,9 +95,12 @@ let HelixHeadlessCarousel = class HelixHeadlessCarousel extends HelixElement {
         this.indexState = next;
         this.requestUpdate('index', previous);
     }
+    get across() {
+        const asked = this.perView ?? 1;
+        return Number.isFinite(asked) ? Math.max(1, Math.floor(asked)) : 1;
+    }
     get positions() {
-        const across = Math.max(1, Math.floor(this.perView ?? 1));
-        return Math.max(1, this.slides.length - across + 1);
+        return Math.max(1, this.slides.length - this.across + 1);
     }
     get panes() {
         return [...(this.renderRoot?.querySelectorAll?.('[part="slide"]') ?? [])];
@@ -305,6 +308,7 @@ let HelixHeadlessCarousel = class HelixHeadlessCarousel extends HelixElement {
       <div
         data-scroller
         part="track"
+        style=${`--carousel-per-view: ${this.across}`}
         @scroll=${this.handleTrackScroll}
         @scrollend=${this.handleScroll}
         @pointerdown=${this.handleTake}

package/dist/data-table/root/data-table-root.d.ts

@@ -52,6 +52,15 @@ declare const HelixHeadlessDataTable_base: (new (...args: any[]) => import("@fus
  * in the order on screen, in the columns on screen. Saving it is the page's
  * business, the same as any other file.
  *
+ * **There is no `columns` attribute here, and `helix-table` has one.** The
+ * difference is what a column is in each: here it is the schema, so a table
+ * without one has nothing to read a row with, and every column is a place to
+ * write a `width`. A `helix-table` holds cells a consumer wrote and can be
+ * written with no column at all, so its `columns` is where such a table is
+ * sized from. Written on this element the attribute is inert, which is the trap
+ * worth knowing when moving between the two. What both take is the CSS hook,
+ * `--data-table-columns` here and `--table-columns` there.
+ *
  * @since 0.1.0
  * @status stable
  * @category data

package/dist/table/cell/table-cell.d.ts

@@ -13,7 +13,7 @@ import { type PropertyValues, type TemplateResult } from 'lit';
  * to hold together.
  *
  * @since 0.1.0
- * @status experimental
+ * @status stable
  * @aliases Cell, TableCell
  * @documentation https://fusion.dev/helix/components/table
  *

package/dist/table/column/table-column.d.ts

@@ -35,11 +35,14 @@ export declare const edgeOf: (align: string | undefined) => string | undefined;
  *
  * @description
  * **The column is the source of both its heading and its track.** Add one and
- * the table has another track; remove one and it does not. Declaring the widths
- * separately, as a CSS track list on the table, leaves nothing tying the two
- * together: a table with three headings and a two-track list renders without
- * complaint, and a track list that is accidentally the headings is invalid CSS
- * the grid silently ignores, collapsing the whole table into one column.
+ * the table has another track; remove one and it does not. That is what ties
+ * the two together, and a table-level track list on its own does not: a list
+ * that is accidentally the headings is invalid CSS a grid ignores in silence,
+ * drawing the whole table as one column. `helix-table`'s `columns` is dealt out
+ * a track at a time against the columns declared under it, so a heading among
+ * the widths costs its own column a width and no more, and a list longer or
+ * shorter than the columns is trimmed or shared rather than being a second
+ * count of them. A column's own `width` wins over the track in its place.
  *
  * **It is also where every per-column fact goes**, which is the reason
  * `helix-data-table` needs no column config object. `field` names the key the
@@ -75,7 +78,7 @@ export declare const edgeOf: (align: string | undefined) => string | undefined;
  * a grip the table moves.
  *
  * @since 0.1.0
- * @status experimental
+ * @status stable
  * @aliases Column header, Th
  * @documentation https://fusion.dev/helix/components/table
  *

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

@@ -22,7 +22,7 @@ declare const HelixHeadlessTable_base: (new (...args: any[]) => import("@fusion.
  * without measuring anything itself.
  *
  * @since 0.1.0
- * @status experimental
+ * @status stable
  * @category data
  * @aliases DataTable, Grid table
  * @documentation https://fusion.dev/helix/components/table
@@ -34,7 +34,6 @@ declare const HelixHeadlessTable_base: (new (...args: any[]) => import("@fusion.
  * @csspart loading - Shown while the rows are still on their way.
  * @csspart table - The grid.
  *
- * @cssproperty --table-columns - Track list for the columns.
  * @cssproperty --table-template - The column track list this element worked out from the columns declared in it. Written by the component, read by the sheet that paints: a stylesheet takes it to lay the grid out, and setting it does nothing, because the component writes it inline on the very element that reads it and an inline declaration beats any sheet. `--table-columns` is the one to set.
  */
 export declare class HelixHeadlessTable extends HelixHeadlessTable_base {
@@ -57,6 +56,19 @@ export declare class HelixHeadlessTable extends HelixHeadlessTable_base {
      * were this list to win, the drag would move the separator and leave the
      * track where the list put it. This is the table's default for its columns,
      * and each column may say otherwise.
+     *
+     * **It is also the only track list a server can send.** The shim has no tree
+     * to walk, so a render there knows of no columns and this attribute is the
+     * whole answer: a table given one lays its grid out in the first paint, and a
+     * table sized only by its columns is one track wide until it upgrades.
+     *
+     * **`helix-data-table` has none of this, and should not.** Its columns are
+     * its schema rather than an option, so there is always a column to write a
+     * `width` on and a list here would be a second way to say what that says.
+     * This table's cells are markup, and a table written as rows of cells with no
+     * `helix-table-column` in it has nowhere else to be sized from. Both families
+     * take the same CSS hook, `--table-columns` and `--data-table-columns`, which
+     * wins over whichever list the element worked out.
      */
     columns: string;
     /**

package/dist/table/row/table-row.d.ts

@@ -10,7 +10,7 @@ import { type PropertyValues, type TemplateResult } from 'lit';
  * cells are laid out by the table algorithm.
  *
  * @since 0.1.0
- * @status experimental
+ * @status stable
  * @aliases Row, TableRow
  * @documentation https://fusion.dev/helix/components/table
  *

package/dist/tree/item/tree-item.d.ts

@@ -24,7 +24,7 @@ declare const HelixHeadlessTreeItem_base: (new (...args: any[]) => import("@fusi
  * click, no status bar. Given an `href` the row *is* an `<a>`.
  *
  * @since 0.1.0
- * @status experimental
+ * @status stable
  * @aliases TreeNode, Branch, Leaf
  * @documentation https://fusion.dev/helix/components/tree
  *
@@ -59,12 +59,23 @@ export declare class HelixHeadlessTreeItem extends HelixHeadlessTreeItem_base {
      */
     href: string;
     /**
-     * Depth from the root, set by the tree so indentation needs no CSS nesting.
+     * Depth from the root, counted by the tree so indentation needs no CSS nesting.
      *
-     * Not reflected. The tree assigns this after it upgrades, so an attribute
-     * here would be a change to markup the consumer rendered and hydration would
-     * report it. The indent it drives is written onto the row instead, inside the
-     * shadow root, which is not part of the tree React hydrates.
+     * **Read rather than written, and no attribute at all.** The tree counts the
+     * items a row sits inside and assigns this on every sync, so a value declared
+     * here is overwritten before the first paint: measured at `level="2"` on three
+     * rows of a flat list, all three back to 1 with `--tree-level: 1` on every
+     * row. It carried an attribute and a shipped example setting it for as long as
+     * both existed, which is a depth a consumer could state and nothing would
+     * honor. Depth in this tree is where a row is, not what it claims: a branch's
+     * children go in its `children` slot, and that nesting is also what decides
+     * which rows a shut branch hides and which row the outward arrow moves to.
+     *
+     * Not reflected either. The tree assigns this after it upgrades, so an
+     * attribute here would be a change to markup the consumer rendered and
+     * hydration would report it. The indent it drives is written onto the row
+     * instead, inside the shadow root, which is not part of the tree React
+     * hydrates.
      */
     level?: number;
     /**
@@ -79,7 +90,7 @@ export declare class HelixHeadlessTreeItem extends HelixHeadlessTreeItem_base {
     /**
      * Whether this item is the current one.
      *
-     * Not reflected, for the reason `level` below gives in full: the tree assigns
+     * Not reflected, for the reason `level` above gives in full: the tree assigns
      * this after it upgrades, so the attribute would be a change to markup the
      * consumer rendered and hydration would report it. Mirroring to
      * `data-selected` on the host instead is the same fault under another name.
@@ -111,9 +122,11 @@ export declare class HelixHeadlessTreeItem extends HelixHeadlessTreeItem_base {
     private branch;
     protected firstUpdated(changed: PropertyValues): void;
     /**
-     * @internal Read by the tree to identify a branch across the light DOM,
-     * which is cheaper than `instanceof` and is why this is public rather than
-     * protected. A consumer asks `branch`, which is the property they set.
+     * @internal Whether this row holds children, read by the tree, which moves
+     * and opens differently for a branch. Public rather than protected because
+     * the tree is another element and there is no other way across; not a
+     * consumer's to read, and there is nothing to set: it is what the `children`
+     * slot was given, which is the markup they already wrote.
      */
     get isBranch(): boolean;
     /**

package/dist/tree/item/tree-item.js

@@ -148,7 +148,7 @@ __decorate([
     property()
 ], HelixHeadlessTreeItem.prototype, "href", void 0);
 __decorate([
-    property({ attribute: 'level', type: Number })
+    property({ attribute: false, type: Number })
 ], HelixHeadlessTreeItem.prototype, "level", void 0);
 __decorate([
     property()

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

@@ -14,7 +14,7 @@ declare const HelixHeadlessTree_base: (new (...args: any[]) => import("@fusion.d
  * does not learn about the styled one.
  *
  * @since 0.1.0
- * @status experimental
+ * @status stable
  * @category navigation
  * @aliases FileTree, Navigation tree
  * @documentation https://fusion.dev/helix/components/tree

package/package.json

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