@fusion.dev/helix-headless 0.96.0 → 0.97.0

package/custom-elements.json

@@ -2348,7 +2348,7 @@
               "kind": "field",
               "name": "curve",
               "type": {
-                "text": "Curve | undefined"
+                "text": "'smooth' | 'step' | 'straight' | undefined"
               },
               "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.\nThe resting value therefore lives in the render, as `curve ?? 'straight'`.\n\n**`LineChart` and `Sparkline` rest at `smooth` and are not disagreeing.** A\nline claims a position, so the bounded invention a monotone cubic makes is\na reading aid and costs nothing. A band claims an amount, and two sums\nsmoothed independently can cross, so the same aid here draws a part as less\nthan nothing. Same axis, different mark, different resting value.",
               "attribute": "curve",
@@ -3134,7 +3134,7 @@
             {
               "name": "curve",
               "type": {
-                "text": "Curve | undefined"
+                "text": "'smooth' | 'step' | 'straight' | undefined"
               },
               "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.\nThe resting value therefore lives in the render, as `curve ?? 'straight'`.\n\n**`LineChart` and `Sparkline` rest at `smooth` and are not disagreeing.** A\nline claims a position, so the bounded invention a monotone cubic makes is\na reading aid and costs nothing. A band claims an amount, and two sums\nsmoothed independently can cross, so the same aid here draws a part as less\nthan nothing. Same axis, different mark, different resting value.",
               "fieldName": "curve"
@@ -17285,7 +17285,7 @@
               "kind": "field",
               "name": "format",
               "type": {
-                "text": "ColorFormat | undefined"
+                "text": "'hex' | 'hsl' | 'rgb' | undefined"
               },
               "description": "The syntax the value is written in: `hex`, `rgb` or `hsl`.\n\n**Undefaulted, because it reflects.** The two together stamp an attribute\nonto every host anybody renders, including the ones nobody configured: the\nserver writes `format=\"hex\"` on every color input on the page, and React,\nholding no such prop, reports a hydration mismatch for each one.\n`helix component`'s `reflected-defaults` holds it. Hex is still what an unset one\nwrites; the resting arrangement is the attribute's absence rather than a\nvalue spelled out.",
               "attribute": "format",
@@ -18631,7 +18631,7 @@
             {
               "name": "format",
               "type": {
-                "text": "ColorFormat | undefined"
+                "text": "'hex' | 'hsl' | 'rgb' | undefined"
               },
               "description": "The syntax the value is written in: `hex`, `rgb` or `hsl`.\n\n**Undefaulted, because it reflects.** The two together stamp an attribute\nonto every host anybody renders, including the ones nobody configured: the\nserver writes `format=\"hex\"` on every color input on the page, and React,\nholding no such prop, reports a hydration mismatch for each one.\n`helix component`'s `reflected-defaults` holds it. Hex is still what an unset one\nwrites; the resting arrangement is the attribute's absence rather than a\nvalue spelled out.",
               "fieldName": "format"
@@ -19071,7 +19071,7 @@
               "kind": "field",
               "name": "format",
               "type": {
-                "text": "ColorFormat | undefined"
+                "text": "'hex' | 'hsl' | 'rgb' | undefined"
               },
               "description": "The syntax the value is written in: `hex`, `rgb` or `hsl`.\n\nOnly what is written. Everything is read whatever this says, so a picker on\n`hex` still takes an `rgb()` handed to it and stores the hex for it.",
               "attribute": "format",
@@ -20126,7 +20126,7 @@
             {
               "name": "format",
               "type": {
-                "text": "ColorFormat | undefined"
+                "text": "'hex' | 'hsl' | 'rgb' | undefined"
               },
               "description": "The syntax the value is written in: `hex`, `rgb` or `hsl`.\n\nOnly what is written. Everything is read whatever this says, so a picker on\n`hex` still takes an `rgb()` handed to it and stores the hex for it.",
               "fieldName": "format"
@@ -47159,7 +47159,7 @@
               "kind": "field",
               "name": "effectiveType",
               "type": {
-                "text": "InputType"
+                "text": "'email' | 'number' | 'password' | 'search' | 'tel' | 'text' | 'url'"
               },
               "privacy": "private",
               "description": "The type the real input is given, which is not always the type asked for.\n\nA revealed password is a text field for exactly as long as the reader is\nlooking at it. Reading through a getter rather than mutating `type` keeps\nthe property the consumer's: what they set is what they get back, whatever\nthe button is doing.",
@@ -47352,7 +47352,7 @@
               "kind": "field",
               "name": "type",
               "type": {
-                "text": "InputType"
+                "text": "'email' | 'number' | 'password' | 'search' | 'tel' | 'text' | 'url'"
               },
               "default": "'text'",
               "description": "What the field accepts, which decides the keyboard and the validation.\n\n**Not reflected.** Reflection exists so a selector can reach a value, and\nno stylesheet in this repository selects on `type`. Reflecting it writes\n`type=\"text\"` onto every `<helix-headless-input>` ever rendered, an\nattribute no consumer's markup has, which is the fault the area rules write\nup under `Button`'s `href`, `target` and `rel`.\n\nNothing reads it from the attribute either. The real `<input>` inside takes\nit as a property binding, which is what makes the keyboard and the\nvalidation follow.",
@@ -48318,7 +48318,7 @@
             {
               "name": "type",
               "type": {
-                "text": "InputType"
+                "text": "'email' | 'number' | 'password' | 'search' | 'tel' | 'text' | 'url'"
               },
               "default": "'text'",
               "description": "What the field accepts, which decides the keyboard and the validation.\n\n**Not reflected.** Reflection exists so a selector can reach a value, and\nno stylesheet in this repository selects on `type`. Reflecting it writes\n`type=\"text\"` onto every `<helix-headless-input>` ever rendered, an\nattribute no consumer's markup has, which is the fault the area rules write\nup under `Button`'s `href`, `target` and `rel`.\n\nNothing reads it from the attribute either. The real `<input>` inside takes\nit as a property binding, which is what makes the keyboard and the\nvalidation follow.",
@@ -49693,7 +49693,7 @@
               "kind": "field",
               "name": "curve",
               "type": {
-                "text": "Curve | undefined"
+                "text": "'smooth' | 'step' | 'straight' | undefined"
               },
               "description": "How the line gets from one reading to the next.\n\n**`smooth` is the resting curve.** A curve invents the values between two\nreadings, which is why `straight` still exists, but the invention is\nbounded: the interpolation is monotone cubic, so it never leaves the band\nthe data sets and never introduces a peak or a trough the series does not\nhave. Within that bound the smoothed line is the easier one to follow\nacross a long series, and `straight` becomes the deliberate claim.\n\n**Absent rather than defaulted on the property**, because a reflecting\nproperty with a default writes its attribute onto every host anybody\nrenders, including the ones nobody configured.\n`line-chart-root.ssr.spec.ts` asserts the host carries only what the\nconsumer wrote. The default therefore lives where the path is built, as\n`curve ?? 'smooth'`.\n\n`step` claims the opposite of both, that a reading holds until the next.\n\n**`AreaChart` rests at `straight` and is not disagreeing.** A line claims a\nposition and a stacked band claims an amount: a curve fitted through one\nsum can pass under the curve fitted through the sum beneath it, so a\nsmoothed stack can draw a part as less than nothing. There is no such edge\nhere, which is what lets a line take the reading aid.",
               "attribute": "curve",
@@ -50476,7 +50476,7 @@
             {
               "name": "curve",
               "type": {
-                "text": "Curve | undefined"
+                "text": "'smooth' | 'step' | 'straight' | undefined"
               },
               "description": "How the line gets from one reading to the next.\n\n**`smooth` is the resting curve.** A curve invents the values between two\nreadings, which is why `straight` still exists, but the invention is\nbounded: the interpolation is monotone cubic, so it never leaves the band\nthe data sets and never introduces a peak or a trough the series does not\nhave. Within that bound the smoothed line is the easier one to follow\nacross a long series, and `straight` becomes the deliberate claim.\n\n**Absent rather than defaulted on the property**, because a reflecting\nproperty with a default writes its attribute onto every host anybody\nrenders, including the ones nobody configured.\n`line-chart-root.ssr.spec.ts` asserts the host carries only what the\nconsumer wrote. The default therefore lives where the path is built, as\n`curve ?? 'smooth'`.\n\n`step` claims the opposite of both, that a reading holds until the next.\n\n**`AreaChart` rests at `straight` and is not disagreeing.** A line claims a\nposition and a stacked band claims an amount: a curve fitted through one\nsum can pass under the curve fitted through the sum beneath it, so a\nsmoothed stack can draw a part as less than nothing. There is no such edge\nhere, which is what lets a line take the reading aid.",
               "fieldName": "curve"
@@ -55547,7 +55547,7 @@
               "kind": "field",
               "name": "placement",
               "type": {
-                "text": "Placement"
+                "text": "'bottom' | 'bottom-end' | 'bottom-start' | 'left' | 'left-end' | 'left-start' | 'right' | 'right-end' | 'right-start' | 'top' | 'top-end' | 'top-start'"
               },
               "default": "'bottom-start'",
               "description": "Preferred side.\n\nIt moves if that side does not fit.",
@@ -56364,7 +56364,7 @@
             {
               "name": "placement",
               "type": {
-                "text": "Placement"
+                "text": "'bottom' | 'bottom-end' | 'bottom-start' | 'left' | 'left-end' | 'left-start' | 'right' | 'right-end' | 'right-start' | 'top' | 'top-end' | 'top-start'"
               },
               "default": "'bottom-start'",
               "description": "Preferred side.\n\nIt moves if that side does not fit.",
@@ -56610,7 +56610,7 @@
               "kind": "field",
               "name": "band",
               "type": {
-                "text": "MeterBand | undefined"
+                "text": "'fair' | 'good' | 'poor' | undefined"
               },
               "description": "The band, said outright, where the three thresholds cannot say it.\n\n**The specification's model has a shape, and it is worth knowing before\nreaching for this.** Three bands and a point mean it can express a\n*direction* in three grades, or a *target* in two, and never a target in\nthree. Measured across a grid: with `low=\"25\" high=\"50\" optimum=\"0\"` the\nreadings 5, 28 and 60 come out good, fair and poor; with `low=\"15\"\nhigh=\"25\" optimum=\"20\"` the readings 28 and 90 both come out fair, because\nfrom a middle band nothing is ever two bands away.\n\nSo a target you can miss badly in either direction has no expression in\n`low`, `high` and `optimum`, and neither has a rule that is not about\ndistance at all: 28 against a target of 20 is fine for a room's temperature\nand is not fine for a dosage, and no arrangement of thresholds knows which\none it is looking at.\n\nWritten, this wins outright and the thresholds are only for drawing the\nticks. A consumer whose rule is more than three buckets already knows the\nanswer, and asking them to encode it as thresholds so this can decode it\nagain is a worse API than letting them say it.\n\nNot reflected. Nothing selects on it: the band reaches the stylesheet as\n`data-band` on the fill, because that is the element being colored, and a\nstylesheet outside as `indicator-good`, `-fair` or `-poor` among the fill's\npart names, so reflecting here would write an attribute onto the host for\nno reader.",
               "attribute": "band"
@@ -56777,7 +56777,7 @@
               "kind": "field",
               "name": "computedBand",
               "type": {
-                "text": "MeterBand | undefined"
+                "text": "'fair' | 'good' | 'poor' | undefined"
               },
               "privacy": "private",
               "description": "Which band the reading is in, by the specification's rule.\n\n`optimum` names a point, and the band containing it is the good one. A\nreading in that band is good, one in a band beside it is fair, and one two\nbands away is poor. Undefined where nothing was declared, which is what\nkeeps an unbanded meter from being painted as good news.",
@@ -57133,7 +57133,7 @@
             {
               "name": "band",
               "type": {
-                "text": "MeterBand | undefined"
+                "text": "'fair' | 'good' | 'poor' | undefined"
               },
               "description": "The band, said outright, where the three thresholds cannot say it.\n\n**The specification's model has a shape, and it is worth knowing before\nreaching for this.** Three bands and a point mean it can express a\n*direction* in three grades, or a *target* in two, and never a target in\nthree. Measured across a grid: with `low=\"25\" high=\"50\" optimum=\"0\"` the\nreadings 5, 28 and 60 come out good, fair and poor; with `low=\"15\"\nhigh=\"25\" optimum=\"20\"` the readings 28 and 90 both come out fair, because\nfrom a middle band nothing is ever two bands away.\n\nSo a target you can miss badly in either direction has no expression in\n`low`, `high` and `optimum`, and neither has a rule that is not about\ndistance at all: 28 against a target of 20 is fine for a room's temperature\nand is not fine for a dosage, and no arrangement of thresholds knows which\none it is looking at.\n\nWritten, this wins outright and the thresholds are only for drawing the\nticks. A consumer whose rule is more than three buckets already knows the\nanswer, and asking them to encode it as thresholds so this can decode it\nagain is a worse API than letting them say it.\n\nNot reflected. Nothing selects on it: the band reaches the stylesheet as\n`data-band` on the fill, because that is the element being colored, and a\nstylesheet outside as `indicator-good`, `-fair` or `-poor` among the fill's\npart names, so reflecting here would write an attribute onto the host for\nno reader.",
               "fieldName": "band"
@@ -66793,7 +66793,7 @@
               "kind": "field",
               "name": "type",
               "type": {
-                "text": "PinType"
+                "text": "'alphanumeric' | 'numeric' | 'text'"
               },
               "default": "'numeric'",
               "description": "What a box accepts, which decides the keyboard a phone offers.\n\n`numeric` and `alphanumeric` also refuse anything else on the way in,\nbecause a code that is digits is digits: letting a letter into a box a\nreader cannot submit is a mistake they have to find and undo themselves.\n`text` refuses nothing and only trims, so it is the mode for a code with a\nhyphen in it.\n\n**`alphanumeric` is ASCII letters and digits**, which is narrower than the\nword is in general and is the right narrowness here. A code of this kind\ncomes off a keypad, an SMS or an authenticator, and none of them emit `é`;\na filter that accepted it would let through a character the service on the\nother end is going to reject. A consumer whose codes really do carry\nmarked letters wants `text`, which judges nothing.\n\n**Not reflected**: nothing selects on it, so reflecting only writes\n`type=\"numeric\"` onto every `<helix-headless-pin-input>` ever rendered, an\nattribute no consumer's markup had. The area rules carry the sentence\n\"reflect only what CSS selects on\". The real inputs take it as a binding,\nwhich is what makes the keyboard follow.",
@@ -67944,7 +67944,7 @@
             {
               "name": "type",
               "type": {
-                "text": "PinType"
+                "text": "'alphanumeric' | 'numeric' | 'text'"
               },
               "default": "'numeric'",
               "description": "What a box accepts, which decides the keyboard a phone offers.\n\n`numeric` and `alphanumeric` also refuse anything else on the way in,\nbecause a code that is digits is digits: letting a letter into a box a\nreader cannot submit is a mistake they have to find and undo themselves.\n`text` refuses nothing and only trims, so it is the mode for a code with a\nhyphen in it.\n\n**`alphanumeric` is ASCII letters and digits**, which is narrower than the\nword is in general and is the right narrowness here. A code of this kind\ncomes off a keypad, an SMS or an authenticator, and none of them emit `é`;\na filter that accepted it would let through a character the service on the\nother end is going to reject. A consumer whose codes really do carry\nmarked letters wants `text`, which judges nothing.\n\n**Not reflected**: nothing selects on it, so reflecting only writes\n`type=\"numeric\"` onto every `<helix-headless-pin-input>` ever rendered, an\nattribute no consumer's markup had. The area rules carry the sentence\n\"reflect only what CSS selects on\". The real inputs take it as a binding,\nwhich is what makes the keyboard follow.",
@@ -68200,7 +68200,7 @@
               "kind": "field",
               "name": "placement",
               "type": {
-                "text": "Placement"
+                "text": "'bottom' | 'bottom-end' | 'bottom-start' | 'left' | 'left-end' | 'left-start' | 'right' | 'right-end' | 'right-start' | 'top' | 'top-end' | 'top-start'"
               },
               "default": "'bottom-start'",
               "description": "Preferred side.\n\nIt moves if that side does not fit.",
@@ -68761,7 +68761,7 @@
             {
               "name": "placement",
               "type": {
-                "text": "Placement"
+                "text": "'bottom' | 'bottom-end' | 'bottom-start' | 'left' | 'left-end' | 'left-start' | 'right' | 'right-end' | 'right-start' | 'top' | 'top-end' | 'top-start'"
               },
               "default": "'bottom-start'",
               "description": "Preferred side.\n\nIt moves if that side does not fit.",
@@ -69503,7 +69503,7 @@
               "kind": "field",
               "name": "correction",
               "type": {
-                "text": "QrCorrection | undefined"
+                "text": "'H' | 'L' | 'M' | 'Q' | undefined"
               },
               "description": "How much of the code can be lost and still read.\n\n`M` by default, which is the level almost every code in the world uses and\ncosts about fifteen percent redundancy. `H` where a mark covers the center,\nchosen automatically when the slot is filled: it is the level that makes\ncovering safe, and a consumer who fills the slot has said what they want\nwithout having to know that.",
               "attribute": "correction"
@@ -69522,7 +69522,7 @@
               "kind": "field",
               "name": "shape",
               "type": {
-                "text": "QrStyle | undefined"
+                "text": "'dots' | 'rounded' | 'square' | undefined"
               },
               "description": "How the modules are drawn.\n\n`square` is the resting state and is written by not writing it, per the\nrule that a reflected property takes no default. It is also the only one\nthat joins runs of adjacent modules into a single subpath, which is what\nkeeps a thousand modules to a handful of nodes. `rounded` and `dots` draw\neach module on its own, because the corners are the thing being drawn and a\njoined run has none in the middle. That cost is paid only by a code that\nasks for them.\n\nA scanner reads contrast between cells, not their shape, so all three\nscan. `dots` sits a little under half a module so neighbors do not touch,\nwhich is what makes it read as dots rather than as a softened square code.",
               "attribute": "shape",
@@ -69552,7 +69552,7 @@
               "kind": "field",
               "name": "level",
               "type": {
-                "text": "QrCorrection"
+                "text": "'H' | 'L' | 'M' | 'Q'"
               },
               "privacy": "private",
               "description": "The level actually used, which the slot can raise.",
@@ -69897,7 +69897,7 @@
             {
               "name": "correction",
               "type": {
-                "text": "QrCorrection | undefined"
+                "text": "'H' | 'L' | 'M' | 'Q' | undefined"
               },
               "description": "How much of the code can be lost and still read.\n\n`M` by default, which is the level almost every code in the world uses and\ncosts about fifteen percent redundancy. `H` where a mark covers the center,\nchosen automatically when the slot is filled: it is the level that makes\ncovering safe, and a consumer who fills the slot has said what they want\nwithout having to know that.",
               "fieldName": "correction"
@@ -69914,7 +69914,7 @@
             {
               "name": "shape",
               "type": {
-                "text": "QrStyle | undefined"
+                "text": "'dots' | 'rounded' | 'square' | undefined"
               },
               "description": "How the modules are drawn.\n\n`square` is the resting state and is written by not writing it, per the\nrule that a reflected property takes no default. It is also the only one\nthat joins runs of adjacent modules into a single subpath, which is what\nkeeps a thousand modules to a handful of nodes. `rounded` and `dots` draw\neach module on its own, because the corners are the thing being drawn and a\njoined run has none in the middle. That cost is paid only by a code that\nasks for them.\n\nA scanner reads contrast between cells, not their shape, so all three\nscan. `dots` sits a little under half a module so neighbors do not touch,\nwhich is what makes it read as dots rather than as a softened square code.",
               "fieldName": "shape"
@@ -79136,7 +79136,7 @@
               "kind": "field",
               "name": "curve",
               "type": {
-                "text": "Curve | undefined"
+                "text": "'smooth' | 'step' | 'straight' | undefined"
               },
               "description": "How the line gets from one reading to the next.\n\n**`smooth` is the resting curve.** A straight segment asserts nothing about\nthe values between two readings and a curve invents them, which is why\n`straight` exists. What settles the default the other way is that the\ninvention is bounded: the interpolation is monotone cubic, so it never\nleaves the band the data sets and never introduces a peak or a trough the\nseries does not have. Within that bound the smoothed line is the easier one\nto follow across a long series, which is what the drawing is for. `straight`\nbecomes the claim a consumer makes deliberately rather than the one they get\nby saying nothing.\n\n**The property stays optional and the default lives in the render.** A\nreflecting property with a default writes its attribute onto every host\nanybody renders, including the ones nobody configured, which the SSR specs\nassert against. So the resting state is still the attribute's absence, and\n`curve ?? 'smooth'` is what reads it.\n\n`step` claims the opposite of both, that a reading holds until the next.\nBars ignore it, having no between to interpolate.\n\n**`AreaChart` rests at `straight` and is not disagreeing.** A line claims a\nposition and a stacked band claims an amount: a curve fitted through one\nsum can pass under the curve fitted through the sum beneath it, so a\nsmoothed stack can draw a part as less than nothing. There is no such edge\nhere, which is what lets a line take the reading aid.",
               "attribute": "curve",
@@ -79529,7 +79529,7 @@
             {
               "name": "curve",
               "type": {
-                "text": "Curve | undefined"
+                "text": "'smooth' | 'step' | 'straight' | undefined"
               },
               "description": "How the line gets from one reading to the next.\n\n**`smooth` is the resting curve.** A straight segment asserts nothing about\nthe values between two readings and a curve invents them, which is why\n`straight` exists. What settles the default the other way is that the\ninvention is bounded: the interpolation is monotone cubic, so it never\nleaves the band the data sets and never introduces a peak or a trough the\nseries does not have. Within that bound the smoothed line is the easier one\nto follow across a long series, which is what the drawing is for. `straight`\nbecomes the claim a consumer makes deliberately rather than the one they get\nby saying nothing.\n\n**The property stays optional and the default lives in the render.** A\nreflecting property with a default writes its attribute onto every host\nanybody renders, including the ones nobody configured, which the SSR specs\nassert against. So the resting state is still the attribute's absence, and\n`curve ?? 'smooth'` is what reads it.\n\n`step` claims the opposite of both, that a reading holds until the next.\nBars ignore it, having no between to interpolate.\n\n**`AreaChart` rests at `straight` and is not disagreeing.** A line claims a\nposition and a stacked band claims an amount: a curve fitted through one\nsum can pass under the curve fitted through the sum beneath it, so a\nsmoothed stack can draw a part as less than nothing. There is no such edge\nhere, which is what lets a line take the reading aid.",
               "fieldName": "curve"
@@ -80235,7 +80235,7 @@
               "kind": "field",
               "name": "placement",
               "type": {
-                "text": "Placement"
+                "text": "'bottom' | 'bottom-end' | 'bottom-start' | 'left' | 'left-end' | 'left-start' | 'right' | 'right-end' | 'right-start' | 'top' | 'top-end' | 'top-start'"
               },
               "default": "'top-end'",
               "description": "Which way the actions fan out. They move if that side does not fit.\n\nUp by default, because the control this hangs off is usually docked to the\nbottom of the window and there is nothing below it to fan into.",
@@ -80813,7 +80813,7 @@
             {
               "name": "placement",
               "type": {
-                "text": "Placement"
+                "text": "'bottom' | 'bottom-end' | 'bottom-start' | 'left' | 'left-end' | 'left-start' | 'right' | 'right-end' | 'right-start' | 'top' | 'top-end' | 'top-start'"
               },
               "default": "'top-end'",
               "description": "Which way the actions fan out. They move if that side does not fit.\n\nUp by default, because the control this hangs off is usually docked to the\nbottom of the window and there is nothing below it to fan into.",
@@ -99914,7 +99914,7 @@
               "kind": "field",
               "name": "placement",
               "type": {
-                "text": "Placement"
+                "text": "'bottom' | 'bottom-end' | 'bottom-start' | 'left' | 'left-end' | 'left-start' | 'right' | 'right-end' | 'right-start' | 'top' | 'top-end' | 'top-start'"
               },
               "default": "'top'",
               "description": "Preferred side.\n\nIt moves if that side does not fit.",
@@ -100687,7 +100687,7 @@
             {
               "name": "placement",
               "type": {
-                "text": "Placement"
+                "text": "'bottom' | 'bottom-end' | 'bottom-start' | 'left' | 'left-end' | 'left-start' | 'right' | 'right-end' | 'right-start' | 'top' | 'top-end' | 'top-start'"
               },
               "default": "'top'",
               "description": "Preferred side.\n\nIt moves if that side does not fit.",
@@ -101807,7 +101807,7 @@
               "kind": "field",
               "name": "placement",
               "type": {
-                "text": "Placement"
+                "text": "'bottom' | 'bottom-end' | 'bottom-start' | 'left' | 'left-end' | 'left-start' | 'right' | 'right-end' | 'right-start' | 'top' | 'top-end' | 'top-start'"
               },
               "default": "'bottom'",
               "description": "Which side of the target the panel prefers.",
@@ -102280,7 +102280,7 @@
             {
               "name": "placement",
               "type": {
-                "text": "Placement"
+                "text": "'bottom' | 'bottom-end' | 'bottom-start' | 'left' | 'left-end' | 'left-start' | 'right' | 'right-end' | 'right-start' | 'top' | 'top-end' | 'top-start'"
               },
               "default": "'bottom'",
               "description": "Which side of the target the panel prefers.",

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.96.0",
+  "version": "0.97.0",
   "license": "MIT",
   "author": "Ross Sheppard <ross.sheppard@fusion.dev>",
   "repository": {
@@ -46,13 +46,13 @@
   },
   "bugs": "https://github.com/project-fusion/fusion/issues",
   "dependencies": {
-    "@fusion.dev/helix-core": "0.96.0",
-    "@fusion.dev/helix-icons": "0.96.0",
+    "@fusion.dev/helix-core": "0.97.0",
+    "@fusion.dev/helix-icons": "0.97.0",
     "uqr": "^0.1.3"
   },
   "devDependencies": {
-    "@fusion.dev/helix-cem": "0.96.0",
-    "@fusion.dev/helix-testing": "0.96.0",
+    "@fusion.dev/helix-cem": "0.97.0",
+    "@fusion.dev/helix-testing": "0.97.0",
     "@fusion.dev/scripts": "0.0.0-dev",
     "@happy-dom/global-registrator": "^20.0.0",
     "@lit-labs/ssr": "^4.1.0",