@fusion.dev/helix-headless 0.40.0 → 0.41.1

package/custom-elements.json

@@ -2235,7 +2235,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "The chart for a composition: every column of the table is a part, the parts\nsum to the whole at each reading, and the top edge is that whole. What a line\nchart of the same table cannot show is the share, which here is the\nthickness of a band.\n\n**Not `Line Chart` with `area`.** That washes each series from the floor on\nits own, so the series overlap; this adds them. Reach for `Line Chart` when\nthe question is how each series moved, and for this when it is how the whole\nis made up.\n\n**It measures from zero, always**, which is `BarChart`'s rule and for the same\nreason: a band's thickness *is* its value, so a range that starts anywhere\nelse draws every part in proportion to nothing. `LineChart` measures from its\nown range because a line claims a position; a band claims an amount.\n\n**Straight between readings unless asked otherwise.** A band's top edge is a\nsum, and a curve fitted through one sum can pass under the curve fitted\nthrough the sum beneath it, so a smoothed stack can draw a part as less than\nnothing between two readings. Straight segments between ordered points stay\nordered. `curve=\"smooth\"` is there for a stack that is read as a shape.\n\n**`share` draws each reading as a hundred percent**, so the bands are the\nparts' shares and the top edge is flat. It answers \"which part grew\" where\nthe default answers \"did the whole grow\".\n\n**What a reader without the picture is told is the total and the share**, not\nevery band in turn. The table beside the chart already reads out every\nnumber; what the drawing adds is the composition, so the summary says the\nlatest reading's total and each part's share of it. The drawing itself is\n`aria-hidden`.\n\nEvery numeric column is a part. A table that carries its own total column\nwould count it twice, so leave it out of the table the chart reads.\nA negative reading is drawn as none: a part of a whole cannot be less than\nnothing, and a band that folded under its neighbor would say it was.",
+          "description": "The chart for a composition: every column of the table is a part, the parts\nsum to the whole at each reading, and the top edge is that whole. What a line\nchart of the same table cannot show is the share, which here is the\nthickness of a band.\n\n**Not `Line Chart` with `area`.** That washes each series from the floor on\nits own, so the series overlap; this adds them. Reach for `Line Chart` when\nthe question is how each series moved, and for this when it is how the whole\nis made up.\n\n**It measures from zero, always**, which is `BarChart`'s rule and for the same\nreason: a band's thickness *is* its value, so a range that starts anywhere\nelse draws every part in proportion to nothing. `LineChart` measures from its\nown range because a line claims a position; a band claims an amount.\n\n**And so it is not a streamgraph**, which is the near neighbor to name.\nA streamgraph moves its baseline to center the bands and reads as a river; it\nis a real form and it is the one thing the rule above refuses, so this\ncarries no alias for it. What it has instead is `share`, which answers the\nquestion a streamgraph is usually reached for, how the composition changed,\nwithout giving up a floor a reader can measure against.\n\n**Straight between readings unless asked otherwise.** A band's top edge is a\nsum, and a curve fitted through one sum can pass under the curve fitted\nthrough the sum beneath it, so a smoothed stack can draw a part as less than\nnothing between two readings. Straight segments between ordered points stay\nordered. `curve=\"smooth\"` is there for a stack that is read as a shape.\n\n`curve=\"step\"` falls on the safe side of that argument rather than being\nunanswered by it, and it is worth saying which side because a reader cannot\ntell from the argument alone. A step takes no value the readings do not have:\nit holds one, jumps at the midpoint, and holds the next. So two stepped edges\nthat are ordered at every reading are ordered everywhere between them, which\nis what `straight` is chosen for. It is the curve for a quantity that changes\nat a moment rather than across an interval, a headcount or a price, where a\nsloped edge claims a gradual change nothing measured.\n\n**`share` draws each reading as a hundred percent**, so the bands are the\nparts' shares and the top edge is flat. It answers \"which part grew\" where\nthe default answers \"did the whole grow\".\n\n**What a reader without the picture is told is the total and the share**, not\nevery band in turn. The table beside the chart already reads out every\nnumber; what the drawing adds is the composition, so the summary says the\nlatest reading's total and each part's share of it. The drawing itself is\n`aria-hidden`.\n\nEvery numeric column is a part. A table that carries its own total column\nwould count it twice, so leave it out of the table the chart reads.\nA negative reading is drawn as none: a part of a whole cannot be less than\nnothing, and a band that folded under its neighbor would say it was.",
           "name": "HelixHeadlessAreaChart",
           "cssParts": [
             {
@@ -2350,7 +2350,7 @@
               "type": {
                 "text": "Curve | undefined"
               },
-              "description": "How a band's edge gets from one reading to the next.\n\nAbsent is `straight`, for the reason the class doc gives, and absent rather\nthan defaulted because a reflecting property with a default writes its\nattribute onto every host, including the ones nobody configured.",
+              "description": "How a band's edge gets from one reading to the next.\n\nThree values, and the class doc argues for each: `straight` is absent and\nis the default, `smooth` is for a stack read as a shape and is the one that\ncan draw a part as less than nothing, `step` is for a quantity that changes\nat a moment and is ordered the way `straight` is.\n\nAbsent rather than defaulted because a reflecting property with a default\nwrites its attribute onto every host, including the ones nobody configured.",
               "attribute": "curve",
               "reflects": true
             },
@@ -2754,6 +2754,44 @@
                 "module": "src/mixins/mixin-chart-source/mixin-chart-source.ts"
               }
             },
