@fusion.dev/helix-headless 0.58.1 → 0.59.0

package/types/jsx.d.ts

@@ -164,12 +164,8 @@ import type {
   HelixTourAskEvent,
   at,
   edgeOf,
-  fromMinutes,
   initialsOf,
-  isTime,
   optionsAmong,
-  toMinutes,
-  writeTime,
 } from '@fusion.dev/helix-headless';
 
 /**
@@ -783,8 +779,8 @@ fills the height and the bands are shares of it. */
   totalLabel?: (HelixHeadlessAreaChart["totalLabel"]) | 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
@@ -833,8 +829,8 @@ fills the height and the bands are shares of it. */
   "prop:totalLabel"?: (HelixHeadlessAreaChart["totalLabel"]) | 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
@@ -1103,8 +1099,8 @@ of any scale question the picture raises. */
   secondary?: (HelixHeadlessBarChart["secondary"]) | 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
@@ -1204,8 +1200,8 @@ of any scale question the picture raises. */
   "prop:secondary"?: (HelixHeadlessBarChart["secondary"]) | 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
@@ -6016,8 +6012,8 @@ the circle is not drawn. */
   sweep?: (HelixHeadlessDonutChart["sweep"]) | 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
@@ -6081,8 +6077,8 @@ the circle is not drawn. */
   "prop:sweep"?: (HelixHeadlessDonutChart["sweep"]) | 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
@@ -7414,8 +7410,8 @@ no order in it. */
   tones?: (HelixHeadlessHeatmap["tones"]) | 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
@@ -7509,8 +7505,8 @@ no order in it. */
   "prop:tones"?: (HelixHeadlessHeatmap["tones"]) | 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
@@ -8447,8 +8443,8 @@ shape `categories` already has. */
   entries?: (HelixHeadlessLegend["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. */
@@ -8476,8 +8472,8 @@ shape `categories` already has. */
   "prop:entries"?: (HelixHeadlessLegend["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. */
@@ -8585,8 +8581,8 @@ near the top of the box. */
   zero?: (HelixHeadlessLineChart["zero"]) | 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
@@ -8695,8 +8691,8 @@ near the top of the box. */
   "prop:zero"?: (HelixHeadlessLineChart["zero"]) | 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
@@ -12538,8 +12534,8 @@ is read along. */
   pointsLabel?: (HelixHeadlessScatterChart["pointsLabel"]) | 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
@@ -12570,8 +12566,8 @@ is read along. */
   "prop:pointsLabel"?: (HelixHeadlessScatterChart["pointsLabel"]) | 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
@@ -16328,8 +16324,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.
@@ -16436,8 +16432,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.
@@ -18386,8 +18382,8 @@ export type CustomElements = {
    * - `total-label`/`totalLabel`: What to call the sum of the parts, in the tooltip and the summary.
    * - `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
@@ -18866,8 +18862,8 @@ export type CustomElements = {
    * of any scale question the picture raises.
    * - `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
@@ -23314,8 +23310,8 @@ export type CustomElements = {
    * the circle is not drawn.
    * - `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
@@ -25070,8 +25066,8 @@ export type CustomElements = {
    * no order in it.
    * - `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
@@ -26018,8 +26014,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.
@@ -26186,8 +26182,8 @@ export type CustomElements = {
    * near the top of the box.
    * - `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
@@ -30216,8 +30212,8 @@ export type CustomElements = {
    * - `points-label`/`pointsLabel`: What to call a row in the summary, which counts them.
    * - `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
@@ -34424,8 +34420,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.
@@ -36347,8 +36343,8 @@ export type CustomElementsSolidJs = {
    * - `total-label`/`totalLabel`: What to call the sum of the parts, in the tooltip and the summary.
    * - `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
@@ -36837,8 +36833,8 @@ export type CustomElementsSolidJs = {
    * of any scale question the picture raises.
    * - `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
@@ -41343,8 +41339,8 @@ export type CustomElementsSolidJs = {
    * the circle is not drawn.
    * - `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
@@ -43119,8 +43115,8 @@ export type CustomElementsSolidJs = {
    * no order in it.
    * - `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
@@ -44083,8 +44079,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.
@@ -44254,8 +44250,8 @@ export type CustomElementsSolidJs = {
    * near the top of the box.
    * - `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
@@ -48349,8 +48345,8 @@ export type CustomElementsSolidJs = {
    * - `points-label`/`pointsLabel`: What to call a row in the summary, which counts them.
    * - `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
@@ -52642,8 +52638,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

@@ -115,10 +115,6 @@ import type {
   HelixHeadlessTag,
   HelixHeadlessTextarea,
   HelixHeadlessTimeInput,
-  isTime,
-  toMinutes,
-  fromMinutes,
-  writeTime,
   HelixHeadlessTimePicker,
   HelixHeadlessTimelineItem,
   HelixHeadlessTimeline,
@@ -435,8 +431,8 @@ fills the height and the bands are shares of it. */
   totalLabel?: (HelixHeadlessAreaChart["totalLabel"]) | 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
@@ -622,8 +618,8 @@ of any scale question the picture raises. */
   secondary?: (HelixHeadlessBarChart["secondary"]) | 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
@@ -3105,8 +3101,8 @@ the circle is not drawn. */
   sweep?: (HelixHeadlessDonutChart["sweep"]) | 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
@@ -3838,8 +3834,8 @@ no order in it. */
   tones?: (HelixHeadlessHeatmap["tones"]) | 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
@@ -4335,8 +4331,8 @@ shape `categories` already has. */
   entries?: (HelixHeadlessLegend["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. */
@@ -4441,8 +4437,8 @@ near the top of the box. */
   zero?: (HelixHeadlessLineChart["zero"]) | 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
@@ -6426,8 +6422,8 @@ is read along. */
   pointsLabel?: (HelixHeadlessScatterChart["pointsLabel"]) | 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
@@ -8383,8 +8379,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.