@fusion.dev/helix 0.103.1 → 0.103.2

package/custom-elements.json

@@ -69424,7 +69424,7 @@
                 "text": "string"
               },
               "default": "''",
-              "description": "Accessible name for the map, which is the one thing a consumer must write.\n\nThere is no sensible default. \"Map\" names the widget rather than the place,\nand a reader meeting three of them on a page learns nothing from hearing the\nsame word three times.",
+              "description": "Accessible name for the map, which is the one thing a consumer must write.\n\nThere is no sensible default. \"Map\" names the widget rather than the place,\nand a reader meeting three of them on a page learns nothing from hearing the\nsame word three times.\n\n**The region is a tab stop**, so the keys are reachable however the controls\nare configured: the listener is on the region, and without a stop of its own\na frame at `controls=\"none\"` around a map with nothing focusable in it had\narrow keys no reader could ever press. `aria-keyshortcuts` says which keys\nrather than spelling them into the name, which would otherwise be read out\nat every encounter.",
               "attribute": "label",
               "inheritedFrom": {
                 "name": "HelixHeadlessMap",
@@ -69632,7 +69632,7 @@
               "name": "handleKeydown",
               "privacy": "private",
               "readonly": true,
-              "description": "The arrow keys, which are the second way rather than the only one.\n\n`inlineStep` rather than a test against `ArrowLeft`, so the reader on a\nright-to-left page gets `end` from the key that points the way their text\nruns, which is what the pan buttons say too.",
+              "description": "The arrow keys, which are the second way rather than the only one.\n\n`inlineStep` rather than a test against `ArrowLeft`, so the reader on a\nright-to-left page gets `end` from the key that points the way their text\nruns, which is what the pan buttons say too.\n\n**Only from this frame's own chrome, and that is the difference between one\nmove and two.** MapLibre and Leaflet both answer the arrow keys themselves,\nso a press inside a slotted map moves it once on its own and once more on\nthe event this would have sent: every press moving twice, and the consumer\nwith no way to tell which half to turn off. A press that started in the\nshadow root is this frame's to relay; anything from the map belongs to the\nmap.",
               "inheritedFrom": {
                 "name": "HelixHeadlessMap",
                 "module": "src/map/root/map-root.ts"
@@ -70238,7 +70238,7 @@
                 "text": "string"
               },
               "default": "''",
-              "description": "Accessible name for the map, which is the one thing a consumer must write.\n\nThere is no sensible default. \"Map\" names the widget rather than the place,\nand a reader meeting three of them on a page learns nothing from hearing the\nsame word three times.",
+              "description": "Accessible name for the map, which is the one thing a consumer must write.\n\nThere is no sensible default. \"Map\" names the widget rather than the place,\nand a reader meeting three of them on a page learns nothing from hearing the\nsame word three times.\n\n**The region is a tab stop**, so the keys are reachable however the controls\nare configured: the listener is on the region, and without a stop of its own\na frame at `controls=\"none\"` around a map with nothing focusable in it had\narrow keys no reader could ever press. `aria-keyshortcuts` says which keys\nrather than spelling them into the name, which would otherwise be read out\nat every encounter.",
               "fieldName": "label",
               "inheritedFrom": {
                 "name": "HelixHeadlessMap",

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.103.1",
+  "version": "0.103.2",
   "license": "MIT",
   "author": "Ross Sheppard <ross.sheppard@fusion.dev>",
   "repository": {
@@ -47,13 +47,13 @@
   },
   "bugs": "https://github.com/project-fusion/fusion/issues",
   "dependencies": {
-    "@fusion.dev/helix-core": "0.103.1",
-    "@fusion.dev/helix-headless": "0.103.1",
-    "@fusion.dev/helix-styles": "0.103.1"
+    "@fusion.dev/helix-core": "0.103.2",
+    "@fusion.dev/helix-headless": "0.103.2",
+    "@fusion.dev/helix-styles": "0.103.2"
   },
   "devDependencies": {
-    "@fusion.dev/helix-cem": "0.103.1",
-    "@fusion.dev/helix-testing": "0.103.1",
+    "@fusion.dev/helix-cem": "0.103.2",
+    "@fusion.dev/helix-testing": "0.103.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

@@ -11581,7 +11581,14 @@ component undoing its own argument. Set it for a display map nobody drives. */
 
 There is no sensible default. "Map" names the widget rather than the place,
 and a reader meeting three of them on a page learns nothing from hearing the
-same word three times. */
+same word three times.
+
+**The region is a tab stop**, so the keys are reachable however the controls
+are configured: the listener is on the region, and without a stop of its own
+a frame at `controls="none"` around a map with nothing focusable in it had
+arrow keys no reader could ever press. `aria-keyshortcuts` says which keys
+rather than spelling them into the name, which would otherwise be read out
+at every encounter. */
   label?: (HelixMap["label"]) | undefined;
   /** What the controls are called, for a page not in English. */
   "pan-label"?: (HelixMap["panLabel"]) | undefined;
@@ -11688,7 +11695,14 @@ component undoing its own argument. Set it for a display map nobody drives. */
 
 There is no sensible default. "Map" names the widget rather than the place,
 and a reader meeting three of them on a page learns nothing from hearing the
-same word three times. */
+same word three times.
+
+**The region is a tab stop**, so the keys are reachable however the controls
+are configured: the listener is on the region, and without a stop of its own
+a frame at `controls="none"` around a map with nothing focusable in it had
+arrow keys no reader could ever press. `aria-keyshortcuts` says which keys
+rather than spelling them into the name, which would otherwise be read out
+at every encounter. */
   "prop:label"?: (HelixMap["label"]) | undefined;
   /** What the controls are called, for a page not in English. */
   "attr:pan-label"?: (HelixMap["panLabel"]) | undefined;
@@ -31918,6 +31932,13 @@ export type CustomElements = {
    * There is no sensible default. "Map" names the widget rather than the place,
    * and a reader meeting three of them on a page learns nothing from hearing the
    * same word three times.
+   *
+   * **The region is a tab stop**, so the keys are reachable however the controls
+   * are configured: the listener is on the region, and without a stop of its own
+   * a frame at `controls="none"` around a map with nothing focusable in it had
+   * arrow keys no reader could ever press. `aria-keyshortcuts` says which keys
+   * rather than spelling them into the name, which would otherwise be read out
+   * at every encounter.
    * - `pan-label`/`panLabel`: What the controls are called, for a page not in English.
    * - `pan-step`/`panStep`: How far one press moves the map, as a fraction of what is on screen.
    *
@@ -52154,6 +52175,13 @@ export type CustomElementsSolidJs = {
    * There is no sensible default. "Map" names the widget rather than the place,
    * and a reader meeting three of them on a page learns nothing from hearing the
    * same word three times.
+   *
+   * **The region is a tab stop**, so the keys are reachable however the controls
+   * are configured: the listener is on the region, and without a stop of its own
+   * a frame at `controls="none"` around a map with nothing focusable in it had
+   * arrow keys no reader could ever press. `aria-keyshortcuts` says which keys
+   * rather than spelling them into the name, which would otherwise be read out
+   * at every encounter.
    * - `pan-label`/`panLabel`: What the controls are called, for a page not in English.
    * - `pan-step`/`panStep`: How far one press moves the map, as a fraction of what is on screen.
    *

package/types/vue.d.ts

@@ -5951,7 +5951,14 @@ component undoing its own argument. Set it for a display map nobody drives. */
 
 There is no sensible default. "Map" names the widget rather than the place,
 and a reader meeting three of them on a page learns nothing from hearing the
-same word three times. */
+same word three times.
+
+**The region is a tab stop**, so the keys are reachable however the controls
+are configured: the listener is on the region, and without a stop of its own
+a frame at `controls="none"` around a map with nothing focusable in it had
+arrow keys no reader could ever press. `aria-keyshortcuts` says which keys
+rather than spelling them into the name, which would otherwise be read out
+at every encounter. */
   label?: (HelixMap["label"]) | undefined;
   /** What the controls are called, for a page not in English. */
   "pan-label"?: (HelixMap["panLabel"]) | undefined;