@fusion.dev/helix-headless 0.103.1 → 0.103.2

package/custom-elements.json

@@ -55565,7 +55565,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"
             },
             {
@@ -55721,7 +55721,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."
             },
             {
               "kind": "method",
@@ -56137,7 +56137,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"
             },
             {

package/dist/map/root/map-root.d.ts

@@ -120,6 +120,13 @@ export declare class HelixHeadlessMap extends HelixElement {
      * 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.
      */
     label: string;
     /**
@@ -159,6 +166,14 @@ export declare class HelixHeadlessMap extends HelixElement {
      * `inlineStep` rather than a test against `ArrowLeft`, so the reader on a
      * right-to-left page gets `end` from the key that points the way their text
      * runs, which is what the pan buttons say too.
+     *
+     * **Only from this frame's own chrome, and that is the difference between one
+     * move and two.** MapLibre and Leaflet both answer the arrow keys themselves,
+     * so a press inside a slotted map moves it once on its own and once more on
+     * the event this would have sent: every press moving twice, and the consumer
+     * with no way to tell which half to turn off. A press that started in the
+     * shadow root is this frame's to relay; anything from the map belongs to the
+     * map.
      */
     private readonly handleKeydown;
     /**

package/dist/map/root/map-root.js

@@ -26,6 +26,9 @@ let HelixHeadlessMap = class HelixHeadlessMap extends HelixElement {
             this.resting = resting;
         });
         this.handleKeydown = (event) => {
+            if (!this.renderRoot.contains(event.target)) {
+                return;
+            }
             const along = inlineStep(this, event.key);
             if (along === 1) {
                 event.preventDefault();
@@ -127,6 +130,8 @@ let HelixHeadlessMap = class HelixHeadlessMap extends HelixElement {
       part="region"
       role="group"
       aria-label=${this.label || 'Map'}
+      aria-keyshortcuts="ArrowUp ArrowDown ArrowLeft ArrowRight Plus Minus"
+      tabindex="0"
       @focusin=${this.idle.stir}
       @keydown=${this.handleKeydown}
       @pointerleave=${this.idle.leave}

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@fusion.dev/helix-headless",
   "description": "Headless component tier. Structure, accessibility, state, and form participation. No styling.",
-  "version": "0.103.1",
+  "version": "0.103.2",
   "license": "MIT",
   "author": "Ross Sheppard <ross.sheppard@fusion.dev>",
   "repository": {
@@ -46,13 +46,13 @@
   },
   "bugs": "https://github.com/project-fusion/fusion/issues",
   "dependencies": {
-    "@fusion.dev/helix-core": "0.103.1",
-    "@fusion.dev/helix-icons": "0.103.1",
+    "@fusion.dev/helix-core": "0.103.2",
+    "@fusion.dev/helix-icons": "0.103.2",
     "uqr": "^0.1.3"
   },
   "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

@@ -9467,7 +9467,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?: (HelixHeadlessMap["label"]) | undefined;
   /** What the controls are called, for a page not in English. */
   "pan-label"?: (HelixHeadlessMap["panLabel"]) | undefined;
@@ -9574,7 +9581,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"?: (HelixHeadlessMap["label"]) | undefined;
   /** What the controls are called, for a page not in English. */
   "attr:pan-label"?: (HelixHeadlessMap["panLabel"]) | undefined;
@@ -27661,6 +27675,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.
    *
@@ -46166,6 +46187,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

@@ -4879,7 +4879,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?: (HelixHeadlessMap["label"]) | undefined;
   /** What the controls are called, for a page not in English. */
   "pan-label"?: (HelixHeadlessMap["panLabel"]) | undefined;