@fusion.dev/helix 0.59.0 → 0.59.2

package/custom-elements.json

@@ -114333,7 +114333,7 @@
               "type": {
                 "text": "'segmented' | 'underlined' | undefined"
               },
-              "description": "How the row reads.\n\nUnset is a raised pill on the selected tab with nothing behind the row,\nwhich is what a set sitting inside other chrome wants. `underlined` is a\nrule under the row and a thicker one under the selected tab, for a set that\nheads a page. `segmented` puts the pill in a framed, sunken track, which\nreads as one control rather than as a row.\n\nA value describes itself rather than naming another component: `segmented`\nand `underlined` are participles reading as a pair, the way `outlined` on\nAccordion does.\n\nReflected and left unset by default, so the host carries nothing a\nconsumer's server markup does not already have.",
+              "description": "How the row reads.\n\nUnset is a raised pill on the selected tab with nothing behind the row,\nwhich is what a set sitting inside other chrome wants. `underlined` is a\nrule under the row and a thicker one under the selected tab, for a set that\nheads a page. `segmented` puts the pill in a framed, sunken track, which\nreads as one control rather than as a row.\n\nA value describes itself rather than naming another component: `segmented`\nand `underlined` are participles reading as a pair, the way `outlined` on\nAccordion does.\n\n**`segmented` is `ToggleGroup`'s track, opted into.** The two draw the same\ngroove, token for token, and the sheets already say so where the height is\nfixed. What differs is polarity, and both are right: a group of toggles is\none control, so its track is the resting state and its `separation` decides\nonly the frame around it, while a row of tabs is a row until something says\notherwise, so the track is a value here rather than the thing a value takes\naway.\n\nReflected and left unset by default, so the host carries nothing a\nconsumer's server markup does not already have.",
               "attribute": "variant",
               "reflects": true,
               "inheritedFrom": {
@@ -114828,7 +114828,7 @@
               "type": {
                 "text": "'segmented' | 'underlined' | undefined"
               },
-              "description": "How the row reads.\n\nUnset is a raised pill on the selected tab with nothing behind the row,\nwhich is what a set sitting inside other chrome wants. `underlined` is a\nrule under the row and a thicker one under the selected tab, for a set that\nheads a page. `segmented` puts the pill in a framed, sunken track, which\nreads as one control rather than as a row.\n\nA value describes itself rather than naming another component: `segmented`\nand `underlined` are participles reading as a pair, the way `outlined` on\nAccordion does.\n\nReflected and left unset by default, so the host carries nothing a\nconsumer's server markup does not already have.",
+              "description": "How the row reads.\n\nUnset is a raised pill on the selected tab with nothing behind the row,\nwhich is what a set sitting inside other chrome wants. `underlined` is a\nrule under the row and a thicker one under the selected tab, for a set that\nheads a page. `segmented` puts the pill in a framed, sunken track, which\nreads as one control rather than as a row.\n\nA value describes itself rather than naming another component: `segmented`\nand `underlined` are participles reading as a pair, the way `outlined` on\nAccordion does.\n\n**`segmented` is `ToggleGroup`'s track, opted into.** The two draw the same\ngroove, token for token, and the sheets already say so where the height is\nfixed. What differs is polarity, and both are right: a group of toggles is\none control, so its track is the resting state and its `separation` decides\nonly the frame around it, while a row of tabs is a row until something says\notherwise, so the track is a value here rather than the thing a value takes\naway.\n\nReflected and left unset by default, so the host carries nothing a\nconsumer's server markup does not already have.",
               "fieldName": "variant",
               "inheritedFrom": {
                 "name": "HelixHeadlessTabs",
@@ -124941,7 +124941,7 @@
               "type": {
                 "text": "| 'bottom-center'\n    | 'bottom-end'\n    | 'bottom-start'\n    | 'top-center'\n    | 'top-end'\n    | 'top-start' | undefined"
               },
-              "description": "Which corner or edge the stack sits at.\n\nNamed here rather than on each message, because where a page puts its\ntoasts is a fact about the page: a stack whose members disagreed about\nwhere they were would not be a stack.\n\n**Optional, and bottom-end is the absence of it.** Reflecting *and*\ndefaulting is the pair that writes onto a host: every toast region anybody\nrendered would gain a `placement=\"bottom-end\"` nobody typed, which a React\nconsumer's server markup does not have. A sheet carries the resting\narrangement in its own `:host` rule and the selectors describe only the\ndepartures, which is what `orientation` does.",
+              "description": "Which corner or edge the stack sits at.\n\nNamed here rather than on each message, because where a page puts its\ntoasts is a fact about the page: a stack whose members disagreed about\nwhere they were would not be a stack.\n\n**Six corners in one word, where `Carousel` splits the same question in\ntwo.** That family takes a placement and an alignment, and argues at its own\ndeclaration that one attribute naming both facts multiplies rather than\ncomposing. It is right there and wrong here, and the difference is the\nshape of the product. A carousel's is ragged: its `overlay` belongs to no\nedge at all, and its two groups of chrome move independently, shipping\ndifferent defaults so they do not land on each other, which is what makes\nrewriting one to move the other a real cost. A stack's is two edges by\nthree alignments, every pair real and every pair named this way by every\ntoast a reader has already met. Fusing spells the domain out and loses\nnothing; a stack has one position and takes it once.\n\n**Optional, and bottom-end is the absence of it.** Reflecting *and*\ndefaulting is the pair that writes onto a host: every toast region anybody\nrendered would gain a `placement=\"bottom-end\"` nobody typed, which a React\nconsumer's server markup does not have. A sheet carries the resting\narrangement in its own `:host` rule and the selectors describe only the\ndepartures, which is what `orientation` does.",
               "attribute": "placement",
               "reflects": true,
               "inheritedFrom": {
@@ -125360,7 +125360,7 @@
               "type": {
                 "text": "| 'bottom-center'\n    | 'bottom-end'\n    | 'bottom-start'\n    | 'top-center'\n    | 'top-end'\n    | 'top-start' | undefined"
               },
-              "description": "Which corner or edge the stack sits at.\n\nNamed here rather than on each message, because where a page puts its\ntoasts is a fact about the page: a stack whose members disagreed about\nwhere they were would not be a stack.\n\n**Optional, and bottom-end is the absence of it.** Reflecting *and*\ndefaulting is the pair that writes onto a host: every toast region anybody\nrendered would gain a `placement=\"bottom-end\"` nobody typed, which a React\nconsumer's server markup does not have. A sheet carries the resting\narrangement in its own `:host` rule and the selectors describe only the\ndepartures, which is what `orientation` does.",
+              "description": "Which corner or edge the stack sits at.\n\nNamed here rather than on each message, because where a page puts its\ntoasts is a fact about the page: a stack whose members disagreed about\nwhere they were would not be a stack.\n\n**Six corners in one word, where `Carousel` splits the same question in\ntwo.** That family takes a placement and an alignment, and argues at its own\ndeclaration that one attribute naming both facts multiplies rather than\ncomposing. It is right there and wrong here, and the difference is the\nshape of the product. A carousel's is ragged: its `overlay` belongs to no\nedge at all, and its two groups of chrome move independently, shipping\ndifferent defaults so they do not land on each other, which is what makes\nrewriting one to move the other a real cost. A stack's is two edges by\nthree alignments, every pair real and every pair named this way by every\ntoast a reader has already met. Fusing spells the domain out and loses\nnothing; a stack has one position and takes it once.\n\n**Optional, and bottom-end is the absence of it.** Reflecting *and*\ndefaulting is the pair that writes onto a host: every toast region anybody\nrendered would gain a `placement=\"bottom-end\"` nobody typed, which a React\nconsumer's server markup does not have. A sheet carries the resting\narrangement in its own `:host` rule and the selectors describe only the\ndepartures, which is what `orientation` does.",
               "fieldName": "placement",
               "inheritedFrom": {
                 "name": "HelixHeadlessToast",
@@ -125532,7 +125532,7 @@
               "type": {
                 "text": "'outlined' | 'plain' | undefined"
               },
-              "description": "How the group separates itself from the page.\n\nSeparation rather than emphasis, because what `plain` drops is the\nbackground *and* the border: the question is where the group ends, not how\nmuch ink it claims. `outlined` because the frame is a border over the\ngroup's own ground, exactly as a Card's is; the track's sunken fill stays\neither way, being a groove for the thumb to sit in rather than a way of\nbeing seen.",
+              "description": "How the group separates itself from the page.\n\nSeparation rather than emphasis, because what `plain` drops is the\nbackground *and* the border: the question is where the group ends, not how\nmuch ink it claims. `outlined` because the frame is a border over the\ngroup's own ground, exactly as a Card's is; the track's sunken fill stays\neither way, being a groove for the thumb to sit in rather than a way of\nbeing seen.\n\n**The track itself is not on this axis, and `Tabs` reaches the same one\nfrom the other side.** There it is `variant=\"segmented\"`, opted into,\nbecause a row of tabs is a row until asked; here it is the resting state,\nbecause a group of toggles is one control. Same groove, opposite polarity,\nand what decides the polarity is which reading is ordinary for the family.",
               "attribute": "separation",
               "reflects": true
             },
@@ -126514,7 +126514,7 @@
               "type": {
                 "text": "'outlined' | 'plain' | undefined"
               },
-              "description": "How the group separates itself from the page.\n\nSeparation rather than emphasis, because what `plain` drops is the\nbackground *and* the border: the question is where the group ends, not how\nmuch ink it claims. `outlined` because the frame is a border over the\ngroup's own ground, exactly as a Card's is; the track's sunken fill stays\neither way, being a groove for the thumb to sit in rather than a way of\nbeing seen.",
+              "description": "How the group separates itself from the page.\n\nSeparation rather than emphasis, because what `plain` drops is the\nbackground *and* the border: the question is where the group ends, not how\nmuch ink it claims. `outlined` because the frame is a border over the\ngroup's own ground, exactly as a Card's is; the track's sunken fill stays\neither way, being a groove for the thumb to sit in rather than a way of\nbeing seen.\n\n**The track itself is not on this axis, and `Tabs` reaches the same one\nfrom the other side.** There it is `variant=\"segmented\"`, opted into,\nbecause a row of tabs is a row until asked; here it is the resting state,\nbecause a group of toggles is one control. Same groove, opposite polarity,\nand what decides the polarity is which reading is ordinary for the family.",
               "fieldName": "separation"
             },
             {
@@ -137480,6 +137480,7 @@
                   "text": "Promise<void>"
                 }
               },
+              "description": "Into picture in picture and back, and quiet about being refused.\n\nCaught rather than `void`ed, the way `FullscreenController` catches its\nown: this is called from a click handler that discards the promise, so a\nrefusal is otherwise an unhandled rejection naming neither the element nor\nthe reason. The roster already declines to draw the button where the\nconsumer refused the feature, which leaves the refusals nothing can see\ncoming, a request without user activation and a window another document is\nalready using.",
               "inheritedFrom": {
                 "name": "HelixHeadlessVideo",
                 "module": "src/video/root/video-root.ts"

package/dist/toggle/group/toggle-group.d.ts

@@ -37,6 +37,12 @@ export declare class HelixToggleGroup extends HelixHeadlessToggleGroup {
      * group's own ground, exactly as a Card's is; the track's sunken fill stays
      * either way, being a groove for the thumb to sit in rather than a way of
      * being seen.
+     *
+     * **The track itself is not on this axis, and `Tabs` reaches the same one
+     * from the other side.** There it is `variant="segmented"`, opted into,
+     * because a row of tabs is a row until asked; here it is the resting state,
+     * because a group of toggles is one control. Same groove, opposite polarity,
+     * and what decides the polarity is which reading is ordinary for the family.
      */
     separation?: 'outlined' | 'plain';
     static styles: CSSResultGroup;

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@fusion.dev/helix",
   "description": "Styled component tier. Extends the headless tier with token-driven presentation.",
-  "version": "0.59.0",
+  "version": "0.59.2",
   "license": "MIT",
   "author": "Ross Sheppard <ross.sheppard@fusion.dev>",
   "repository": {
@@ -47,14 +47,14 @@
   },
   "bugs": "https://github.com/project-fusion/fusion/issues",
   "dependencies": {
-    "@fusion.dev/helix-core": "0.59.0",
-    "@fusion.dev/helix-headless": "0.59.0",
-    "@fusion.dev/helix-styles": "0.59.0"
+    "@fusion.dev/helix-core": "0.59.2",
+    "@fusion.dev/helix-headless": "0.59.2",
+    "@fusion.dev/helix-styles": "0.59.2"
   },
   "devDependencies": {
     "@custom-elements-manifest/analyzer": "^0.11.0",
-    "@fusion.dev/helix-cem": "0.59.0",
-    "@fusion.dev/helix-testing": "0.59.0",
+    "@fusion.dev/helix-cem": "0.59.2",
+    "@fusion.dev/helix-testing": "0.59.2",
     "@fusion.dev/scripts": "0.0.0-dev",
     "@happy-dom/global-registrator": "^20.0.0",
     "@lit-labs/ssr": "^4.1.0",

package/types/jsx.d.ts

@@ -17615,6 +17615,14 @@ A value describes itself rather than naming another component: `segmented`
 and `underlined` are participles reading as a pair, the way `outlined` on
 Accordion does.
 
+**`segmented` is `ToggleGroup`'s track, opted into.** The two draw the same
+groove, token for token, and the sheets already say so where the height is
+fixed. What differs is polarity, and both are right: a group of toggles is
+one control, so its track is the resting state and its `separation` decides
+only the frame around it, while a row of tabs is a row until something says
+otherwise, so the track is a value here rather than the thing a value takes
+away.
+
 Reflected and left unset by default, so the host carries nothing a
 consumer's server markup does not already have. */
   variant?: (HelixTabs["variant"]) | undefined;
@@ -17667,6 +17675,14 @@ A value describes itself rather than naming another component: `segmented`
 and `underlined` are participles reading as a pair, the way `outlined` on
 Accordion does.
 
+**`segmented` is `ToggleGroup`'s track, opted into.** The two draw the same
+groove, token for token, and the sheets already say so where the height is
+fixed. What differs is polarity, and both are right: a group of toggles is
+one control, so its track is the resting state and its `separation` decides
+only the frame around it, while a row of tabs is a row until something says
+otherwise, so the track is a value here rather than the thing a value takes
+away.
+
 Reflected and left unset by default, so the host carries nothing a
 consumer's server markup does not already have. */
   "prop:variant"?: (HelixTabs["variant"]) | undefined;
@@ -19116,6 +19132,18 @@ Named here rather than on each message, because where a page puts its
 toasts is a fact about the page: a stack whose members disagreed about
 where they were would not be a stack.
 
+**Six corners in one word, where `Carousel` splits the same question in
+two.** That family takes a placement and an alignment, and argues at its own
+declaration that one attribute naming both facts multiplies rather than
+composing. It is right there and wrong here, and the difference is the
+shape of the product. A carousel's is ragged: its `overlay` belongs to no
+edge at all, and its two groups of chrome move independently, shipping
+different defaults so they do not land on each other, which is what makes
+rewriting one to move the other a real cost. A stack's is two edges by
+three alignments, every pair real and every pair named this way by every
+toast a reader has already met. Fusing spells the domain out and loses
+nothing; a stack has one position and takes it once.
+
 **Optional, and bottom-end is the absence of it.** Reflecting *and*
 defaulting is the pair that writes onto a host: every toast region anybody
 rendered would gain a `placement="bottom-end"` nobody typed, which a React
@@ -19137,6 +19165,18 @@ Named here rather than on each message, because where a page puts its
 toasts is a fact about the page: a stack whose members disagreed about
 where they were would not be a stack.
 
+**Six corners in one word, where `Carousel` splits the same question in
+two.** That family takes a placement and an alignment, and argues at its own
+declaration that one attribute naming both facts multiplies rather than
+composing. It is right there and wrong here, and the difference is the
+shape of the product. A carousel's is ragged: its `overlay` belongs to no
+edge at all, and its two groups of chrome move independently, shipping
+different defaults so they do not land on each other, which is what makes
+rewriting one to move the other a real cost. A stack's is two edges by
+three alignments, every pair real and every pair named this way by every
+toast a reader has already met. Fusing spells the domain out and loses
+nothing; a stack has one position and takes it once.
+
 **Optional, and bottom-end is the absence of it.** Reflecting *and*
 defaulting is the pair that writes onto a host: every toast region anybody
 rendered would gain a `placement="bottom-end"` nobody typed, which a React
@@ -19173,7 +19213,13 @@ background *and* the border: the question is where the group ends, not how
 much ink it claims. `outlined` because the frame is a border over the
 group's own ground, exactly as a Card's is; the track's sunken fill stays
 either way, being a groove for the thumb to sit in rather than a way of
-being seen. */
+being seen.
+
+**The track itself is not on this axis, and `Tabs` reaches the same one
+from the other side.** There it is `variant="segmented"`, opted into,
+because a row of tabs is a row until asked; here it is the resting state,
+because a group of toggles is one control. Same groove, opposite polarity,
+and what decides the polarity is which reading is ordinary for the family. */
   separation?: (HelixToggleGroup["separation"]) | undefined;
   /** The value the markup declared, which is where a reset returns to. */
   "default-value"?: (HelixToggleGroup["defaultValue"]) | undefined;
@@ -19271,7 +19317,13 @@ background *and* the border: the question is where the group ends, not how
 much ink it claims. `outlined` because the frame is a border over the
 group's own ground, exactly as a Card's is; the track's sunken fill stays
 either way, being a groove for the thumb to sit in rather than a way of
-being seen. */
+being seen.
+
+**The track itself is not on this axis, and `Tabs` reaches the same one
+from the other side.** There it is `variant="segmented"`, opted into,
+because a row of tabs is a row until asked; here it is the resting state,
+because a group of toggles is one control. Same groove, opposite polarity,
+and what decides the polarity is which reading is ordinary for the family. */
   "prop:separation"?: (HelixToggleGroup["separation"]) | undefined;
   /** The value the markup declared, which is where a reset returns to. */
   "attr:default-value"?: (HelixToggleGroup["defaultValue"]) | undefined;
@@ -37523,6 +37575,14 @@ export type CustomElements = {
    * and `underlined` are participles reading as a pair, the way `outlined` on
    * Accordion does.
    *
+   * **`segmented` is `ToggleGroup`'s track, opted into.** The two draw the same
+   * groove, token for token, and the sheets already say so where the height is
+   * fixed. What differs is polarity, and both are right: a group of toggles is
+   * one control, so its track is the resting state and its `separation` decides
+   * only the frame around it, while a row of tabs is a row until something says
+   * otherwise, so the track is a value here rather than the thing a value takes
+   * away.
+   *
    * Reflected and left unset by default, so the host carries nothing a
    * consumer's server markup does not already have.
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
@@ -38948,6 +39008,18 @@ export type CustomElements = {
    * toasts is a fact about the page: a stack whose members disagreed about
    * where they were would not be a stack.
    *
+   * **Six corners in one word, where `Carousel` splits the same question in
+   * two.** That family takes a placement and an alignment, and argues at its own
+   * declaration that one attribute naming both facts multiplies rather than
+   * composing. It is right there and wrong here, and the difference is the
+   * shape of the product. A carousel's is ragged: its `overlay` belongs to no
+   * edge at all, and its two groups of chrome move independently, shipping
+   * different defaults so they do not land on each other, which is what makes
+   * rewriting one to move the other a real cost. A stack's is two edges by
+   * three alignments, every pair real and every pair named this way by every
+   * toast a reader has already met. Fusing spells the domain out and loses
+   * nothing; a stack has one position and takes it once.
+   *
    * **Optional, and bottom-end is the absence of it.** Reflecting *and*
    * defaulting is the pair that writes onto a host: every toast region anybody
    * rendered would gain a `placement="bottom-end"` nobody typed, which a React
@@ -39032,6 +39104,12 @@ export type CustomElements = {
    * group's own ground, exactly as a Card's is; the track's sunken fill stays
    * either way, being a groove for the thumb to sit in rather than a way of
    * being seen.
+   *
+   * **The track itself is not on this axis, and `Tabs` reaches the same one
+   * from the other side.** There it is `variant="segmented"`, opted into,
+   * because a row of tabs is a row until asked; here it is the resting state,
+   * because a group of toggles is one control. Same groove, opposite polarity,
+   * and what decides the polarity is which reading is ordinary for the family.
    * - `default-value`/`defaultValue`: The value the markup declared, which is where a reset returns to.
    * - `value`: What the control holds now, and what its form submits.
    *
@@ -57475,6 +57553,14 @@ export type CustomElementsSolidJs = {
    * and `underlined` are participles reading as a pair, the way `outlined` on
    * Accordion does.
    *
+   * **`segmented` is `ToggleGroup`'s track, opted into.** The two draw the same
+   * groove, token for token, and the sheets already say so where the height is
+   * fixed. What differs is polarity, and both are right: a group of toggles is
+   * one control, so its track is the resting state and its `separation` decides
+   * only the frame around it, while a row of tabs is a row until something says
+   * otherwise, so the track is a value here rather than the thing a value takes
+   * away.
+   *
    * Reflected and left unset by default, so the host carries nothing a
    * consumer's server markup does not already have.
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
@@ -58926,6 +59012,18 @@ export type CustomElementsSolidJs = {
    * toasts is a fact about the page: a stack whose members disagreed about
    * where they were would not be a stack.
    *
+   * **Six corners in one word, where `Carousel` splits the same question in
+   * two.** That family takes a placement and an alignment, and argues at its own
+   * declaration that one attribute naming both facts multiplies rather than
+   * composing. It is right there and wrong here, and the difference is the
+   * shape of the product. A carousel's is ragged: its `overlay` belongs to no
+   * edge at all, and its two groups of chrome move independently, shipping
+   * different defaults so they do not land on each other, which is what makes
+   * rewriting one to move the other a real cost. A stack's is two edges by
+   * three alignments, every pair real and every pair named this way by every
+   * toast a reader has already met. Fusing spells the domain out and loses
+   * nothing; a stack has one position and takes it once.
+   *
    * **Optional, and bottom-end is the absence of it.** Reflecting *and*
    * defaulting is the pair that writes onto a host: every toast region anybody
    * rendered would gain a `placement="bottom-end"` nobody typed, which a React
@@ -59015,6 +59113,12 @@ export type CustomElementsSolidJs = {
    * group's own ground, exactly as a Card's is; the track's sunken fill stays
    * either way, being a groove for the thumb to sit in rather than a way of
    * being seen.
+   *
+   * **The track itself is not on this axis, and `Tabs` reaches the same one
+   * from the other side.** There it is `variant="segmented"`, opted into,
+   * because a row of tabs is a row until asked; here it is the resting state,
+   * because a group of toggles is one control. Same groove, opposite polarity,
+   * and what decides the polarity is which reading is ordinary for the family.
    * - `default-value`/`defaultValue`: The value the markup declared, which is where a reset returns to.
    * - `value`: What the control holds now, and what its form submits.
    *

package/types/vue.d.ts

@@ -9034,6 +9034,14 @@ A value describes itself rather than naming another component: `segmented`
 and `underlined` are participles reading as a pair, the way `outlined` on
 Accordion does.
 
+**`segmented` is `ToggleGroup`'s track, opted into.** The two draw the same
+groove, token for token, and the sheets already say so where the height is
+fixed. What differs is polarity, and both are right: a group of toggles is
+one control, so its track is the resting state and its `separation` decides
+only the frame around it, while a row of tabs is a row until something says
+otherwise, so the track is a value here rather than the thing a value takes
+away.
+
 Reflected and left unset by default, so the host carries nothing a
 consumer's server markup does not already have. */
   variant?: (HelixTabs["variant"]) | undefined;
@@ -9785,6 +9793,18 @@ Named here rather than on each message, because where a page puts its
 toasts is a fact about the page: a stack whose members disagreed about
 where they were would not be a stack.
 
+**Six corners in one word, where `Carousel` splits the same question in
+two.** That family takes a placement and an alignment, and argues at its own
+declaration that one attribute naming both facts multiplies rather than
+composing. It is right there and wrong here, and the difference is the
+shape of the product. A carousel's is ragged: its `overlay` belongs to no
+edge at all, and its two groups of chrome move independently, shipping
+different defaults so they do not land on each other, which is what makes
+rewriting one to move the other a real cost. A stack's is two edges by
+three alignments, every pair real and every pair named this way by every
+toast a reader has already met. Fusing spells the domain out and loses
+nothing; a stack has one position and takes it once.
+
 **Optional, and bottom-end is the absence of it.** Reflecting *and*
 defaulting is the pair that writes onto a host: every toast region anybody
 rendered would gain a `placement="bottom-end"` nobody typed, which a React
@@ -9819,7 +9839,13 @@ background *and* the border: the question is where the group ends, not how
 much ink it claims. `outlined` because the frame is a border over the
 group's own ground, exactly as a Card's is; the track's sunken fill stays
 either way, being a groove for the thumb to sit in rather than a way of
-being seen. */
+being seen.
+
+**The track itself is not on this axis, and `Tabs` reaches the same one
+from the other side.** There it is `variant="segmented"`, opted into,
+because a row of tabs is a row until asked; here it is the resting state,
+because a group of toggles is one control. Same groove, opposite polarity,
+and what decides the polarity is which reading is ordinary for the family. */
   separation?: (HelixToggleGroup["separation"]) | undefined;
   /** The value the markup declared, which is where a reset returns to. */
   "default-value"?: (HelixToggleGroup["defaultValue"]) | undefined;