@fusion.dev/helix 0.58.1 → 0.59.0

package/types/jsx.d.ts

@@ -922,8 +922,8 @@ the property carries the part's name, `content`. */
 export type HelixAreaChartProps = {
   /** The id of the table to read.
 
-Resolved through `getRootNode()`, so a chart inside another component's
-shadow root names a table in that root rather than in the document. A
+Names a table in the same tree, so a chart inside another component's
+shadow root reads a table in that root rather than one in the document. A
 `<table>` or anything built from grid roles, including `helix-table`.
 
 **In React this arrives as a property and not as an attribute**, the way
@@ -972,8 +972,8 @@ fills the height and the bands are shares of it. */
 export type HelixAreaChartSolidJsProps = {
   /** The id of the table to read.
 
-Resolved through `getRootNode()`, so a chart inside another component's
-shadow root names a table in that root rather than in the document. A
+Names a table in the same tree, so a chart inside another component's
+shadow root reads a table in that root rather than one in the document. A
 `<table>` or anything built from grid roles, including `helix-table`.
 
 **In React this arrives as a property and not as an attribute**, the way
@@ -1559,8 +1559,8 @@ the `bar-wash-start` and `bar-wash-end` stops. */
   wash?: (HelixBarChart["wash"]) | undefined;
   /** The id of the table to read.
 
-Resolved through `getRootNode()`, so a chart inside another component's
-shadow root names a table in that root rather than in the document. A
+Names a table in the same tree, so a chart inside another component's
+shadow root reads a table in that root rather than one in the document. A
 `<table>` or anything built from grid roles, including `helix-table`.
 
 **In React this arrives as a property and not as an attribute**, the way
@@ -1764,8 +1764,8 @@ the `bar-wash-start` and `bar-wash-end` stops. */
   "prop:wash"?: (HelixBarChart["wash"]) | undefined;
   /** The id of the table to read.
 
-Resolved through `getRootNode()`, so a chart inside another component's
-shadow root names a table in that root rather than in the document. A
+Names a table in the same tree, so a chart inside another component's
+shadow root reads a table in that root rather than one in the document. A
 `<table>` or anything built from grid roles, including `helix-table`.
 
 **In React this arrives as a property and not as an attribute**, the way
@@ -7405,8 +7405,8 @@ having the datum rather than by painting it invisibly. */
   material?: (HelixDonutChart["material"]) | undefined;
   /** The id of the table to read.
 
-Resolved through `getRootNode()`, so a chart inside another component's
-shadow root names a table in that root rather than in the document. A
+Names a table in the same tree, so a chart inside another component's
+shadow root reads a table in that root rather than one in the document. A
 `<table>` or anything built from grid roles, including `helix-table`.
 
 **In React this arrives as a property and not as an attribute**, the way
@@ -7511,8 +7511,8 @@ having the datum rather than by painting it invisibly. */
   "prop:material"?: (HelixDonutChart["material"]) | undefined;
   /** The id of the table to read.
 
-Resolved through `getRootNode()`, so a chart inside another component's
-shadow root names a table in that root rather than in the document. A
+Names a table in the same tree, so a chart inside another component's
+shadow root reads a table in that root rather than one in the document. A
 `<table>` or anything built from grid roles, including `helix-table`.
 
 **In React this arrives as a property and not as an attribute**, the way
@@ -9019,8 +9019,8 @@ export type HelixHeatmapHelixResizeElementEvent =
 export type HelixHeatmapProps = {
   /** The id of the table to read.
 
-Resolved through `getRootNode()`, so a chart inside another component's
-shadow root names a table in that root rather than in the document. A
+Names a table in the same tree, so a chart inside another component's
+shadow root reads a table in that root rather than one in the document. A
 `<table>` or anything built from grid roles, including `helix-table`.
 
 **In React this arrives as a property and not as an attribute**, the way
@@ -9114,8 +9114,8 @@ no order in it. */
 export type HelixHeatmapSolidJsProps = {
   /** The id of the table to read.
 
-Resolved through `getRootNode()`, so a chart inside another component's
-shadow root names a table in that root rather than in the document. A
+Names a table in the same tree, so a chart inside another component's
+shadow root reads a table in that root rather than one in the document. A
 `<table>` or anything built from grid roles, including `helix-table`.
 
 **In React this arrives as a property and not as an attribute**, the way
@@ -10291,8 +10291,8 @@ shape `categories` already has. */
   entries?: (HelixLegend["entries"]) | undefined;
   /** The id of the table to take the names from.
 
-Resolved through `getRootNode()`, so a legend inside another component's
-shadow root names a table in that root rather than in the document.
+Names a table in the same tree, so a legend inside another component's
+shadow root reads a table in that root rather than one in the document.
 
 **In React this arrives as a property and not as an attribute**, the way
 `Tooltip.for` does, so it does not reflect and nothing styles on it. */
@@ -10387,8 +10387,8 @@ shape `categories` already has. */
   "prop:entries"?: (HelixLegend["entries"]) | undefined;
   /** The id of the table to take the names from.
 
-Resolved through `getRootNode()`, so a legend inside another component's
-shadow root names a table in that root rather than in the document.
+Names a table in the same tree, so a legend inside another component's
+shadow root reads a table in that root rather than one in the document.
 
 **In React this arrives as a property and not as an attribute**, the way
 `Tooltip.for` does, so it does not reflect and nothing styles on it. */
@@ -10443,8 +10443,8 @@ having the datum rather than by painting it invisibly. */
   material?: (HelixLineChart["material"]) | undefined;
   /** The id of the table to read.
 
-Resolved through `getRootNode()`, so a chart inside another component's
-shadow root names a table in that root rather than in the document. A
+Names a table in the same tree, so a chart inside another component's
+shadow root reads a table in that root rather than one in the document. A
 `<table>` or anything built from grid roles, including `helix-table`.
 
 **In React this arrives as a property and not as an attribute**, the way
@@ -10593,8 +10593,8 @@ having the datum rather than by painting it invisibly. */
   "prop:material"?: (HelixLineChart["material"]) | undefined;
   /** The id of the table to read.
 
-Resolved through `getRootNode()`, so a chart inside another component's
-shadow root names a table in that root rather than in the document. A
+Names a table in the same tree, so a chart inside another component's
+shadow root reads a table in that root rather than one in the document. A
 `<table>` or anything built from grid roles, including `helix-table`.
 
 **In React this arrives as a property and not as an attribute**, the way
@@ -15403,8 +15403,8 @@ export type HelixSandboxToolbarSolidJsProps = {
 export type HelixScatterChartProps = {
   /** The id of the table to read.
 
-Resolved through `getRootNode()`, so a chart inside another component's
-shadow root names a table in that root rather than in the document. A
+Names a table in the same tree, so a chart inside another component's
+shadow root reads a table in that root rather than one in the document. A
 `<table>` or anything built from grid roles, including `helix-table`.
 
 **In React this arrives as a property and not as an attribute**, the way
@@ -15435,8 +15435,8 @@ is read along. */
 export type HelixScatterChartSolidJsProps = {
   /** The id of the table to read.
 
-Resolved through `getRootNode()`, so a chart inside another component's
-shadow root names a table in that root rather than in the document. A
+Names a table in the same tree, so a chart inside another component's
+shadow root reads a table in that root rather than one in the document. A
 `<table>` or anything built from grid roles, including `helix-table`.
 
 **In React this arrives as a property and not as an attribute**, the way
@@ -19573,8 +19573,8 @@ Set it and the tooltip stops wrapping: it renders no trigger, listens on
 the element it names, and points its bubble there. Leave it unset and the
 default slot is the trigger, which is the older form.
 
-Resolved through `getRootNode()`, so a tooltip inside another component's
-shadow root names an element in that root rather than in the document.
+Names an element in the same tree, so a tooltip inside another component's
+shadow root points at one in that root rather than one in the document.
 
 **In React this arrives as a property and not as an attribute**, which is
 worth knowing before someone reads the DOM and thinks it did not take.
@@ -19707,8 +19707,8 @@ Set it and the tooltip stops wrapping: it renders no trigger, listens on
 the element it names, and points its bubble there. Leave it unset and the
 default slot is the trigger, which is the older form.
 
-Resolved through `getRootNode()`, so a tooltip inside another component's
-shadow root names an element in that root rather than in the document.
+Names an element in the same tree, so a tooltip inside another component's
+shadow root points at one in that root rather than one in the document.
 
 **In React this arrives as a property and not as an attribute**, which is
 worth knowing before someone reads the DOM and thinks it did not take.
@@ -21783,8 +21783,8 @@ export type CustomElements = {
    *
    * - `for`: The id of the table to read.
    *
-   * Resolved through `getRootNode()`, so a chart inside another component's
-   * shadow root names a table in that root rather than in the document. A
+   * Names a table in the same tree, so a chart inside another component's
+   * shadow root reads a table in that root rather than one in the document. A
    * `<table>` or anything built from grid roles, including `helix-table`.
    *
    * **In React this arrives as a property and not as an attribute**, the way
@@ -22487,8 +22487,8 @@ export type CustomElements = {
    * the `bar-wash-start` and `bar-wash-end` stops.
    * - `for`: The id of the table to read.
    *
-   * Resolved through `getRootNode()`, so a chart inside another component's
-   * shadow root names a table in that root rather than in the document. A
+   * Names a table in the same tree, so a chart inside another component's
+   * shadow root reads a table in that root rather than one in the document. A
    * `<table>` or anything built from grid roles, including `helix-table`.
    *
    * **In React this arrives as a property and not as an attribute**, the way
@@ -27270,8 +27270,8 @@ export type CustomElements = {
    * having the datum rather than by painting it invisibly.
    * - `for`: The id of the table to read.
    *
-   * Resolved through `getRootNode()`, so a chart inside another component's
-   * shadow root names a table in that root rather than in the document. A
+   * Names a table in the same tree, so a chart inside another component's
+   * shadow root reads a table in that root rather than one in the document. A
    * `<table>` or anything built from grid roles, including `helix-table`.
    *
    * **In React this arrives as a property and not as an attribute**, the way
@@ -29014,8 +29014,8 @@ export type CustomElements = {
    *
    * - `for`: The id of the table to read.
    *
-   * Resolved through `getRootNode()`, so a chart inside another component's
-   * shadow root names a table in that root rather than in the document. A
+   * Names a table in the same tree, so a chart inside another component's
+   * shadow root reads a table in that root rather than one in the document. A
    * `<table>` or anything built from grid roles, including `helix-table`.
    *
    * **In React this arrives as a property and not as an attribute**, the way
@@ -30107,8 +30107,8 @@ export type CustomElements = {
    * shape `categories` already has.
    * - `for`: The id of the table to take the names from.
    *
-   * Resolved through `getRootNode()`, so a legend inside another component's
-   * shadow root names a table in that root rather than in the document.
+   * Names a table in the same tree, so a legend inside another component's
+   * shadow root reads a table in that root rather than one in the document.
    *
    * **In React this arrives as a property and not as an attribute**, the way
    * `Tooltip.for` does, so it does not reflect and nothing styles on it.
@@ -30223,8 +30223,8 @@ export type CustomElements = {
    * having the datum rather than by painting it invisibly.
    * - `for`: The id of the table to read.
    *
-   * Resolved through `getRootNode()`, so a chart inside another component's
-   * shadow root names a table in that root rather than in the document. A
+   * Names a table in the same tree, so a chart inside another component's
+   * shadow root reads a table in that root rather than one in the document. A
    * `<table>` or anything built from grid roles, including `helix-table`.
    *
    * **In React this arrives as a property and not as an attribute**, the way
@@ -35080,8 +35080,8 @@ export type CustomElements = {
    *
    * - `for`: The id of the table to read.
    *
-   * Resolved through `getRootNode()`, so a chart inside another component's
-   * shadow root names a table in that root rather than in the document. A
+   * Names a table in the same tree, so a chart inside another component's
+   * shadow root reads a table in that root rather than one in the document. A
    * `<table>` or anything built from grid roles, including `helix-table`.
    *
    * **In React this arrives as a property and not as an attribute**, the way
@@ -39441,8 +39441,8 @@ export type CustomElements = {
    * the element it names, and points its bubble there. Leave it unset and the
    * default slot is the trigger, which is the older form.
    *
-   * Resolved through `getRootNode()`, so a tooltip inside another component's
-   * shadow root names an element in that root rather than in the document.
+   * Names an element in the same tree, so a tooltip inside another component's
+   * shadow root points at one in that root rather than one in the document.
    *
    * **In React this arrives as a property and not as an attribute**, which is
    * worth knowing before someone reads the DOM and thinks it did not take.
@@ -41402,8 +41402,8 @@ export type CustomElementsSolidJs = {
    *
    * - `for`: The id of the table to read.
    *
-   * Resolved through `getRootNode()`, so a chart inside another component's
-   * shadow root names a table in that root rather than in the document. A
+   * Names a table in the same tree, so a chart inside another component's
+   * shadow root reads a table in that root rather than one in the document. A
    * `<table>` or anything built from grid roles, including `helix-table`.
    *
    * **In React this arrives as a property and not as an attribute**, the way
@@ -42122,8 +42122,8 @@ export type CustomElementsSolidJs = {
    * the `bar-wash-start` and `bar-wash-end` stops.
    * - `for`: The id of the table to read.
    *
-   * Resolved through `getRootNode()`, so a chart inside another component's
-   * shadow root names a table in that root rather than in the document. A
+   * Names a table in the same tree, so a chart inside another component's
+   * shadow root reads a table in that root rather than one in the document. A
    * `<table>` or anything built from grid roles, including `helix-table`.
    *
    * **In React this arrives as a property and not as an attribute**, the way
@@ -46984,8 +46984,8 @@ export type CustomElementsSolidJs = {
    * having the datum rather than by painting it invisibly.
    * - `for`: The id of the table to read.
    *
-   * Resolved through `getRootNode()`, so a chart inside another component's
-   * shadow root names a table in that root rather than in the document. A
+   * Names a table in the same tree, so a chart inside another component's
+   * shadow root reads a table in that root rather than one in the document. A
    * `<table>` or anything built from grid roles, including `helix-table`.
    *
    * **In React this arrives as a property and not as an attribute**, the way
@@ -48770,8 +48770,8 @@ export type CustomElementsSolidJs = {
    *
    * - `for`: The id of the table to read.
    *
-   * Resolved through `getRootNode()`, so a chart inside another component's
-   * shadow root names a table in that root rather than in the document. A
+   * Names a table in the same tree, so a chart inside another component's
+   * shadow root reads a table in that root rather than one in the document. A
    * `<table>` or anything built from grid roles, including `helix-table`.
    *
    * **In React this arrives as a property and not as an attribute**, the way
@@ -49883,8 +49883,8 @@ export type CustomElementsSolidJs = {
    * shape `categories` already has.
    * - `for`: The id of the table to take the names from.
    *
-   * Resolved through `getRootNode()`, so a legend inside another component's
-   * shadow root names a table in that root rather than in the document.
+   * Names a table in the same tree, so a legend inside another component's
+   * shadow root reads a table in that root rather than one in the document.
    *
    * **In React this arrives as a property and not as an attribute**, the way
    * `Tooltip.for` does, so it does not reflect and nothing styles on it.
@@ -50002,8 +50002,8 @@ export type CustomElementsSolidJs = {
    * having the datum rather than by painting it invisibly.
    * - `for`: The id of the table to read.
    *
-   * Resolved through `getRootNode()`, so a chart inside another component's
-   * shadow root names a table in that root rather than in the document. A
+   * Names a table in the same tree, so a chart inside another component's
+   * shadow root reads a table in that root rather than one in the document. A
    * `<table>` or anything built from grid roles, including `helix-table`.
    *
    * **In React this arrives as a property and not as an attribute**, the way
@@ -54970,8 +54970,8 @@ export type CustomElementsSolidJs = {
    *
    * - `for`: The id of the table to read.
    *
-   * Resolved through `getRootNode()`, so a chart inside another component's
-   * shadow root names a table in that root rather than in the document. A
+   * Names a table in the same tree, so a chart inside another component's
+   * shadow root reads a table in that root rather than one in the document. A
    * `<table>` or anything built from grid roles, including `helix-table`.
    *
    * **In React this arrives as a property and not as an attribute**, the way
@@ -59433,8 +59433,8 @@ export type CustomElementsSolidJs = {
    * the element it names, and points its bubble there. Leave it unset and the
    * default slot is the trigger, which is the older form.
    *
-   * Resolved through `getRootNode()`, so a tooltip inside another component's
-   * shadow root names an element in that root rather than in the document.
+   * Names an element in the same tree, so a tooltip inside another component's
+   * shadow root points at one in that root rather than one in the document.
    *
    * **In React this arrives as a property and not as an attribute**, which is
    * worth knowing before someone reads the DOM and thinks it did not take.

package/types/vue.d.ts

@@ -493,8 +493,8 @@ export type HelixAppHeaderVueEvents = {
 export type HelixAreaChartVueProps = {
   /** The id of the table to read.
 
-Resolved through `getRootNode()`, so a chart inside another component's
-shadow root names a table in that root rather than in the document. A
+Names a table in the same tree, so a chart inside another component's
+shadow root reads a table in that root rather than one in the document. A
 `<table>` or anything built from grid roles, including `helix-table`.
 
 **In React this arrives as a property and not as an attribute**, the way
@@ -863,8 +863,8 @@ the `bar-wash-start` and `bar-wash-end` stops. */
   wash?: (HelixBarChart["wash"]) | undefined;
   /** The id of the table to read.
 
-Resolved through `getRootNode()`, so a chart inside another component's
-shadow root names a table in that root rather than in the document. A
+Names a table in the same tree, so a chart inside another component's
+shadow root reads a table in that root rather than one in the document. A
 `<table>` or anything built from grid roles, including `helix-table`.
 
 **In React this arrives as a property and not as an attribute**, the way
@@ -3806,8 +3806,8 @@ having the datum rather than by painting it invisibly. */
   material?: (HelixDonutChart["material"]) | undefined;
   /** The id of the table to read.
 
-Resolved through `getRootNode()`, so a chart inside another component's
-shadow root names a table in that root rather than in the document. A
+Names a table in the same tree, so a chart inside another component's
+shadow root reads a table in that root rather than one in the document. A
 `<table>` or anything built from grid roles, including `helix-table`.
 
 **In React this arrives as a property and not as an attribute**, the way
@@ -4622,8 +4622,8 @@ export type HelixHeatmapHelixResizeElementEvent =
 export type HelixHeatmapVueProps = {
   /** The id of the table to read.
 
-Resolved through `getRootNode()`, so a chart inside another component's
-shadow root names a table in that root rather than in the document. A
+Names a table in the same tree, so a chart inside another component's
+shadow root reads a table in that root rather than one in the document. A
 `<table>` or anything built from grid roles, including `helix-table`.
 
 **In React this arrives as a property and not as an attribute**, the way
@@ -5305,8 +5305,8 @@ shape `categories` already has. */
   entries?: (HelixLegend["entries"]) | undefined;
   /** The id of the table to take the names from.
 
-Resolved through `getRootNode()`, so a legend inside another component's
-shadow root names a table in that root rather than in the document.
+Names a table in the same tree, so a legend inside another component's
+shadow root reads a table in that root rather than one in the document.
 
 **In React this arrives as a property and not as an attribute**, the way
 `Tooltip.for` does, so it does not reflect and nothing styles on it. */
@@ -5358,8 +5358,8 @@ having the datum rather than by painting it invisibly. */
   material?: (HelixLineChart["material"]) | undefined;
   /** The id of the table to read.
 
-Resolved through `getRootNode()`, so a chart inside another component's
-shadow root names a table in that root rather than in the document. A
+Names a table in the same tree, so a chart inside another component's
+shadow root reads a table in that root rather than one in the document. A
 `<table>` or anything built from grid roles, including `helix-table`.
 
 **In React this arrives as a property and not as an attribute**, the way
@@ -7887,8 +7887,8 @@ export type HelixSandboxToolbarVueEvents = {};
 export type HelixScatterChartVueProps = {
   /** The id of the table to read.
 
-Resolved through `getRootNode()`, so a chart inside another component's
-shadow root names a table in that root rather than in the document. A
+Names a table in the same tree, so a chart inside another component's
+shadow root reads a table in that root rather than one in the document. A
 `<table>` or anything built from grid roles, including `helix-table`.
 
 **In React this arrives as a property and not as an attribute**, the way
@@ -10055,8 +10055,8 @@ Set it and the tooltip stops wrapping: it renders no trigger, listens on
 the element it names, and points its bubble there. Leave it unset and the
 default slot is the trigger, which is the older form.
 
-Resolved through `getRootNode()`, so a tooltip inside another component's
-shadow root names an element in that root rather than in the document.
+Names an element in the same tree, so a tooltip inside another component's
+shadow root points at one in that root rather than one in the document.
 
 **In React this arrives as a property and not as an attribute**, which is
 worth knowing before someone reads the DOM and thinks it did not take.