@fusion.dev/helix 0.4.6 → 0.4.7

package/custom-elements.json

@@ -53889,7 +53889,7 @@
               "type": {
                 "text": "string"
               },
-              "description": "The words, for a listbox that has to match text against them.\n\nRead from the rendered content rather than required as a property, because\nthe content is where a consumer naturally puts it and asking for both is\nasking for two things to disagree.\n\n**The default slot's content, never `this.textContent`.** An option holds\nthree slots: the words, plus `start` for an icon and `end` for a shortcut\nor a count. Neither of the latter two is what a reader searched for, and\n`textContent` runs both onto the end of it. Measured on a font picker whose\noptions carry a two-letter specimen in `end`: the field read\n`Noto Sans Linear BAg`, and typing `ag` matched 1,892 of 1,893 options,\nevery row containing the sample. An option with a keyboard shortcut in its\nend slot has the same fault and a worse one, every row carrying one matching\nevery letter of it.\n\nSix things read this: the collapsed field of Select and of Combobox, the\nlistbox's filter, Combobox's match against typed text, its inline\ncompletion, and the label on a chosen tag.\n\nA node goes to the default slot when it names no other, which is the rule\nthe platform applies at assignment. Asking the same question here rather\nthan a second one is what stops the two disagreeing. Text nodes are\nalways the default slot's and cannot say otherwise.",
+              "description": "The words, for a listbox that has to match text against them.\n\nRead from the rendered content rather than required as a property, because\nthe content is where a consumer naturally puts it and asking for both is\nasking for two things to disagree.\n\n**The default slot's content, never `this.textContent`.** An option holds\nthree slots: the words, plus `start` for an icon and `end` for a shortcut\nor a count. Neither of the latter two is what a reader searched for, and\n`textContent` runs both onto the end of it. Measured on a font picker whose\noptions carry a two-letter specimen in `end`: the field read\n`Noto Sans Linear BAg`, and typing `ag` matched 1,892 of 1,893 options,\nevery row containing the sample. An option with a keyboard shortcut in its\nend slot has the same fault and a worse one, every row carrying one matching\nevery letter of it.\n\nSix things read this: the collapsed field of Select and of Combobox, the\nlistbox's filter, Combobox's match against typed text, its inline\ncompletion, and the label on a chosen tag.\n\nA node goes to the default slot when it names no other, which is the rule\nthe platform applies at assignment. Asking the same question here rather\nthan a second one is what stops the two disagreeing. Text nodes are\nalways the default slot's and cannot say otherwise.\n\n**Text and elements, named rather than \"not an element\".** The filter read\n`!(node instanceof Element) || node.slot === ''`, which admits a comment,\nand `textContent` on a comment is the comment's own body. Every option Lit\nrenders carries one: a child binding is marked with `<!--?lit$1234$-->`, so\nan option written as `` html`<${option}>${size}</${option}>` `` read back as\n`?lit$090648746$25`. Measured in `pagination/footer`, where the trigger\npainted exactly that instead of `25`, on both twins.\n\nIt is worse than one wrong label, because of the six readers listed above:\nthe filter and Combobox's match compare against this string, so a marker in\nit is in every comparison too.",
               "readonly": true,
               "inheritedFrom": {
                 "name": "HelixHeadlessOption",

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.4.6",
+  "version": "0.4.7",
   "license": "MIT",
   "author": "Ross Sheppard <ross.sheppard@fusion.dev>",
   "repository": {
@@ -46,14 +46,14 @@
   },
   "bugs": "https://github.com/project-fusion/fusion/issues",
   "dependencies": {
-    "@fusion.dev/helix-core": "0.4.6",
-    "@fusion.dev/helix-headless": "0.4.6",
-    "@fusion.dev/helix-styles": "0.4.6"
+    "@fusion.dev/helix-core": "0.4.7",
+    "@fusion.dev/helix-headless": "0.4.7",
+    "@fusion.dev/helix-styles": "0.4.7"
   },
   "devDependencies": {
     "@custom-elements-manifest/analyzer": "^0.11.0",
-    "@fusion.dev/helix-cem": "0.4.6",
-    "@fusion.dev/helix-testing": "0.4.6",
+    "@fusion.dev/helix-cem": "0.4.7",
+    "@fusion.dev/helix-testing": "0.4.7",
     "@fusion.dev/scripts": "0.0.0-dev",
     "@happy-dom/global-registrator": "^20.0.0",
     "@lit-labs/ssr": "^3.3.0",

package/types/jsx.d.ts

@@ -26555,7 +26555,19 @@ export type CustomElements = {
    * A node goes to the default slot when it names no other, which is the rule
    * the platform applies at assignment. Asking the same question here rather
    * than a second one is what stops the two disagreeing. Text nodes are
-   * always the default slot's and cannot say otherwise. (property only) (readonly)
+   * always the default slot's and cannot say otherwise.
+   *
+   * **Text and elements, named rather than "not an element".** The filter read
+   * `!(node instanceof Element) || node.slot === ''`, which admits a comment,
+   * and `textContent` on a comment is the comment's own body. Every option Lit
+   * renders carries one: a child binding is marked with `<!--?lit$1234$-->`, so
+   * an option written as `` html`<${option}>${size}</${option}>` `` read back as
+   * `?lit$090648746$25`. Measured in `pagination/footer`, where the trigger
+   * painted exactly that instead of `25`, on both twins.
+   *
+   * It is worse than one wrong label, because of the six readers listed above:
+   * the filter and Combobox's match compare against this string, so a marker in
+   * it is in every comparison too. (property only) (readonly)
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
    * **Named `whenSettled` because `settled` is taken four times over**, by
@@ -42314,7 +42326,19 @@ export type CustomElementsSolidJs = {
    * A node goes to the default slot when it names no other, which is the rule
    * the platform applies at assignment. Asking the same question here rather
    * than a second one is what stops the two disagreeing. Text nodes are
-   * always the default slot's and cannot say otherwise. (property only) (readonly)
+   * always the default slot's and cannot say otherwise.
+   *
+   * **Text and elements, named rather than "not an element".** The filter read
+   * `!(node instanceof Element) || node.slot === ''`, which admits a comment,
+   * and `textContent` on a comment is the comment's own body. Every option Lit
+   * renders carries one: a child binding is marked with `<!--?lit$1234$-->`, so
+   * an option written as `` html`<${option}>${size}</${option}>` `` read back as
+   * `?lit$090648746$25`. Measured in `pagination/footer`, where the trigger
+   * painted exactly that instead of `25`, on both twins.
+   *
+   * It is worse than one wrong label, because of the six readers listed above:
+   * the filter and Combobox's match compare against this string, so a marker in
+   * it is in every comparison too. (property only) (readonly)
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
    * **Named `whenSettled` because `settled` is taken four times over**, by