+            {
+              "kind": "field",
+              "name": "plottedColumns",
+              "type": {
+                "text": "number[]"
+              },
+              "description": "Which cells of a row hold numbers, by their place in it, in table order.\n\nThe same test `readSeries` applies when it drops a column of notes: a\ncolumn is a series where any row parses, so a series survives one blank\ncell and a column of words is never one.",
+              "readonly": true,
+              "inheritedFrom": {
+                "name": "MixinChartSource",
+                "module": "src/mixins/mixin-chart-source/mixin-chart-source.ts"
+              }
+            },
+            {
+              "kind": "method",
+              "name": "seriesOf",
+              "return": {
+                "type": {
+                  "text": "number | undefined"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "cell",
+                  "type": {
+                    "text": "number"
+                  }
+                }
+              ],
+              "description": "The palette slot the cell at this place in a row is drawn in.\n\n**A cell's place in its row is not its series' depth, and the tooltip\nspent a while assuming it was.** `readSeries` drops a column nothing\nparses and `readRows` keeps it, so one column of notes among the figures\nmoves every column after it one color along in the bubble: a row reading\n`Referral 1,080` wearing series three's green beside a legend that says\nseries three is something else, which is the one failure the dot exists\nto prevent.\n\nOverridden where a chart reads the table some other way. `ScatterChart`\nsplits the first plotted column off as the measure across, so its first\n*plotted* series is this table's second numeric column.",
+              "inheritedFrom": {
+                "name": "MixinChartSource",
+                "module": "src/mixins/mixin-chart-source/mixin-chart-source.ts"
+              },
+              "type": {
+                "text": "seriesOf(cell: number) => number | undefined"
+              }
+            },
             {
               "kind": "field",
               "name": "readings",
@@ -3098,7 +3136,7 @@
               "type": {
                 "text": "Curve | undefined"
               },
-              "description": "How a band's edge gets from one reading to the next.\n\nAbsent is `straight`, for the reason the class doc gives, and absent rather\nthan defaulted because a reflecting property with a default writes its\nattribute onto every host, including the ones nobody configured.",
+              "description": "How a band's edge gets from one reading to the next.\n\nThree values, and the class doc argues for each: `straight` is absent and\nis the default, `smooth` is for a stack read as a shape and is the one that\ncan draw a part as less than nothing, `step` is for a quantity that changes\nat a moment and is ordered the way `straight` is.\n\nAbsent rather than defaulted because a reflecting property with a default\nwrites its attribute onto every host, including the ones nobody configured.",
               "fieldName": "curve"
             },
             {
@@ -3168,12 +3206,12 @@
           "helix": {
             "category": "charts",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/area-chart",
             "aliases": [
               "Stacked Area Chart",
               "Composition Chart",
-              "Stream Chart"
+              "Banded Chart"
             ],
             "tier": "headless",
             "group": "BaseAreaChart",
@@ -4797,7 +4835,7 @@
           "name": "HelixHeadlessBarChart",
           "cssProperties": [
             {
-              "description": "The color of a single-series axis, taken from that series.",
+              "description": "How wide an axis column is drawn, in `ch`, from the widest number on it. Written on the axis itself, and only where the categories run along the bottom: turned sideways an axis is a row and takes a line's height instead.",
               "name": "--bar-chart-axis"
             },
             {
@@ -4961,7 +4999,7 @@
               "type": {
                 "text": "string | undefined"
               },
-              "description": "Which series are drawn as a line instead of as columns, by name.\n\nSpace separated, matched against the column headings the table gives, so a\nchart says `lines=\"Margin\"` rather than counting columns. Names because\nthey are what the table already carries and what the legend already shows:\nan index is a fourth place the column order is written down and the first\none to go stale when somebody moves a column.\n\n**A combination chart is one scale, and that is the honest half of it.**\nBoth marks are measured against the same domain, so a line here says\nsomething comparable to the columns beside it. The usual reason to reach\nfor a combination chart is the other thing, a count against a percentage on\na second axis, and that is deliberately not this: two scales on one frame\nlet the author put any two shapes in any relation by choosing the ranges,\nand the reader has no way to see it happening.\n\nA line among columns still measures from zero, because the columns do and\nthey share the axis.",
+              "description": "Which series are drawn as a line instead of as columns, by name.\n\nSeparated by whitespace or commas and matched against the column headings\nthe table gives, so a chart says `lines=\"Margin\"` rather than counting\ncolumns. Names because they are what the table already carries and what the\nlegend already shows: an index is a fourth place the column order is\nwritten down and the first one to go stale when somebody moves a column.\n\n**This says which mark a series takes and nothing about which scale it is\nmeasured on.** Named here alone, a line shares the columns' domain, so it\nsays something comparable to the columns beside it.\n\nThe other half of a combination chart, a count against a percentage on a\nscale of its own, is `secondary`, which is a separate property because it\nis a separate question and because the two compose: `with-a-second-axis`\nships naming one series in both. The argument for why a second scale is opt\nin, and why setting it labels both axes, is written there.\n\nA line among columns measures from zero, because the columns do and they\nshare the axis. So does a line on the second scale, which is that scale's\nown rule rather than this one's.",
               "attribute": "lines"
             },
             {
@@ -4970,7 +5008,7 @@
               "type": {
                 "text": "string | undefined"
               },
-              "description": "Which series are measured against a scale of their own, by name.\n\nSpace separated and matched the way `lines` is, against the column headings\nthe table gives. Opt in: absent, every series shares one domain, which is\nwhat makes a chart comparable and is the right default.\n\n**Two scales on one frame let an author put any two shapes in any relation\nby choosing the ranges, and a reader cannot see it happening.** That is not\na caveat, it is what the feature does: a line that crosses the columns\ntwice and a line that never touches them can be the same two series drawn\nagainst different ranges. It earns its place when the two quantities are\ngenuinely incomparable, a count against a percentage, and it is a way to\nmislead in every other case.\n\n**So it draws its axes**, and that is not optional here. The chart renders\nno value axis at all when there is one scale, because the columns are\nmeasured against each other and a reader needs no numbers to do that. With\ntwo, a reader has no way of knowing there are two, let alone which series\nis on which, so both scales are labeled the moment this is set. An\nunlabeled second axis is the deceptive case rather than the tidy one.\n\nThe grid stays on the primary axis, since a rule measured against two\nscales at once is a rule that means nothing. The tooltip is unaffected: it\nhas always shown every column's own number, which is the reader's way out\nof any scale question the picture raises.",
+              "description": "Which series are measured against a scale of their own, by name.\n\nSeparated and matched the way `lines` is, against the column headings the\ntable gives. Opt in: absent, every series shares one domain, which is what\nmakes a chart comparable and is the right default.\n\n**The scale, and `lines` is the mark.** The two are separate properties\nbecause they answer separate questions and a series usually wants both:\na percentage beside a count is drawn as a line *and* measured on its own\naxis, which is what `with-a-second-axis` writes out. Neither implies the\nother, so a series can be a line on the shared scale and a column can have\na scale to itself.\n\n**Two scales on one frame let an author put any two shapes in any relation\nby choosing the ranges, and a reader cannot see it happening.** That is not\na caveat, it is what the feature does: a line that crosses the columns\ntwice and a line that never touches them can be the same two series drawn\nagainst different ranges. It earns its place when the two quantities are\ngenuinely incomparable, a count against a percentage, and it is a way to\nmislead in every other case.\n\n**So it draws its axes**, and that is not optional here. The chart renders\nno value axis at all when there is one scale, because the columns are\nmeasured against each other and a reader needs no numbers to do that. With\ntwo, a reader has no way of knowing there are two, let alone which series\nis on which, so both scales are labeled the moment this is set. An\nunlabeled second axis is the deceptive case rather than the tidy one.\n\nThe grid stays on the primary axis, since a rule measured against two\nscales at once is a rule that means nothing. The tooltip is unaffected: it\nhas always shown every column's own number, which is the reader's way out\nof any scale question the picture raises.",
               "attribute": "secondary",
               "reflects": true
             },
@@ -5338,6 +5376,44 @@
                 "module": "src/mixins/mixin-chart-source/mixin-chart-source.ts"
               }
             },
+            {
+              "kind": "field",
+              "name": "plottedColumns",
+              "type": {
+                "text": "number[]"
+              },
+              "description": "Which cells of a row hold numbers, by their place in it, in table order.\n\nThe same test `readSeries` applies when it drops a column of notes: a\ncolumn is a series where any row parses, so a series survives one blank\ncell and a column of words is never one.",
+              "readonly": true,
+              "inheritedFrom": {
+                "name": "MixinChartSource",
+                "module": "src/mixins/mixin-chart-source/mixin-chart-source.ts"
+              }
+            },
+            {
+              "kind": "method",
+              "name": "seriesOf",
+              "return": {
+                "type": {
+                  "text": "number | undefined"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "cell",
+                  "type": {
+                    "text": "number"
+                  }
+                }
+              ],
+              "description": "The palette slot the cell at this place in a row is drawn in.\n\n**A cell's place in its row is not its series' depth, and the tooltip\nspent a while assuming it was.** `readSeries` drops a column nothing\nparses and `readRows` keeps it, so one column of notes among the figures\nmoves every column after it one color along in the bubble: a row reading\n`Referral 1,080` wearing series three's green beside a legend that says\nseries three is something else, which is the one failure the dot exists\nto prevent.\n\nOverridden where a chart reads the table some other way. `ScatterChart`\nsplits the first plotted column off as the measure across, so its first\n*plotted* series is this table's second numeric column.",
+              "inheritedFrom": {
+                "name": "MixinChartSource",
+                "module": "src/mixins/mixin-chart-source/mixin-chart-source.ts"
+              },
+              "type": {
+                "text": "seriesOf(cell: number) => number | undefined"
+              }
+            },
             {
               "kind": "field",
               "name": "readings",
@@ -5698,7 +5774,7 @@
               "type": {
                 "text": "string | undefined"
               },
-              "description": "Which series are drawn as a line instead of as columns, by name.\n\nSpace separated, matched against the column headings the table gives, so a\nchart says `lines=\"Margin\"` rather than counting columns. Names because\nthey are what the table already carries and what the legend already shows:\nan index is a fourth place the column order is written down and the first\none to go stale when somebody moves a column.\n\n**A combination chart is one scale, and that is the honest half of it.**\nBoth marks are measured against the same domain, so a line here says\nsomething comparable to the columns beside it. The usual reason to reach\nfor a combination chart is the other thing, a count against a percentage on\na second axis, and that is deliberately not this: two scales on one frame\nlet the author put any two shapes in any relation by choosing the ranges,\nand the reader has no way to see it happening.\n\nA line among columns still measures from zero, because the columns do and\nthey share the axis.",
+              "description": "Which series are drawn as a line instead of as columns, by name.\n\nSeparated by whitespace or commas and matched against the column headings\nthe table gives, so a chart says `lines=\"Margin\"` rather than counting\ncolumns. Names because they are what the table already carries and what the\nlegend already shows: an index is a fourth place the column order is\nwritten down and the first one to go stale when somebody moves a column.\n\n**This says which mark a series takes and nothing about which scale it is\nmeasured on.** Named here alone, a line shares the columns' domain, so it\nsays something comparable to the columns beside it.\n\nThe other half of a combination chart, a count against a percentage on a\nscale of its own, is `secondary`, which is a separate property because it\nis a separate question and because the two compose: `with-a-second-axis`\nships naming one series in both. The argument for why a second scale is opt\nin, and why setting it labels both axes, is written there.\n\nA line among columns measures from zero, because the columns do and they\nshare the axis. So does a line on the second scale, which is that scale's\nown rule rather than this one's.",
               "fieldName": "lines"
             },
             {
@@ -5706,7 +5782,7 @@
               "type": {
                 "text": "string | undefined"
               },
-              "description": "Which series are measured against a scale of their own, by name.\n\nSpace separated and matched the way `lines` is, against the column headings\nthe table gives. Opt in: absent, every series shares one domain, which is\nwhat makes a chart comparable and is the right default.\n\n**Two scales on one frame let an author put any two shapes in any relation\nby choosing the ranges, and a reader cannot see it happening.** That is not\na caveat, it is what the feature does: a line that crosses the columns\ntwice and a line that never touches them can be the same two series drawn\nagainst different ranges. It earns its place when the two quantities are\ngenuinely incomparable, a count against a percentage, and it is a way to\nmislead in every other case.\n\n**So it draws its axes**, and that is not optional here. The chart renders\nno value axis at all when there is one scale, because the columns are\nmeasured against each other and a reader needs no numbers to do that. With\ntwo, a reader has no way of knowing there are two, let alone which series\nis on which, so both scales are labeled the moment this is set. An\nunlabeled second axis is the deceptive case rather than the tidy one.\n\nThe grid stays on the primary axis, since a rule measured against two\nscales at once is a rule that means nothing. The tooltip is unaffected: it\nhas always shown every column's own number, which is the reader's way out\nof any scale question the picture raises.",
+              "description": "Which series are measured against a scale of their own, by name.\n\nSeparated and matched the way `lines` is, against the column headings the\ntable gives. Opt in: absent, every series shares one domain, which is what\nmakes a chart comparable and is the right default.\n\n**The scale, and `lines` is the mark.** The two are separate properties\nbecause they answer separate questions and a series usually wants both:\na percentage beside a count is drawn as a line *and* measured on its own\naxis, which is what `with-a-second-axis` writes out. Neither implies the\nother, so a series can be a line on the shared scale and a column can have\na scale to itself.\n\n**Two scales on one frame let an author put any two shapes in any relation\nby choosing the ranges, and a reader cannot see it happening.** That is not\na caveat, it is what the feature does: a line that crosses the columns\ntwice and a line that never touches them can be the same two series drawn\nagainst different ranges. It earns its place when the two quantities are\ngenuinely incomparable, a count against a percentage, and it is a way to\nmislead in every other case.\n\n**So it draws its axes**, and that is not optional here. The chart renders\nno value axis at all when there is one scale, because the columns are\nmeasured against each other and a reader needs no numbers to do that. With\ntwo, a reader has no way of knowing there are two, let alone which series\nis on which, so both scales are labeled the moment this is set. An\nunlabeled second axis is the deceptive case rather than the tidy one.\n\nThe grid stays on the primary axis, since a rule measured against two\nscales at once is a rule that means nothing. The tooltip is unaffected: it\nhas always shown every column's own number, which is the reader's way out\nof any scale question the picture raises.",
               "fieldName": "secondary"
             },
             {
@@ -5750,7 +5826,7 @@
           "helix": {
             "category": "charts",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/bar-chart",
             "aliases": [
               "Column Chart",
@@ -32925,9 +33001,8 @@
               "type": {
                 "text": "'large' | 'none' | 'small' | undefined"
               },
-              "description": "How much is left open in the middle.\n\nAbsent is a ring with room for a total in it. `small` and `large` move the\nhole without moving the outer edge, so a chart keeps its footprint.\n\n**`none` is a pie**, and it is the same drawing rather than another one:\nthe radius follows the thickness, so the inner edge reaching the center is\nwhat closing the hole means. A pie reads less accurately than a ring, angle\nbeing harder to judge than length, but it is not *misleading* the way a bar\nmeasured from anything but zero is, which is why this is a value here and\nthe bar chart's baseline is not a property at all.\n\n**Geometry rather than a CSS hook.** The dash arithmetic needs the\ncircumference, which needs the radius, and reading a custom property means\n`getComputedStyle`, which is client-only: a server would draw a different\nring than the client. A plot's proportions are markup for the same reason\n`curve` is.",
-              "attribute": "hole",
-              "reflects": true
+              "description": "How much is left open in the middle.\n\nAbsent is a ring with room for a total in it. `small` and `large` move the\nhole without moving the outer edge, so a chart keeps its footprint.\n\n**`none` is a pie**, and it is the same drawing rather than another one:\nthe radius follows the thickness, so the inner edge reaching the center is\nwhat closing the hole means. A pie reads less accurately than a ring, angle\nbeing harder to judge than length, but it is not *misleading* the way a bar\nmeasured from anything but zero is, which is why this is a value here and\nthe bar chart's baseline is not a property at all.\n\n**Geometry rather than a CSS hook.** The dash arithmetic needs the\ncircumference, which needs the radius, and reading a custom property means\n`getComputedStyle`, which is client-only: a server would draw a different\nring than the client. A plot's proportions are markup for the same reason\n`curve` is.\n\n**And so it does not reflect**, which is the same argument read forward. No\nselector on either tier asks about it and none can want to: everything the\nthickness decides is arithmetic done here and published as\n`--donut-chart-stroke`, which is a number a rule can do sums with where the\nword is not. Reflected, it wrote a value onto every host a script had set\nit on for nothing to read. `sweep` beside it is the converse and reflects,\nbecause three rules select on it.",
+              "attribute": "hole"
             },
             {
               "kind": "field",
@@ -33168,6 +33243,44 @@
                 "module": "src/mixins/mixin-chart-source/mixin-chart-source.ts"
               }
             },
+            {
+              "kind": "field",
+              "name": "plottedColumns",
+              "type": {
+                "text": "number[]"
+              },
+              "description": "Which cells of a row hold numbers, by their place in it, in table order.\n\nThe same test `readSeries` applies when it drops a column of notes: a\ncolumn is a series where any row parses, so a series survives one blank\ncell and a column of words is never one.",
+              "readonly": true,
+              "inheritedFrom": {
+                "name": "MixinChartSource",
+                "module": "src/mixins/mixin-chart-source/mixin-chart-source.ts"
+              }
+            },
+            {
+              "kind": "method",
+              "name": "seriesOf",
+              "return": {
+                "type": {
+                  "text": "number | undefined"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "cell",
+                  "type": {
+                    "text": "number"
+                  }
+                }
+              ],
+              "description": "The palette slot the cell at this place in a row is drawn in.\n\n**A cell's place in its row is not its series' depth, and the tooltip\nspent a while assuming it was.** `readSeries` drops a column nothing\nparses and `readRows` keeps it, so one column of notes among the figures\nmoves every column after it one color along in the bubble: a row reading\n`Referral 1,080` wearing series three's green beside a legend that says\nseries three is something else, which is the one failure the dot exists\nto prevent.\n\nOverridden where a chart reads the table some other way. `ScatterChart`\nsplits the first plotted column off as the measure across, so its first\n*plotted* series is this table's second numeric column.",
+              "inheritedFrom": {
+                "name": "MixinChartSource",
+                "module": "src/mixins/mixin-chart-source/mixin-chart-source.ts"
+              },
+              "type": {
+                "text": "seriesOf(cell: number) => number | undefined"
+              }
+            },
             {
               "kind": "field",
               "name": "readings",
@@ -33512,7 +33625,7 @@
               "type": {
                 "text": "'large' | 'none' | 'small' | undefined"
               },
-              "description": "How much is left open in the middle.\n\nAbsent is a ring with room for a total in it. `small` and `large` move the\nhole without moving the outer edge, so a chart keeps its footprint.\n\n**`none` is a pie**, and it is the same drawing rather than another one:\nthe radius follows the thickness, so the inner edge reaching the center is\nwhat closing the hole means. A pie reads less accurately than a ring, angle\nbeing harder to judge than length, but it is not *misleading* the way a bar\nmeasured from anything but zero is, which is why this is a value here and\nthe bar chart's baseline is not a property at all.\n\n**Geometry rather than a CSS hook.** The dash arithmetic needs the\ncircumference, which needs the radius, and reading a custom property means\n`getComputedStyle`, which is client-only: a server would draw a different\nring than the client. A plot's proportions are markup for the same reason\n`curve` is.",
+              "description": "How much is left open in the middle.\n\nAbsent is a ring with room for a total in it. `small` and `large` move the\nhole without moving the outer edge, so a chart keeps its footprint.\n\n**`none` is a pie**, and it is the same drawing rather than another one:\nthe radius follows the thickness, so the inner edge reaching the center is\nwhat closing the hole means. A pie reads less accurately than a ring, angle\nbeing harder to judge than length, but it is not *misleading* the way a bar\nmeasured from anything but zero is, which is why this is a value here and\nthe bar chart's baseline is not a property at all.\n\n**Geometry rather than a CSS hook.** The dash arithmetic needs the\ncircumference, which needs the radius, and reading a custom property means\n`getComputedStyle`, which is client-only: a server would draw a different\nring than the client. A plot's proportions are markup for the same reason\n`curve` is.\n\n**And so it does not reflect**, which is the same argument read forward. No\nselector on either tier asks about it and none can want to: everything the\nthickness decides is arithmetic done here and published as\n`--donut-chart-stroke`, which is a number a rule can do sums with where the\nword is not. Reflected, it wrote a value onto every host a script had set\nit on for nothing to read. `sweep` beside it is the converse and reflects,\nbecause three rules select on it.",
               "fieldName": "hole"
             },
             {
@@ -33564,7 +33677,7 @@
           "helix": {
             "category": "charts",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/donut-chart",
             "aliases": [
               "Pie Chart",
@@ -43212,6 +43325,44 @@
                 "module": "src/mixins/mixin-chart-source/mixin-chart-source.ts"
               }
             },
+            {
+              "kind": "field",
+              "name": "plottedColumns",
+              "type": {
+                "text": "number[]"
+              },
+              "description": "Which cells of a row hold numbers, by their place in it, in table order.\n\nThe same test `readSeries` applies when it drops a column of notes: a\ncolumn is a series where any row parses, so a series survives one blank\ncell and a column of words is never one.",
+              "readonly": true,
+              "inheritedFrom": {
+                "name": "MixinChartSource",
+                "module": "src/mixins/mixin-chart-source/mixin-chart-source.ts"
+              }
+            },
+            {
+              "kind": "method",
+              "name": "seriesOf",
+              "return": {
+                "type": {
+                  "text": "number | undefined"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "cell",
+                  "type": {
+                    "text": "number"
+                  }
+                }
+              ],
+              "description": "The palette slot the cell at this place in a row is drawn in.\n\n**A cell's place in its row is not its series' depth, and the tooltip\nspent a while assuming it was.** `readSeries` drops a column nothing\nparses and `readRows` keeps it, so one column of notes among the figures\nmoves every column after it one color along in the bubble: a row reading\n`Referral 1,080` wearing series three's green beside a legend that says\nseries three is something else, which is the one failure the dot exists\nto prevent.\n\nOverridden where a chart reads the table some other way. `ScatterChart`\nsplits the first plotted column off as the measure across, so its first\n*plotted* series is this table's second numeric column.",
+              "inheritedFrom": {
+                "name": "MixinChartSource",
+                "module": "src/mixins/mixin-chart-source/mixin-chart-source.ts"
+              },
+              "type": {
+                "text": "seriesOf(cell: number) => number | undefined"
+              }
+            },
             {
               "kind": "field",
               "name": "readings",
@@ -48838,7 +48989,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "A legend is a list, so it is a list: not part of a chart, and shared by\nwhichever of them needs one. It takes its entries from the same table the\nchart reads, through `for`, so the two cannot disagree.\n\n`entries` picks which way to read that table. `series` is one entry per data\ncolumn, named by the header row, which is a line or a bar chart.\n`categories` is one entry per body row, which is a donut: its slices are the\nrows and it has no axis to write their names along.\n\n**The table is resolved on the client and there is no server pass.**",
+          "description": "A legend is a list, so it is a list: not part of a chart, and shared by\nwhichever of them needs one. It takes its entries from the same table the\nchart reads, through `for`, so the two cannot disagree.\n\n`entries` picks which way to read that table. `series` is one entry per data\ncolumn, named by the header row, which is a line or a bar chart.\n`categories` is one entry per body row, which is a donut: its slices are the\nrows and it has no axis to write their names along. `measures` drops the\nfirst data column, which is a scatter.\n\n**The table is resolved on the client and there is no server pass.**",
           "name": "HelixHeadlessLegend",
           "cssParts": [
             {
@@ -48863,9 +49014,9 @@
               "kind": "field",
               "name": "entries",
               "type": {
-                "text": "'categories' | 'series' | undefined"
+                "text": "'categories' | 'measures' | 'series' | undefined"
               },
-              "description": "Which way to read the table.\n\nAbsent is `series`, one entry per data column. `categories` reads one entry\nper body row instead, for a donut, whose slices are the rows.",
+              "description": "Which way to read the table.\n\nAbsent is `series`, one entry per data column. `categories` reads one entry\nper body row instead, for a donut, whose slices are the rows.\n\n**`measures` is `series` without the first column, and it is for a\nscatter.** That chart reads its first numeric column as the measure\n*across*, so its first plotted series is the table's second and everything\na legend beside it named was one color out: the across column wearing the\ncolor of the first series drawn, and each real series wearing the next\none's. The across gets no entry rather than a shifted one, because it is an\naxis and a scatter already writes its name at the end of the scale under\nthe plot.\n\nA legend cannot ask the chart which of these it is, `for` naming the table\nthey share and not each other, so the consumer says it. That is the same\nshape `categories` already has.",
               "attribute": "entries",
               "reflects": true
             },
@@ -49226,9 +49377,9 @@
             {
               "name": "entries",
               "type": {
-                "text": "'categories' | 'series' | undefined"
+                "text": "'categories' | 'measures' | 'series' | undefined"
               },
-              "description": "Which way to read the table.\n\nAbsent is `series`, one entry per data column. `categories` reads one entry\nper body row instead, for a donut, whose slices are the rows.",
+              "description": "Which way to read the table.\n\nAbsent is `series`, one entry per data column. `categories` reads one entry\nper body row instead, for a donut, whose slices are the rows.\n\n**`measures` is `series` without the first column, and it is for a\nscatter.** That chart reads its first numeric column as the measure\n*across*, so its first plotted series is the table's second and everything\na legend beside it named was one color out: the across column wearing the\ncolor of the first series drawn, and each real series wearing the next\none's. The across gets no entry rather than a shifted one, because it is an\naxis and a scatter already writes its name at the end of the scale under\nthe plot.\n\nA legend cannot ask the chart which of these it is, `for` naming the table\nthey share and not each other, so the consumer says it. That is the same\nshape `categories` already has.",
               "fieldName": "entries"
             },
             {
@@ -49325,6 +49476,16 @@
           "kind": "class",
           "description": "The chart for a shape rather than for a quantity, which is what decides the\none thing a bar chart is not allowed to do.\n\n**It measures from its own range and not from zero, deliberately.** `BarChart`\nrefuses that switch because a bar's length *is* its value, so a baseline\nanywhere else makes the lengths proportional to nothing. A line claims no\nsuch thing: it says where the readings went, and forcing zero into the range\nof a series that moves between 980 and 1020 flattens the entire shape into a\nrule across the top of the box. The two rules are opposite because the two\ncharts answer opposite questions, and `zero` is here for the case where the\ndistance from nothing is the point.\n\n**One scale across every series**, the same as the bar chart, because two\nseries drawn to different scales are two charts sharing a picture.\n\n**Not the chart for a total made of parts.** `area` washes each series from\nthe floor on its own, so they overlap; `Area Chart` stacks them, so the top\nedge is the total and each band is a share. A line chart answers how each\nseries moved, an area chart how the whole is made up.\n\n**The labels are HTML beside the drawing rather than `<text>` inside it**, for\nthe reason `BarChart` records: an `<svg>` that fills its box scales its type\nwith everything else, the same `font-size` arriving at 10px in a narrow chart\nand 43px in a wide one, and there is no non-scaling-font to answer it the way\n`vector-effect` answers strokes.\n\nThe table is the accessible representation and this drawing is `aria-hidden`.\nA reader who wants the numbers gets the numbers, not a described picture.",
           "name": "HelixHeadlessLineChart",
+          "cssProperties": [
+            {
+              "description": "Where a series' last reading sits horizontally, as a percentage. Written by the component.",
+              "name": "--chart-terminus-x"
+            },
+            {
+              "description": "Where a series' last reading sits vertically, as a percentage. Written by the component.",
+              "name": "--chart-terminus-y"
+            }
+          ],
           "cssParts": [
             {
               "description": "The wash under one line, where `area` is set.",
@@ -49492,7 +49653,7 @@
               "type": {
                 "text": "'none' | 'ring' | 'square' | 'triangle' | undefined"
               },
-              "description": "The shape of the mark on each series' last reading.\n\nAbsent is a dot, and absent rather than defaulted because a reflecting\nproperty with a default writes its attribute onto a host the consumer\nrendered, which React reports as a hydration mismatch.\n\n**One per series, in a column at the far edge**, because every series here\nshares an x-axis and therefore ends at the same reading. That column is the\nuseful thing: it is where a reader looks for \"and what is it now\", which is\nthe question a sparkline's single mark answers too.\n\n`none` lets the lines stop on their own, which suits a chart read for its\nshape rather than for where it finished. The shapes come from\n`helix/styled/src/shared/chart/terminus.css`, the same sheet `Sparkline` takes, so\nthe set is identical wherever one appears.\n\n`ring` is the one that asks something of the drawing. It leaves a hole and a\nline ends at the reading, which is the hole's center, so the `<svg>` is\nmasked with one disc per series and every stroke stops at its own ring's\ninner edge. `mask-composite: intersect` is what makes N holes out of N\nlayers; a single `mask-image` would only ever cut the last one.",
+              "description": "The shape of the mark on each series' last reading.\n\nAbsent is a dot, and absent rather than defaulted because a reflecting\nproperty with a default writes its attribute onto a host the consumer\nrendered, which React reports as a hydration mismatch.\n\n**One per series, in a column at the far edge**, because every series here\nshares an x-axis and therefore ends at the same reading. That column is the\nuseful thing: it is where a reader looks for \"and what is it now\", which is\nthe question a sparkline's single mark answers too.\n\n`none` lets the lines stop on their own, which suits a chart read for its\nshape rather than for where it finished. `square` is the same mark with its\ncorners, for a drawing whose neighbors are square, the columns of a table\nbeside it for instance. `ring` lets the ground through, for a chart drawn\nover something busy. `triangle` points along the axis and reads as \"and\nonward\" rather than as a second claim about the data.\n\nThe shapes come from\n`helix/styled/src/shared/chart/terminus.css`, the same sheet `Sparkline` takes, so\nthe set is identical wherever one appears. **Which is why every value is\nnamed here.** `Sparkline` shipped `square` implemented, drawn, asserted and\nundocumented until the cohort before this one; this family reads the same\nfour out of the same sheet and had left two of them unwritten, so the\nfinding arrived twice. A shared vocabulary wants naming at each door into\nit, because a reader arrives at one door and not at the set.\n\n`ring` is the one that asks something of the drawing. It leaves a hole and a\nline ends at the reading, which is the hole's center, so the `<svg>` is\nmasked with one disc per series and every stroke stops at its own ring's\ninner edge. `mask-composite: intersect` is what makes N holes out of N\nlayers; a single `mask-image` would only ever cut the last one.",
               "attribute": "terminus",
               "reflects": true
             },
@@ -49845,6 +50006,44 @@
                 "module": "src/mixins/mixin-chart-source/mixin-chart-source.ts"
               }
             },
+            {
+              "kind": "field",
+              "name": "plottedColumns",
+              "type": {
+                "text": "number[]"
+              },
+              "description": "Which cells of a row hold numbers, by their place in it, in table order.\n\nThe same test `readSeries` applies when it drops a column of notes: a\ncolumn is a series where any row parses, so a series survives one blank\ncell and a column of words is never one.",
+              "readonly": true,
+              "inheritedFrom": {
+                "name": "MixinChartSource",
+                "module": "src/mixins/mixin-chart-source/mixin-chart-source.ts"
+              }
+            },
+            {
+              "kind": "method",
+              "name": "seriesOf",
+              "return": {
+                "type": {
+                  "text": "number | undefined"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "cell",
+                  "type": {
+                    "text": "number"
+                  }
+                }
+              ],
+              "description": "The palette slot the cell at this place in a row is drawn in.\n\n**A cell's place in its row is not its series' depth, and the tooltip\nspent a while assuming it was.** `readSeries` drops a column nothing\nparses and `readRows` keeps it, so one column of notes among the figures\nmoves every column after it one color along in the bubble: a row reading\n`Referral 1,080` wearing series three's green beside a legend that says\nseries three is something else, which is the one failure the dot exists\nto prevent.\n\nOverridden where a chart reads the table some other way. `ScatterChart`\nsplits the first plotted column off as the measure across, so its first\n*plotted* series is this table's second numeric column.",
+              "inheritedFrom": {
+                "name": "MixinChartSource",
+                "module": "src/mixins/mixin-chart-source/mixin-chart-source.ts"
+              },
+              "type": {
+                "text": "seriesOf(cell: number) => number | undefined"
+              }
+            },
             {
               "kind": "field",
               "name": "readings",
@@ -50214,7 +50413,7 @@
               "type": {
                 "text": "'none' | 'ring' | 'square' | 'triangle' | undefined"
               },
-              "description": "The shape of the mark on each series' last reading.\n\nAbsent is a dot, and absent rather than defaulted because a reflecting\nproperty with a default writes its attribute onto a host the consumer\nrendered, which React reports as a hydration mismatch.\n\n**One per series, in a column at the far edge**, because every series here\nshares an x-axis and therefore ends at the same reading. That column is the\nuseful thing: it is where a reader looks for \"and what is it now\", which is\nthe question a sparkline's single mark answers too.\n\n`none` lets the lines stop on their own, which suits a chart read for its\nshape rather than for where it finished. The shapes come from\n`helix/styled/src/shared/chart/terminus.css`, the same sheet `Sparkline` takes, so\nthe set is identical wherever one appears.\n\n`ring` is the one that asks something of the drawing. It leaves a hole and a\nline ends at the reading, which is the hole's center, so the `<svg>` is\nmasked with one disc per series and every stroke stops at its own ring's\ninner edge. `mask-composite: intersect` is what makes N holes out of N\nlayers; a single `mask-image` would only ever cut the last one.",
+              "description": "The shape of the mark on each series' last reading.\n\nAbsent is a dot, and absent rather than defaulted because a reflecting\nproperty with a default writes its attribute onto a host the consumer\nrendered, which React reports as a hydration mismatch.\n\n**One per series, in a column at the far edge**, because every series here\nshares an x-axis and therefore ends at the same reading. That column is the\nuseful thing: it is where a reader looks for \"and what is it now\", which is\nthe question a sparkline's single mark answers too.\n\n`none` lets the lines stop on their own, which suits a chart read for its\nshape rather than for where it finished. `square` is the same mark with its\ncorners, for a drawing whose neighbors are square, the columns of a table\nbeside it for instance. `ring` lets the ground through, for a chart drawn\nover something busy. `triangle` points along the axis and reads as \"and\nonward\" rather than as a second claim about the data.\n\nThe shapes come from\n`helix/styled/src/shared/chart/terminus.css`, the same sheet `Sparkline` takes, so\nthe set is identical wherever one appears. **Which is why every value is\nnamed here.** `Sparkline` shipped `square` implemented, drawn, asserted and\nundocumented until the cohort before this one; this family reads the same\nfour out of the same sheet and had left two of them unwritten, so the\nfinding arrived twice. A shared vocabulary wants naming at each door into\nit, because a reader arrives at one door and not at the set.\n\n`ring` is the one that asks something of the drawing. It leaves a hole and a\nline ends at the reading, which is the hole's center, so the `<svg>` is\nmasked with one disc per series and every stroke stops at its own ring's\ninner edge. `mask-composite: intersect` is what makes N holes out of N\nlayers; a single `mask-image` would only ever cut the last one.",
               "fieldName": "terminus"
             },
             {
@@ -50267,7 +50466,7 @@
           "helix": {
             "category": "charts",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/line-chart",
             "aliases": [
               "Time Series",
@@ -73434,6 +73633,31 @@
               "default": "undefined",
               "description": "The point a pointer is resting nearest, which the tooltip sits on."
             },
+            {
+              "kind": "method",
+              "name": "seriesOf",
+              "return": {
+                "type": {
+                  "text": "number | undefined"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "cell",
+                  "type": {
+                    "text": "number"
+                  }
+                }
+              ],
+              "description": "The palette slot a cell of a row is drawn in, which here is shifted by one.\n\n**A scatter's first plotted series is the table's *second* numeric\ncolumn**, the first having been split off as the measure across. So the\nmixin's answer, which is right for a chart whose columns are its series in\norder, is one too high on every column here and names a color for the\nacross, which is drawn in none. Left at that, the bubble painted the across\ncolumn in series one, the color the points themselves are drawn in, and\ngave the series actually plotted series two.\n\nThe across gets no dot at all rather than a shifted one. It is an axis and\nnot a series: it has a scale under the plot with its name at the end of it,\nwhich is where a reader is told what it is.",
+              "inheritedFrom": {
+                "name": "MixinChartSource",
+                "module": "src/mixins/mixin-chart-source/mixin-chart-source.ts"
+              },
+              "type": {
+                "text": "seriesOf(cell: number) => number | undefined"
+              }
+            },
             {
               "kind": "field",
               "name": "rulesX",
@@ -73628,6 +73852,19 @@
                 "module": "src/mixins/mixin-chart-source/mixin-chart-source.ts"
               }
             },
+            {
+              "kind": "field",
+              "name": "plottedColumns",
+              "type": {
+                "text": "number[]"
+              },
+              "description": "Which cells of a row hold numbers, by their place in it, in table order.\n\nThe same test `readSeries` applies when it drops a column of notes: a\ncolumn is a series where any row parses, so a series survives one blank\ncell and a column of words is never one.",
+              "readonly": true,
+              "inheritedFrom": {
+                "name": "MixinChartSource",
+                "module": "src/mixins/mixin-chart-source/mixin-chart-source.ts"
+              }
+            },
             {
               "kind": "field",
               "name": "readings",
@@ -74034,7 +74271,7 @@
           "helix": {
             "category": "charts",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/scatter-chart",
             "aliases": [
               "Scatter Plot",

package/dist/area-chart/root/area-chart-root.d.ts

@@ -34,12 +34,28 @@ declare const HelixHeadlessAreaChart_base: typeof HelixElement & (new (...args:
  * else draws every part in proportion to nothing. `LineChart` measures from its
  * own range because a line claims a position; a band claims an amount.
  *
+ * **And so it is not a streamgraph**, which is the near neighbor to name.
+ * A streamgraph moves its baseline to center the bands and reads as a river; it
+ * is a real form and it is the one thing the rule above refuses, so this
+ * carries no alias for it. What it has instead is `share`, which answers the
+ * question a streamgraph is usually reached for, how the composition changed,
+ * without giving up a floor a reader can measure against.
+ *
  * **Straight between readings unless asked otherwise.** A band's top edge is a
  * sum, and a curve fitted through one sum can pass under the curve fitted
  * through the sum beneath it, so a smoothed stack can draw a part as less than
  * nothing between two readings. Straight segments between ordered points stay
  * ordered. `curve="smooth"` is there for a stack that is read as a shape.
  *
+ * `curve="step"` falls on the safe side of that argument rather than being
+ * unanswered by it, and it is worth saying which side because a reader cannot
+ * tell from the argument alone. A step takes no value the readings do not have:
+ * it holds one, jumps at the midpoint, and holds the next. So two stepped edges
+ * that are ordered at every reading are ordered everywhere between them, which
+ * is what `straight` is chosen for. It is the curve for a quantity that changes
+ * at a moment rather than across an interval, a headcount or a price, where a
+ * sloped edge claims a gradual change nothing measured.
+ *
  * **`share` draws each reading as a hundred percent**, so the bands are the
  * parts' shares and the top edge is flat. It answers "which part grew" where
  * the default answers "did the whole grow".
@@ -56,9 +72,9 @@ declare const HelixHeadlessAreaChart_base: typeof HelixElement & (new (...args:
  * nothing, and a band that folded under its neighbor would say it was.
  *
  * @since 0.1.0
- * @status experimental
+ * @status stable
  * @category charts
- * @aliases Stacked Area Chart, Composition Chart, Stream Chart
+ * @aliases Stacked Area Chart, Composition Chart, Banded Chart
  * @documentation https://fusion.dev/helix/components/area-chart
  *
  * @csspart area - One part's band.
@@ -92,9 +108,13 @@ export declare class HelixHeadlessAreaChart extends HelixHeadlessAreaChart_base
     /**
      * How a band's edge gets from one reading to the next.
      *
-     * Absent is `straight`, for the reason the class doc gives, and absent rather
-     * than defaulted because a reflecting property with a default writes its
-     * attribute onto every host, including the ones nobody configured.
+     * Three values, and the class doc argues for each: `straight` is absent and
+     * is the default, `smooth` is for a stack read as a shape and is the one that
+     * can draw a part as less than nothing, `step` is for a quantity that changes
+     * at a moment and is ordered the way `straight` is.
+     *
+     * Absent rather than defaulted because a reflecting property with a default
+     * writes its attribute onto every host, including the ones nobody configured.
      */
     curve?: Curve;
     /**

package/dist/area-chart/root/area-chart-root.js

@@ -26,8 +26,7 @@ let HelixHeadlessAreaChart = class HelixHeadlessAreaChart extends MixinChartSour
     }
     get stack() {
         const rows = this.sourceRows;
-        const width = Math.max(0, ...rows.map((row) => row.cells.length));
-        const columns = Array.from({ length: width }, (_, column) => column).filter((column) => rows.some((row) => row.cells[column]?.value !== undefined));
+        const columns = this.plottedColumns;
         const values = columns.map((column) => rows.map((row) => {
             const value = row.cells[column]?.value ?? 0;
             if (value < 0) {
@@ -185,7 +184,7 @@ let HelixHeadlessAreaChart = class HelixHeadlessAreaChart extends MixinChartSour
             placement: 'top',
             x: `${at * slot + slot / 2}%`,
             y: `${y(stack.layers.at(-1)?.[at] ?? 0)}%`,
-        });
+        }, (cell) => this.seriesOf(cell));
     }
 };
 __decorate([