@fusion.dev/helix 0.103.2 → 0.103.3

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.2",
+  "version": "0.103.3",
   "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.2",
-    "@fusion.dev/helix-headless": "0.103.2",
-    "@fusion.dev/helix-styles": "0.103.2"
+    "@fusion.dev/helix-core": "0.103.3",
+    "@fusion.dev/helix-headless": "0.103.3",
+    "@fusion.dev/helix-styles": "0.103.3"
   },
   "devDependencies": {
-    "@fusion.dev/helix-cem": "0.103.2",
-    "@fusion.dev/helix-testing": "0.103.2",
+    "@fusion.dev/helix-cem": "0.103.3",
+    "@fusion.dev/helix-testing": "0.103.3",
     "@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

@@ -11510,56 +11510,48 @@ export type HelixMapHelixMapZoomElementEvent =
   HelixMapElementEvent<HelixMapZoomEvent>;
 
 export type HelixMapProps = {
-  /** Which of the controls this frame draws, as a list of what to keep.
-
-**A list rather than a switch, because the overlap is not symmetric.**
-Every map library draws zoom controls and none of them draws pan buttons:
-MapLibre's navigation control is zoom and a compass, Leaflet's is zoom,
-Google's is zoom. So a consumer slotting one of those has our zoom twice
-over and our pan pad not at all, and a single switch would make them choose
-between a duplicate and nothing.
-
-`none` draws none of them, which is the right answer where the slotted map
-already has controls a reader can find: what this family argues for is that
-*a* findable control exists, never that it is ours. The methods stay public
-either way, so a consumer drawing their own chrome can still drive the
-frame.
-
-Absent is all three, which is this library's rule that a resting value is an
-attribute's absence, and it is what the stylesheet asks about: the layout
-rules are written against `[controls]:not([controls~="zoom"])` rather than
-the bare negation, or a frame that named no list at all would be laid out as
-though it had dropped everything. */
+  /** Which of the controls this surface draws, as a list of what to keep.
+
+**A list rather than a switch, because the overlap is not symmetric.** A
+surface a consumer brings often has zoom controls of its own and almost
+never has pan buttons, so a single switch would make them choose between
+a duplicate and nothing.
+
+`none` draws none of them, which is the right answer where what was
+slotted already has controls a reader can find: what this argues for is
+that *a* findable control exists, never that it is ours. The methods stay
+public either way, so a consumer drawing their own chrome can still drive
+the surface.
+
+Absent is all three, which is this library's rule that a resting value is
+an attribute's absence, and it is what the stylesheet asks about: the
+layout rules are written against `[controls]:not([controls~="zoom"])`
+rather than the bare negation, or a surface that named no list at all
+would be laid out as though it had dropped everything. */
   controls?: (HelixMap["controls"]) | undefined;
   /** Which corner the controls sit in.
 
-**Configurable because there is no safe default**, and this is a collision
-rather than a taste: MapLibre puts its own controls at the top end, Leaflet
-and OpenLayers at the top start, Google's zoom at the bottom end. Whichever
-corner this took would land on somebody's, which is why every one of those
-libraries made it a setting too.
+**Configurable because there is no safe default**, which is a collision
+rather than a taste: whatever a consumer slots may put its own controls
+in any corner, and every library that draws some made this a setting for
+the same reason.
 
 Logical corners rather than left and right, so a right-to-left page moves
-them without a consumer writing a second rule.
-
-Absent is the top end, which is this library's rule that a resting value is
-an attribute's absence: a default that reflected would write an attribute
-onto every host that no server sent and nobody asked for. */
+them without a consumer writing a second rule. Absent is the top end, a
+resting value being an attribute's absence: a default that reflected
+would write an attribute onto every host that no server sent. */
   "controls-placement"?: (HelixMap["controlsPlacement"]) | undefined;
   /** Which corner the controls sit in.
 
-**Configurable because there is no safe default**, and this is a collision
-rather than a taste: MapLibre puts its own controls at the top end, Leaflet
-and OpenLayers at the top start, Google's zoom at the bottom end. Whichever
-corner this took would land on somebody's, which is why every one of those
-libraries made it a setting too.
+**Configurable because there is no safe default**, which is a collision
+rather than a taste: whatever a consumer slots may put its own controls
+in any corner, and every library that draws some made this a setting for
+the same reason.
 
 Logical corners rather than left and right, so a right-to-left page moves
-them without a consumer writing a second rule.
-
-Absent is the top end, which is this library's rule that a resting value is
-an attribute's absence: a default that reflected would write an attribute
-onto every host that no server sent and nobody asked for. */
+them without a consumer writing a second rule. Absent is the top end, a
+resting value being an attribute's absence: a default that reflected
+would write an attribute onto every host that no server sent. */
   controlsPlacement?: (HelixMap["controlsPlacement"]) | undefined;
   /** What the control that fills the screen is called. */
   "fullscreen-label"?: (HelixMap["fullscreenLabel"]) | undefined;
@@ -11567,16 +11559,42 @@ onto every host that no server sent and nobody asked for. */
   fullscreenLabel?: (HelixMap["fullscreenLabel"]) | undefined;
   /** How long the reader may be still before the chrome hides, in milliseconds.
 
-Zero keeps it up, which is the default: a map's controls are how a keyboard
-reader operates it, and chrome that hides itself by default would be this
-component undoing its own argument. Set it for a display map nobody drives. */
+Zero keeps it up, which is the default: these controls are how a keyboard
+reader operates the surface, and chrome that hid itself by default would
+be the component undoing its own argument. Set it for a display nobody
+drives. */
   "idle-delay"?: (HelixMap["idleDelay"] | `${number}`) | undefined;
   /** How long the reader may be still before the chrome hides, in milliseconds.
 
-Zero keeps it up, which is the default: a map's controls are how a keyboard
-reader operates it, and chrome that hides itself by default would be this
-component undoing its own argument. Set it for a display map nobody drives. */
+Zero keeps it up, which is the default: these controls are how a keyboard
+reader operates the surface, and chrome that hid itself by default would
+be the component undoing its own argument. Set it for a display nobody
+drives. */
   idleDelay?: (HelixMap["idleDelay"]) | undefined;
+  /** What one pan control is called, with `{way}` filled in. */
+  "pan-label"?: (HelixMap["panLabel"]) | undefined;
+  /** What one pan control is called, with `{way}` filled in. */
+  panLabel?: (HelixMap["panLabel"]) | undefined;
+  /** How far one press moves the view, as a fraction of what is on screen.
+
+A fraction rather than a distance, because this surface does not know the
+scale of what is inside it: a quarter of the viewport is the same gesture
+at any zoom, and a consumer who wants their own units multiplies by them. */
+  "pan-step"?: (HelixMap["panStep"] | `${number}`) | undefined;
+  /** How far one press moves the view, as a fraction of what is on screen.
+
+A fraction rather than a distance, because this surface does not know the
+scale of what is inside it: a quarter of the viewport is the same gesture
+at any zoom, and a consumer who wants their own units multiplies by them. */
+  panStep?: (HelixMap["panStep"]) | undefined;
+  /** What the control that zooms in is called. */
+  "zoom-in-label"?: (HelixMap["zoomInLabel"]) | undefined;
+  /** What the control that zooms in is called. */
+  zoomInLabel?: (HelixMap["zoomInLabel"]) | undefined;
+  /** What the control that zooms out is called. */
+  "zoom-out-label"?: (HelixMap["zoomOutLabel"]) | undefined;
+  /** What the control that zooms out is called. */
+  zoomOutLabel?: (HelixMap["zoomOutLabel"]) | undefined;
   /** Accessible name for the map, which is the one thing a consumer must write.
 
 There is no sensible default. "Map" names the widget rather than the place,
@@ -11590,32 +11608,6 @@ 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;
-  /** What the controls are called, for a page not in English. */
-  panLabel?: (HelixMap["panLabel"]) | undefined;
-  /** How far one press moves the map, as a fraction of what is on screen.
-
-A fraction rather than a distance, because this frame does not know the
-scale of what is inside it: a quarter of the viewport is the same gesture at
-street level and at country level, and a consumer who wants metres can
-multiply by their own. */
-  "pan-step"?: (HelixMap["panStep"] | `${number}`) | undefined;
-  /** How far one press moves the map, as a fraction of what is on screen.
-
-A fraction rather than a distance, because this frame does not know the
-scale of what is inside it: a quarter of the viewport is the same gesture at
-street level and at country level, and a consumer who wants metres can
-multiply by their own. */
-  panStep?: (HelixMap["panStep"]) | undefined;
-  /** What the zoom controls are called. */
-  "zoom-in-label"?: (HelixMap["zoomInLabel"]) | undefined;
-  /** What the zoom controls are called. */
-  zoomInLabel?: (HelixMap["zoomInLabel"]) | undefined;
-  /** What the zoom control that goes the other way is called. */
-  "zoom-out-label"?: (HelixMap["zoomOutLabel"]) | undefined;
-  /** What the zoom control that goes the other way is called. */
-  zoomOutLabel?: (HelixMap["zoomOutLabel"]) | undefined;
 
   /** The reader asked the map to move. Answer it against your own map. */
   "onhelix-map-pan"?: ((e: HelixMapHelixMapPanElementEvent) => void) | undefined;
@@ -11624,56 +11616,48 @@ multiply by their own. */
 };
 
 export type HelixMapSolidJsProps = {
-  /** Which of the controls this frame draws, as a list of what to keep.
-
-**A list rather than a switch, because the overlap is not symmetric.**
-Every map library draws zoom controls and none of them draws pan buttons:
-MapLibre's navigation control is zoom and a compass, Leaflet's is zoom,
-Google's is zoom. So a consumer slotting one of those has our zoom twice
-over and our pan pad not at all, and a single switch would make them choose
-between a duplicate and nothing.
-
-`none` draws none of them, which is the right answer where the slotted map
-already has controls a reader can find: what this family argues for is that
-*a* findable control exists, never that it is ours. The methods stay public
-either way, so a consumer drawing their own chrome can still drive the
-frame.
-
-Absent is all three, which is this library's rule that a resting value is an
-attribute's absence, and it is what the stylesheet asks about: the layout
-rules are written against `[controls]:not([controls~="zoom"])` rather than
-the bare negation, or a frame that named no list at all would be laid out as
-though it had dropped everything. */
+  /** Which of the controls this surface draws, as a list of what to keep.
+
+**A list rather than a switch, because the overlap is not symmetric.** A
+surface a consumer brings often has zoom controls of its own and almost
+never has pan buttons, so a single switch would make them choose between
+a duplicate and nothing.
+
+`none` draws none of them, which is the right answer where what was
+slotted already has controls a reader can find: what this argues for is
+that *a* findable control exists, never that it is ours. The methods stay
+public either way, so a consumer drawing their own chrome can still drive
+the surface.
+
+Absent is all three, which is this library's rule that a resting value is
+an attribute's absence, and it is what the stylesheet asks about: the
+layout rules are written against `[controls]:not([controls~="zoom"])`
+rather than the bare negation, or a surface that named no list at all
+would be laid out as though it had dropped everything. */
   "prop:controls"?: (HelixMap["controls"]) | undefined;
   /** Which corner the controls sit in.
 
-**Configurable because there is no safe default**, and this is a collision
-rather than a taste: MapLibre puts its own controls at the top end, Leaflet
-and OpenLayers at the top start, Google's zoom at the bottom end. Whichever
-corner this took would land on somebody's, which is why every one of those
-libraries made it a setting too.
+**Configurable because there is no safe default**, which is a collision
+rather than a taste: whatever a consumer slots may put its own controls
+in any corner, and every library that draws some made this a setting for
+the same reason.
 
 Logical corners rather than left and right, so a right-to-left page moves
-them without a consumer writing a second rule.
-
-Absent is the top end, which is this library's rule that a resting value is
-an attribute's absence: a default that reflected would write an attribute
-onto every host that no server sent and nobody asked for. */
+them without a consumer writing a second rule. Absent is the top end, a
+resting value being an attribute's absence: a default that reflected
+would write an attribute onto every host that no server sent. */
   "attr:controls-placement"?: (HelixMap["controlsPlacement"]) | undefined;
   /** Which corner the controls sit in.
 
-**Configurable because there is no safe default**, and this is a collision
-rather than a taste: MapLibre puts its own controls at the top end, Leaflet
-and OpenLayers at the top start, Google's zoom at the bottom end. Whichever
-corner this took would land on somebody's, which is why every one of those
-libraries made it a setting too.
+**Configurable because there is no safe default**, which is a collision
+rather than a taste: whatever a consumer slots may put its own controls
+in any corner, and every library that draws some made this a setting for
+the same reason.
 
 Logical corners rather than left and right, so a right-to-left page moves
-them without a consumer writing a second rule.
-
-Absent is the top end, which is this library's rule that a resting value is
-an attribute's absence: a default that reflected would write an attribute
-onto every host that no server sent and nobody asked for. */
+them without a consumer writing a second rule. Absent is the top end, a
+resting value being an attribute's absence: a default that reflected
+would write an attribute onto every host that no server sent. */
   "prop:controlsPlacement"?: (HelixMap["controlsPlacement"]) | undefined;
   /** What the control that fills the screen is called. */
   "attr:fullscreen-label"?: (HelixMap["fullscreenLabel"]) | undefined;
@@ -11681,16 +11665,42 @@ onto every host that no server sent and nobody asked for. */
   "prop:fullscreenLabel"?: (HelixMap["fullscreenLabel"]) | undefined;
   /** How long the reader may be still before the chrome hides, in milliseconds.
 
-Zero keeps it up, which is the default: a map's controls are how a keyboard
-reader operates it, and chrome that hides itself by default would be this
-component undoing its own argument. Set it for a display map nobody drives. */
+Zero keeps it up, which is the default: these controls are how a keyboard
+reader operates the surface, and chrome that hid itself by default would
+be the component undoing its own argument. Set it for a display nobody
+drives. */
   "attr:idle-delay"?: (HelixMap["idleDelay"] | `${number}`) | undefined;
   /** How long the reader may be still before the chrome hides, in milliseconds.
 
-Zero keeps it up, which is the default: a map's controls are how a keyboard
-reader operates it, and chrome that hides itself by default would be this
-component undoing its own argument. Set it for a display map nobody drives. */
+Zero keeps it up, which is the default: these controls are how a keyboard
+reader operates the surface, and chrome that hid itself by default would
+be the component undoing its own argument. Set it for a display nobody
+drives. */
   "prop:idleDelay"?: (HelixMap["idleDelay"]) | undefined;
+  /** What one pan control is called, with `{way}` filled in. */
+  "attr:pan-label"?: (HelixMap["panLabel"]) | undefined;
+  /** What one pan control is called, with `{way}` filled in. */
+  "prop:panLabel"?: (HelixMap["panLabel"]) | undefined;
+  /** How far one press moves the view, as a fraction of what is on screen.
+
+A fraction rather than a distance, because this surface does not know the
+scale of what is inside it: a quarter of the viewport is the same gesture
+at any zoom, and a consumer who wants their own units multiplies by them. */
+  "attr:pan-step"?: (HelixMap["panStep"] | `${number}`) | undefined;
+  /** How far one press moves the view, as a fraction of what is on screen.
+
+A fraction rather than a distance, because this surface does not know the
+scale of what is inside it: a quarter of the viewport is the same gesture
+at any zoom, and a consumer who wants their own units multiplies by them. */
+  "prop:panStep"?: (HelixMap["panStep"]) | undefined;
+  /** What the control that zooms in is called. */
+  "attr:zoom-in-label"?: (HelixMap["zoomInLabel"]) | undefined;
+  /** What the control that zooms in is called. */
+  "prop:zoomInLabel"?: (HelixMap["zoomInLabel"]) | undefined;
+  /** What the control that zooms out is called. */
+  "attr:zoom-out-label"?: (HelixMap["zoomOutLabel"]) | undefined;
+  /** What the control that zooms out is called. */
+  "prop:zoomOutLabel"?: (HelixMap["zoomOutLabel"]) | undefined;
   /** Accessible name for the map, which is the one thing a consumer must write.
 
 There is no sensible default. "Map" names the widget rather than the place,
@@ -11704,32 +11714,6 @@ 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;
-  /** What the controls are called, for a page not in English. */
-  "prop:panLabel"?: (HelixMap["panLabel"]) | undefined;
-  /** How far one press moves the map, as a fraction of what is on screen.
-
-A fraction rather than a distance, because this frame does not know the
-scale of what is inside it: a quarter of the viewport is the same gesture at
-street level and at country level, and a consumer who wants metres can
-multiply by their own. */
-  "attr:pan-step"?: (HelixMap["panStep"] | `${number}`) | undefined;
-  /** How far one press moves the map, as a fraction of what is on screen.
-
-A fraction rather than a distance, because this frame does not know the
-scale of what is inside it: a quarter of the viewport is the same gesture at
-street level and at country level, and a consumer who wants metres can
-multiply by their own. */
-  "prop:panStep"?: (HelixMap["panStep"]) | undefined;
-  /** What the zoom controls are called. */
-  "attr:zoom-in-label"?: (HelixMap["zoomInLabel"]) | undefined;
-  /** What the zoom controls are called. */
-  "prop:zoomInLabel"?: (HelixMap["zoomInLabel"]) | undefined;
-  /** What the zoom control that goes the other way is called. */
-  "attr:zoom-out-label"?: (HelixMap["zoomOutLabel"]) | undefined;
-  /** What the zoom control that goes the other way is called. */
-  "prop:zoomOutLabel"?: (HelixMap["zoomOutLabel"]) | undefined;
   /** The reader asked the map to move. Answer it against your own map. */
   "on:helix-map-pan"?: ((e: HelixMapHelixMapPanElementEvent) => void) | undefined;
   /** The reader asked the map to zoom, by a direction rather than to a level. */
@@ -31887,46 +31871,50 @@ export type CustomElements = {
    *
    * Component attributes and properties that can be applied to the element or by using JavaScript.
    *
-   * - `controls`: Which of the controls this frame draws, as a list of what to keep.
+   * - `controls`: Which of the controls this surface draws, as a list of what to keep.
    *
-   * **A list rather than a switch, because the overlap is not symmetric.**
-   * Every map library draws zoom controls and none of them draws pan buttons:
-   * MapLibre's navigation control is zoom and a compass, Leaflet's is zoom,
-   * Google's is zoom. So a consumer slotting one of those has our zoom twice
-   * over and our pan pad not at all, and a single switch would make them choose
-   * between a duplicate and nothing.
+   * **A list rather than a switch, because the overlap is not symmetric.** A
+   * surface a consumer brings often has zoom controls of its own and almost
+   * never has pan buttons, so a single switch would make them choose between
+   * a duplicate and nothing.
    *
-   * `none` draws none of them, which is the right answer where the slotted map
-   * already has controls a reader can find: what this family argues for is that
-   * *a* findable control exists, never that it is ours. The methods stay public
-   * either way, so a consumer drawing their own chrome can still drive the
-   * frame.
+   * `none` draws none of them, which is the right answer where what was
+   * slotted already has controls a reader can find: what this argues for is
+   * that *a* findable control exists, never that it is ours. The methods stay
+   * public either way, so a consumer drawing their own chrome can still drive
+   * the surface.
    *
-   * Absent is all three, which is this library's rule that a resting value is an
-   * attribute's absence, and it is what the stylesheet asks about: the layout
-   * rules are written against `[controls]:not([controls~="zoom"])` rather than
-   * the bare negation, or a frame that named no list at all would be laid out as
-   * though it had dropped everything.
+   * Absent is all three, which is this library's rule that a resting value is
+   * an attribute's absence, and it is what the stylesheet asks about: the
+   * layout rules are written against `[controls]:not([controls~="zoom"])`
+   * rather than the bare negation, or a surface that named no list at all
+   * would be laid out as though it had dropped everything.
    * - `controls-placement`/`controlsPlacement`: Which corner the controls sit in.
    *
-   * **Configurable because there is no safe default**, and this is a collision
-   * rather than a taste: MapLibre puts its own controls at the top end, Leaflet
-   * and OpenLayers at the top start, Google's zoom at the bottom end. Whichever
-   * corner this took would land on somebody's, which is why every one of those
-   * libraries made it a setting too.
+   * **Configurable because there is no safe default**, which is a collision
+   * rather than a taste: whatever a consumer slots may put its own controls
+   * in any corner, and every library that draws some made this a setting for
+   * the same reason.
    *
    * Logical corners rather than left and right, so a right-to-left page moves
-   * them without a consumer writing a second rule.
-   *
-   * Absent is the top end, which is this library's rule that a resting value is
-   * an attribute's absence: a default that reflected would write an attribute
-   * onto every host that no server sent and nobody asked for.
+   * them without a consumer writing a second rule. Absent is the top end, a
+   * resting value being an attribute's absence: a default that reflected
+   * would write an attribute onto every host that no server sent.
    * - `fullscreen-label`/`fullscreenLabel`: What the control that fills the screen is called.
    * - `idle-delay`/`idleDelay`: How long the reader may be still before the chrome hides, in milliseconds.
    *
-   * Zero keeps it up, which is the default: a map's controls are how a keyboard
-   * reader operates it, and chrome that hides itself by default would be this
-   * component undoing its own argument. Set it for a display map nobody drives.
+   * Zero keeps it up, which is the default: these controls are how a keyboard
+   * reader operates the surface, and chrome that hid itself by default would
+   * be the component undoing its own argument. Set it for a display nobody
+   * drives.
+   * - `pan-label`/`panLabel`: What one pan control is called, with `{way}` filled in.
+   * - `pan-step`/`panStep`: How far one press moves the view, as a fraction of what is on screen.
+   *
+   * A fraction rather than a distance, because this surface does not know the
+   * scale of what is inside it: a quarter of the viewport is the same gesture
+   * at any zoom, and a consumer who wants their own units multiplies by them.
+   * - `zoom-in-label`/`zoomInLabel`: What the control that zooms in is called.
+   * - `zoom-out-label`/`zoomOutLabel`: What the control that zooms out is called.
    * - `label`: Accessible name for the map, which is the one thing a consumer must write.
    *
    * There is no sensible default. "Map" names the widget rather than the place,
@@ -31939,15 +31927,6 @@ export type CustomElements = {
    * 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.
-   *
-   * A fraction rather than a distance, because this frame does not know the
-   * scale of what is inside it: a quarter of the viewport is the same gesture at
-   * street level and at country level, and a consumer who wants metres can
-   * multiply by their own.
-   * - `zoom-in-label`/`zoomInLabel`: What the zoom controls are called.
-   * - `zoom-out-label`/`zoomOutLabel`: What the zoom control that goes the other way is called.
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
    * **Named `whenSettled` because `settled` is taken four times over**, by
@@ -31989,9 +31968,9 @@ export type CustomElements = {
    *
    * Methods that can be called to access component functionality.
    *
-   * - `toggleFullscreen() => void`: Fills the screen with the frame, or comes back.
-   * - `pan(to: Way) => void`: Asks for the map to move, which the consumer answers.
-   * - `zoom(by: number) => void`: Asks for the map to zoom, `1` in and `-1` out.
+   * - `pan(to: ViewportWay) => void`: Asks for the view to move, which the consumer answers.
+   * - `zoom(by: number) => void`: Asks for the view to zoom, `1` in and `-1` out.
+   * - `toggleFullscreen() => void`: Fills the screen with the surface, or comes back.
    *
    * ## CSS Custom Properties
    *
@@ -52130,46 +52109,50 @@ export type CustomElementsSolidJs = {
    *
    * Component attributes and properties that can be applied to the element or by using JavaScript.
    *
-   * - `controls`: Which of the controls this frame draws, as a list of what to keep.
+   * - `controls`: Which of the controls this surface draws, as a list of what to keep.
    *
-   * **A list rather than a switch, because the overlap is not symmetric.**
-   * Every map library draws zoom controls and none of them draws pan buttons:
-   * MapLibre's navigation control is zoom and a compass, Leaflet's is zoom,
-   * Google's is zoom. So a consumer slotting one of those has our zoom twice
-   * over and our pan pad not at all, and a single switch would make them choose
-   * between a duplicate and nothing.
+   * **A list rather than a switch, because the overlap is not symmetric.** A
+   * surface a consumer brings often has zoom controls of its own and almost
+   * never has pan buttons, so a single switch would make them choose between
+   * a duplicate and nothing.
    *
-   * `none` draws none of them, which is the right answer where the slotted map
-   * already has controls a reader can find: what this family argues for is that
-   * *a* findable control exists, never that it is ours. The methods stay public
-   * either way, so a consumer drawing their own chrome can still drive the
-   * frame.
+   * `none` draws none of them, which is the right answer where what was
+   * slotted already has controls a reader can find: what this argues for is
+   * that *a* findable control exists, never that it is ours. The methods stay
+   * public either way, so a consumer drawing their own chrome can still drive
+   * the surface.
    *
-   * Absent is all three, which is this library's rule that a resting value is an
-   * attribute's absence, and it is what the stylesheet asks about: the layout
-   * rules are written against `[controls]:not([controls~="zoom"])` rather than
-   * the bare negation, or a frame that named no list at all would be laid out as
-   * though it had dropped everything.
+   * Absent is all three, which is this library's rule that a resting value is
+   * an attribute's absence, and it is what the stylesheet asks about: the
+   * layout rules are written against `[controls]:not([controls~="zoom"])`
+   * rather than the bare negation, or a surface that named no list at all
+   * would be laid out as though it had dropped everything.
    * - `controls-placement`/`controlsPlacement`: Which corner the controls sit in.
    *
-   * **Configurable because there is no safe default**, and this is a collision
-   * rather than a taste: MapLibre puts its own controls at the top end, Leaflet
-   * and OpenLayers at the top start, Google's zoom at the bottom end. Whichever
-   * corner this took would land on somebody's, which is why every one of those
-   * libraries made it a setting too.
+   * **Configurable because there is no safe default**, which is a collision
+   * rather than a taste: whatever a consumer slots may put its own controls
+   * in any corner, and every library that draws some made this a setting for
+   * the same reason.
    *
    * Logical corners rather than left and right, so a right-to-left page moves
-   * them without a consumer writing a second rule.
-   *
-   * Absent is the top end, which is this library's rule that a resting value is
-   * an attribute's absence: a default that reflected would write an attribute
-   * onto every host that no server sent and nobody asked for.
+   * them without a consumer writing a second rule. Absent is the top end, a
+   * resting value being an attribute's absence: a default that reflected
+   * would write an attribute onto every host that no server sent.
    * - `fullscreen-label`/`fullscreenLabel`: What the control that fills the screen is called.
    * - `idle-delay`/`idleDelay`: How long the reader may be still before the chrome hides, in milliseconds.
    *
-   * Zero keeps it up, which is the default: a map's controls are how a keyboard
-   * reader operates it, and chrome that hides itself by default would be this
-   * component undoing its own argument. Set it for a display map nobody drives.
+   * Zero keeps it up, which is the default: these controls are how a keyboard
+   * reader operates the surface, and chrome that hid itself by default would
+   * be the component undoing its own argument. Set it for a display nobody
+   * drives.
+   * - `pan-label`/`panLabel`: What one pan control is called, with `{way}` filled in.
+   * - `pan-step`/`panStep`: How far one press moves the view, as a fraction of what is on screen.
+   *
+   * A fraction rather than a distance, because this surface does not know the
+   * scale of what is inside it: a quarter of the viewport is the same gesture
+   * at any zoom, and a consumer who wants their own units multiplies by them.
+   * - `zoom-in-label`/`zoomInLabel`: What the control that zooms in is called.
+   * - `zoom-out-label`/`zoomOutLabel`: What the control that zooms out is called.
    * - `label`: Accessible name for the map, which is the one thing a consumer must write.
    *
    * There is no sensible default. "Map" names the widget rather than the place,
@@ -52182,15 +52165,6 @@ export type CustomElementsSolidJs = {
    * 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.
-   *
-   * A fraction rather than a distance, because this frame does not know the
-   * scale of what is inside it: a quarter of the viewport is the same gesture at
-   * street level and at country level, and a consumer who wants metres can
-   * multiply by their own.
-   * - `zoom-in-label`/`zoomInLabel`: What the zoom controls are called.
-   * - `zoom-out-label`/`zoomOutLabel`: What the zoom control that goes the other way is called.
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
    * **Named `whenSettled` because `settled` is taken four times over**, by
@@ -52232,9 +52206,9 @@ export type CustomElementsSolidJs = {
    *
    * Methods that can be called to access component functionality.
    *
-   * - `toggleFullscreen() => void`: Fills the screen with the frame, or comes back.
-   * - `pan(to: Way) => void`: Asks for the map to move, which the consumer answers.
-   * - `zoom(by: number) => void`: Asks for the map to zoom, `1` in and `-1` out.
+   * - `pan(to: ViewportWay) => void`: Asks for the view to move, which the consumer answers.
+   * - `zoom(by: number) => void`: Asks for the view to zoom, `1` in and `-1` out.
+   * - `toggleFullscreen() => void`: Fills the screen with the surface, or comes back.
    *
    * ## CSS Custom Properties
    *