vintage-frames 0.15.0 → 0.16.1

package/custom-elements.json

@@ -2563,7 +2563,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "`<vf-desktop>` — the full-bleed classic desktop container.\n\nRenders the desktop pattern — the classic 50% dither by default, or any of\nthe standard patterns by name (`pattern`, System 7's General Controls\nsetting) — and manages the stacking order and `active` state of slotted\n`vf-window` children: a `pointerdown` or\n`focusin` (keyboard focus) anywhere inside a window brings it to the front\nand makes it the single active window. The windows' light-DOM order is kept\nin step with the stacking order (bottom-most first, synced in a task once\nany pointer gesture has ended), so tabbing walks the stack the way the eye\ndoes and Shift+Tab is its exact mirror.\n\nUtility windows (`vf-window[variant=\"utility\"]`) stack in a floating tier\nabove every document-tier window, restack only among themselves, and stand\noutside the single-active invariant entirely — clicking a palette neither\ndeactivates the active document window nor greys the palette, exactly as\nSystem 7's floating windoids behaved while their application was frontmost.\nA slotted `vf-menu-bar` (or a free-standing `vf-menu`) sits on a tier\nabove both, so its dropped menus cover palettes and document windows\nalike; only the screen-corner mask is in front of it.\n\n**Deactivation.** On a real System 7 machine clicking the desktop clicked\nthe *Finder* — the frontmost application's windows lost their stripes.\nclearActive is that gesture's handler: it clears `active` from\nthe whole document tier, and **zero active windows is a legal state**,\nheld until a press or keyboard focus re-enters a document window (or a\nnew one is slotted, which activates it — opening a window brings its\napplication forward). The desktop never takes this decision itself: its\nfurniture is slotted light DOM (an icon layer, say), so only the page\nknows which of its children — or which presses on the bare dither — mean\n\"the Finder\", and it routes those through `clearActive()`. Left alone,\nthe classic always-one-active behavior is unchanged. activeWindow\nreads the current holder, and every change of holder — including to and\nfrom none — fires `vf-activate`.\n\n**Hidden windows.** A window with `hidden` — closed by a page that hides\nits windows rather than removing them, through `vf-window.hide()` or the\nattribute itself — never holds the active state. One slotted hidden waits\nto be shown; `bringToFront()` on one gives it its place in the stack and\nactivates nothing; the holder hiding hands the state to the topmost shown\ndocument window, or to none. A window shown into a tier where none is\nactive, unless the tier was deliberately deactivated, takes it.\nstackingOrder lists the windows as they stand, bottom-most first.\n\n**The work area.** A slotted `vf-menu-bar` along the top takes its band\noff the screen: workArea is what is left, and the gestures on the\nscreen stay in it — a window dragged up stops with its title bar under the\nbar, where it can still be grabbed, and an icon dropped, nudged or walked\non the desktop lands below the bar. `window-top` deepens the area for\nwindows alone (windowArea), for a page with a strip of its own\nunder the bar. A gesture asks for the box it is clamped into with\n`vf-placement-bounds-request` (bubbles, non-composed), the drag surface's\nhandshake, and the desktop answers for the hosts placed on its screen.\n\nThe desktop is a raster with an explicit size, always: **`width` and\n`height`**, in system px, the way a WIND resource declared a window's —\nthe host box renders at the declared screen plus `2 × bezel` per axis, a\nwhole number of system pixels by construction (default 512×342, the\ncompact Mac's screen). Pure CSS sizing is not supported; the page sets\nthe numbers — directly, or via VfDesktop.fitWithin on\n`resize`/`onScaleChange` for a viewport-filling desktop — and positions\nthe sized box with its own stylesheet, keeping any sub-system-pixel\nslack on its side. `bezel` (system px) draws the black screen surround —\nthe CRT's unlit margin — around the screen, rounding its four corners\nwith the classic corner mask.\n\n**`pattern`** names the desktop pattern — `gray-50` (the dither) by\ndefault, any of the 38 standard patterns (docs/PATTERNS.md), or sixteen\nhex digits stating a custom 8×8 pattern, as on `vf-container`. It is\npainted as the screen's own background: black ink on an opaque white\npaper, a repeating tile drawn at the display's resolution, 1-bit at every\ndensity and zoom (src/pattern-fill.ts).\n\n**The drag surface.** The Finder dragged an icon as a dotted outline drawn\non the *screen*, clipped at its edge and phase-locked to its raster, so\nthe screen hosts the layer that outline draws on: a full-bleed child of\nthe screen, `pointer-events: none` (never a hit for the page's\n`elementsFromPoint`), whose children paint one tier above the menu bar\nand under the corner mask — the layer itself is deliberately no stacking\ncontext, since a blend inside one would composite against nothing. An\nicon reaches it without an import, the menu-handshake idiom: on a drag's\nfirst step it dispatches `vf-drag-surface-request` (bubbles, non-composed,\n`detail.surface` null), and the nearest desktop on its light-DOM path\nfills the detail with the layer. A window asks the same way and draws\nthere with the same pen: its zoom rects when it opens from a rect\n(`vf-window.show({ from })`), its outline under an `outline-drag`. Not the\ntop layer: stable Safari cannot\nblend an element there against the page (src/cursor.ts), and a second\nkit entry in the top layer would need a re-promotion handshake.\n\nCustom properties:\n- `--vf-desktop-pattern` — a consumer's own tile art in place of the\n  pattern (the kit's default is a 1-bit 50% checker, opaque\n  black-on-white on a 30-system-px tile). Set, it wins over `pattern` and\n  renders as a placed tile grid at that same 30-px geometry\n  (src/tile-grid.ts); a token swapped at runtime without touching the\n  component wants a `requestUpdate()`.\n- `--vf-desktop` — base color painted *under* the pattern (default\n  `#808080`). The pattern's paper is opaque, so this only becomes visible\n  when `--vf-desktop-pattern` is overridden with a tile that has\n  transparent cells (or with `none`).",
+          "description": "`<vf-desktop>` — the full-bleed classic desktop container.\n\nRenders the desktop pattern — the classic 50% dither by default, or any of\nthe standard patterns by name (`pattern`, System 7's General Controls\nsetting) — and manages the stacking order and `active` state of slotted\n`vf-window` children: a `pointerdown` or\n`focusin` (keyboard focus) anywhere inside a window brings it to the front\nand makes it the single active window. A press on a title bar with ⌘ held\nraises nothing, so a background window is dragged where it stands in the\nstack. The windows' light-DOM order is kept\nin step with the stacking order (bottom-most first, synced in a task once\nany pointer gesture has ended), so tabbing walks the stack the way the eye\ndoes and Shift+Tab is its exact mirror.\n\nUtility windows (`vf-window[variant=\"utility\"]`) stack in a floating tier\nabove every document-tier window, restack only among themselves, and stand\noutside the single-active invariant entirely — clicking a palette neither\ndeactivates the active document window nor greys the palette, exactly as\nSystem 7's floating windoids behaved while their application was frontmost.\nA slotted `vf-menu-bar` (or a free-standing `vf-menu`) sits on a tier\nabove both, so its dropped menus cover palettes and document windows\nalike; only the screen-corner mask is in front of it.\n\n**Deactivation.** On a real System 7 machine clicking the desktop clicked\nthe *Finder* — the frontmost application's windows lost their stripes.\nclearActive is that gesture's handler: it clears `active` from\nthe whole document tier, and **zero active windows is a legal state**,\nheld until a press or keyboard focus re-enters a document window (or a\nnew one is slotted, which activates it — opening a window brings its\napplication forward). The desktop never takes this decision itself: its\nfurniture is slotted light DOM (an icon layer, say), so only the page\nknows which of its children — or which presses on the bare dither — mean\n\"the Finder\", and it routes those through `clearActive()`. Left alone,\nthe classic always-one-active behavior is unchanged. activeWindow\nreads the current holder, and every change of holder — including to and\nfrom none — fires `vf-activate`.\n\n**Hidden windows.** A window with `hidden` — closed by a page that hides\nits windows rather than removing them, through `vf-window.hide()` or the\nattribute itself — never holds the active state. One slotted hidden waits\nto be shown; `bringToFront()` on one gives it its place in the stack and\nactivates nothing; the holder hiding hands the state to the topmost shown\ndocument window, or to none. A window shown into a tier where none is\nactive, unless the tier was deliberately deactivated, takes it.\nstackingOrder lists the windows as they stand, bottom-most first.\n\n**The work area.** A slotted `vf-menu-bar` along the top takes its band\noff the screen: workArea is what is left, and the gestures on the\nscreen stay in it — a window dragged up stops with its title bar under the\nbar, where it can still be grabbed, and an icon dropped, nudged or walked\non the desktop lands below the bar. `window-top` deepens the area for\nwindows alone (windowArea), for a page with a strip of its own\nunder the bar. A gesture asks for the box it is clamped into with\n`vf-placement-bounds-request` (bubbles, non-composed), the drag surface's\nhandshake, and the desktop answers for the hosts placed on its screen.\n\nThe desktop is a raster with an explicit size, always: **`width` and\n`height`**, in system px, the way a WIND resource declared a window's —\nthe host box renders at the declared screen plus `2 × bezel` per axis, a\nwhole number of system pixels by construction (default 512×342, the\ncompact Mac's screen). Pure CSS sizing is not supported; the page sets\nthe numbers — directly, or via VfDesktop.fitWithin on\n`resize`/`onScaleChange` for a viewport-filling desktop — and positions\nthe sized box with its own stylesheet, keeping any sub-system-pixel\nslack on its side. `bezel` (system px) draws the black screen surround —\nthe CRT's unlit margin — around the screen, rounding its four corners\nwith the classic corner mask.\n\n**`pattern`** names the desktop pattern — `gray-50` (the dither) by\ndefault, any of the 38 standard patterns (docs/PATTERNS.md), or sixteen\nhex digits stating a custom 8×8 pattern, as on `vf-container`. It is\npainted as the screen's own background: black ink on an opaque white\npaper, a repeating tile drawn at the display's resolution, 1-bit at every\ndensity and zoom (src/pattern-fill.ts).\n\n**The drag surface.** The Finder dragged an icon as a dotted outline drawn\non the *screen*, clipped at its edge and phase-locked to its raster, so\nthe screen hosts the layer that outline draws on: a full-bleed child of\nthe screen, `pointer-events: none` (never a hit for the page's\n`elementsFromPoint`), whose children paint one tier above the menu bar\nand under the corner mask — the layer itself is deliberately no stacking\ncontext, since a blend inside one would composite against nothing. An\nicon reaches it without an import, the menu-handshake idiom: on a drag's\nfirst step it dispatches `vf-drag-surface-request` (bubbles, non-composed,\n`detail.surface` null), and the nearest desktop on its light-DOM path\nfills the detail with the layer. A window asks the same way and draws\nthere with the same pen: its zoom rects when it opens from a rect\n(`vf-window.show({ from })`), its outline under an `outline-drag`. Not the\ntop layer: stable Safari cannot\nblend an element there against the page (src/cursor.ts), and a second\nkit entry in the top layer would need a re-promotion handshake.\n\nCustom properties:\n- `--vf-desktop-pattern` — a consumer's own tile art in place of the\n  pattern (the kit's default is a 1-bit 50% checker, opaque\n  black-on-white on a 30-system-px tile). Set, it wins over `pattern` and\n  renders as a placed tile grid at that same 30-px geometry\n  (src/tile-grid.ts); a token swapped at runtime without touching the\n  component wants a `requestUpdate()`.\n- `--vf-desktop` — base color painted *under* the pattern (default\n  `#808080`). The pattern's paper is opaque, so this only becomes visible\n  when `--vf-desktop-pattern` is overridden with a tile that has\n  transparent cells (or with `none`).",
           "name": "VfDesktop",
           "cssProperties": [
             {
@@ -2626,8 +2626,9 @@
                 "text": "string | null | undefined"
               },
               "default": "'gray-50'",
-              "description": "The desktop pattern — System 7's General Controls setting. A library\npattern by name (`gray-50`, the classic dither, by default; `gray-75`,\n`bricks`, … — docs/PATTERNS.md) or sixteen hex digits stating a custom\n8×8 pattern, as on `vf-container`. Painted black on opaque white over\nthe whole screen, 1-bit at every density and zoom. A\n`--vf-desktop-pattern` token override still wins and renders the\nconsumer's tile as a placed grid; an unrecognized value warns once and\nkeeps the dither.",
-              "attribute": "pattern"
+              "description": "The desktop pattern — System 7's General Controls setting. A library\npattern by name (`gray-50`, the classic dither, by default; `gray-75`,\n`bricks`, … — docs/PATTERNS.md) or sixteen hex digits stating a custom\n8×8 pattern, as on `vf-container`. Painted black on opaque white over\nthe whole screen, 1-bit at every density and zoom. A\n`--vf-desktop-pattern` token override still wins and renders the\nconsumer's tile as a placed grid; an unrecognized value warns once and\nkeeps the dither. Reflects, so a change can be observed on the\nattribute.",
+              "attribute": "pattern",
+              "reflects": true
             },
             {
               "kind": "field",
@@ -3298,7 +3299,7 @@
                 "text": "string | null | undefined"
               },
               "default": "DEFAULT_PATTERN",
-              "description": "The desktop pattern — System 7's General Controls setting. A library\npattern by name (`gray-50`, the classic dither, by default; `gray-75`,\n`bricks`, … — docs/PATTERNS.md) or sixteen hex digits stating a custom\n8×8 pattern, as on `vf-container`. Painted black on opaque white over\nthe whole screen, 1-bit at every density and zoom. A\n`--vf-desktop-pattern` token override still wins and renders the\nconsumer's tile as a placed grid; an unrecognized value warns once and\nkeeps the dither.",
+              "description": "The desktop pattern — System 7's General Controls setting. A library\npattern by name (`gray-50`, the classic dither, by default; `gray-75`,\n`bricks`, … — docs/PATTERNS.md) or sixteen hex digits stating a custom\n8×8 pattern, as on `vf-container`. Painted black on opaque white over\nthe whole screen, 1-bit at every density and zoom. A\n`--vf-desktop-pattern` token override still wins and renders the\nconsumer's tile as a placed grid; an unrecognized value warns once and\nkeeps the dither. Reflects, so a change can be observed on the\nattribute.",
               "fieldName": "pattern"
             },
             {
@@ -3398,7 +3399,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "`<vf-dialog>` — the System 7 modal dialog shell.\n\nTwo chromes, one modal lifecycle (native `<dialog>` for top-layer rendering\nand focus trapping, with a fully transparent backdrop — no dimming). Both\nare the same dBoxProc double frame — 1px outer rule, 2px gap, 2px inner\nband, no shadow (vfModalFrame):\n\n- **Default:** the movable modal (movableDBoxProc) — the striped title bar\n  set into the top of that frame, with a centered title over a white body.\n  Drag the title bar to move it. `closable` adds the standard close box\n  (left of the bar) — the HIG's own figures disagree on whether a movable\n  modal carries one (Figure 5-1 says yes, Figure 6-1 and the Chapter 6 text\n  say no), so the component enables either reading rather than enforcing\n  one.\n- **`frame=\"plain\"`:** the modal dialog box — the bare frame, no title bar —\n  and immovable, like the original. With no bar, `heading` only names the\n  dialog and `closable` is ignored.\n\nOpen it with `show()` (or set the `open` attribute/property); close with\n`close()`. Escape closes it and fires `vf-close` with\n`{ reason: 'escape' }`; the close box and programmatic closing fire\n`{ reason: 'close' }`. With `light-dismiss`, a click outside the frame\ncloses it too, with `{ reason: 'outside' }` — for the About box; off by\ndefault, since the classic modal ignored an outside click.\n\nAnswers: a `<form method=\"dialog\">` inside it closes it with the\nsubmitting button's `value` as `returnValue`, and `close(value)` does the\nsame. `vf-close` carries it as `detail.returnValue`, null when the close\ncarried none (Escape, a click outside, the close box).\n\nKeyboard, the classic Dialog Manager's two rules (VfModalDialog):\non open, focus goes to the first text-entry control — a slotted control\nwith `autofocus` first — or, with none, to the default button\n(`vf-button variant=\"default\"`). Return or Enter activates the default\nbutton from anywhere in the dialog, a focused Cancel included; Space\npresses the focused control. A link keeps its own Enter, and in a\nmulti-line editor Return inserts the newline while the keypad's Enter\nactivates the button.\n\nSlotted children placed with `top`/`left` measure from the content region's\ncorner — the frame's inner edge, below the title bar — and flow content\nstarts at the same corner.",
+          "description": "`<vf-dialog>` — the System 7 modal dialog shell.\n\nTwo chromes, one modal lifecycle (native `<dialog>` for top-layer rendering\nand focus trapping, with a fully transparent backdrop — no dimming). Both\nare the same dBoxProc double frame — 1px outer rule, 2px gap, 2px inner\nband, no shadow (vfModalFrame):\n\n- **Default:** the movable modal (movableDBoxProc) — the striped title bar\n  set into the top of that frame, with a centered title over a white body.\n  Drag the title bar to move it. `closable` adds the standard close box\n  (left of the bar) — the HIG's own figures disagree on whether a movable\n  modal carries one (Figure 5-1 says yes, Figure 6-1 and the Chapter 6 text\n  say no), so the component enables either reading rather than enforcing\n  one.\n- **`frame=\"plain\"`:** the modal dialog box — the bare frame, no title bar —\n  and immovable, like the original. With no bar, `heading` only names the\n  dialog and `closable` is ignored.\n\nOpen it with `show()` (or set the `open` attribute/property); close with\n`close()`. Escape closes it and fires `vf-close` with\n`{ reason: 'escape' }`; the close box and programmatic closing fire\n`{ reason: 'close' }`. With `light-dismiss`, a click outside the frame\ncloses it too, with `{ reason: 'outside' }` — for the About box; off by\ndefault, since the classic modal ignored an outside click.\n\nAnswers: a `<form method=\"dialog\">` inside it closes it with the\nsubmitting button's `value` as `returnValue`, and `close(value)` does the\nsame. `vf-close` carries it as `detail.returnValue`, null when the close\ncarried none (Escape, a click outside, the close box).\n\nKeyboard, the classic Dialog Manager's two rules (VfModalDialog):\non open, focus goes to the first text-entry control — a slotted control\nwith `autofocus` or `autoselect` first — or, with none, to the default\nbutton (`vf-button variant=\"default\"`). A field marked `autoselect` opens\nwith its whole text selected, on every open. Return or Enter activates\nthe default button from anywhere in the dialog, a focused Cancel\nincluded; Space presses the focused control. A link keeps its own Enter,\nand in a multi-line editor Return inserts the newline while the keypad's\nEnter activates the button.\n\nSlotted children placed with `top`/`left` measure from the content region's\ncorner — the frame's inner edge, below the title bar — and flow content\nstarts at the same corner.",
           "name": "VfDialog",
           "cssProperties": [
             {
@@ -3494,7 +3495,7 @@
                 "text": "boolean"
               },
               "default": "false",
-              "description": "Show the close box (left side of the title bar). Off by default — the\nbare movable-modal bar. Ignored with `frame=\"plain\"` (no bar). Clicking\nit closes the dialog and fires `vf-close` with `{ reason: 'close' }`.",
+              "description": "Show the close box (left side of the title bar). Off by default — the\nbare movable-modal bar. Ignored with `frame=\"plain\"` (no bar). Clicking\nit closes the dialog and fires `vf-close` with `{ reason: 'close' }` and\nthe modifier keys held on the click, as `vf-window`'s close box does.",
               "attribute": "closable",
               "reflects": true
             },
@@ -3561,7 +3562,15 @@
                 "type": {
                   "text": "void"
                 }
-              }
+              },
+              "parameters": [
+                {
+                  "name": "event",
+                  "type": {
+                    "text": "MouseEvent"
+                  }
+                }
+              ]
             },
             {
               "kind": "field",
@@ -3753,6 +3762,20 @@
                 "module": "src/modal-dialog.ts"
               }
             },
+            {
+              "kind": "field",
+              "name": "#closeKeys",
+              "privacy": "private",
+              "type": {
+                "text": "VfCloseKeys | null"
+              },
+              "default": "null",
+              "description": "The modifier keys a close box's click held, pending for the next native `close` event.",
+              "inheritedFrom": {
+                "name": "VfModalDialog",
+                "module": "src/modal-dialog.ts"
+              }
+            },
             {
               "kind": "field",
               "name": "#onSubmit",
@@ -3810,7 +3833,7 @@
                 "text": "HTMLElement | null"
               },
               "privacy": "protected",
-              "description": "Where focus lands on open. The classic Dialog Manager put the insertion\npoint in the first editable text item and gave nothing else focus at all;\nthe web needs a focused control for the keyboard to have anywhere to be,\nso with no text field the default button takes it (which is also what\nmakes Return and Space work there without a Tab). In order:\n\n1. a slotted control carrying `autofocus` — the author's say;\n2. the first enabled text-entry control (`vf-text-field`,\n   `vf-number-field`, `vf-text-area`, or a native text input/textarea);\n3. the defaultButton;\n4. null — leave the browser's own choice alone.\n\nLeft to itself, `showModal()` focuses the first focusable thing in flat\ntree order, which for a Cancel/OK row is Cancel, and for a body with a\nlink in it is the link — so Return did the one thing a classic dialog's\nReturn never did. Override to choose differently.",
+              "description": "Where focus lands on open. The classic Dialog Manager put the insertion\npoint in the first editable text item and gave nothing else focus at all;\nthe web needs a focused control for the keyboard to have anywhere to be,\nso with no text field the default button takes it (which is also what\nmakes Return and Space work there without a Tab). In order:\n\n1. the first slotted control carrying `autofocus` or `autoselect` — the\n   author's say;\n2. the first enabled text-entry control (`vf-text-field`,\n   `vf-number-field`, `vf-text-area`, or a native text input/textarea);\n3. the defaultButton;\n4. null — leave the browser's own choice alone.\n\nLeft to itself, `showModal()` focuses the first focusable thing in flat\ntree order, which for a Cancel/OK row is Cancel, and for a body with a\nlink in it is the link — so Return did the one thing a classic dialog's\nReturn never did. Override to choose differently. A target marked\n`autoselect` has its text selected once `vf-show` has fired.",
               "readonly": true,
               "inheritedFrom": {
                 "name": "VfModalDialog",
@@ -3823,10 +3846,10 @@
               "privacy": "private",
               "return": {
                 "type": {
-                  "text": "void"
+                  "text": "HTMLElement | null"
                 }
               },
-              "description": "Hand focus to initialFocusTarget, right after `showModal()`'s own\nfocusing steps have run (so this is the last word, not a race).",
+              "description": "Hand focus to initialFocusTarget, right after `showModal()`'s own\nfocusing steps have run (so this is the last word, not a race). Returns\nthe element focused, for `vf-show`.",
               "inheritedFrom": {
                 "name": "VfModalDialog",
                 "module": "src/modal-dialog.ts"
@@ -3922,6 +3945,29 @@
                 "module": "src/modal-dialog.ts"
               }
             },
+            {
+              "kind": "method",
+              "name": "closeFromBox",
+              "privacy": "protected",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "keys",
+                  "type": {
+                    "text": "VfCloseKeys"
+                  }
+                }
+              ],
+              "description": "Close from a close box, its `vf-close` carrying the modifier keys held on the click.",
+              "inheritedFrom": {
+                "name": "VfModalDialog",
+                "module": "src/modal-dialog.ts"
+              }
+            },
             {
               "kind": "method",
               "name": "#viewport",
@@ -4159,7 +4205,15 @@
           ],
           "events": [
             {
-              "description": "Dialog closed. Detail `{ reason: 'escape' | 'close' | 'outside', returnValue: string | null }` — `'outside'` only under `light-dismiss`.",
+              "description": "Dialog opened, placed and given its initial focus. Detail `{ focus }`, the element focused: the moment to measure copy that varies. A field marked `autoselect` has its text selected after it.",
+              "name": "vf-show",
+              "inheritedFrom": {
+                "name": "VfModalDialog",
+                "module": "src/modal-dialog.ts"
+              }
+            },
+            {
+              "description": "Dialog closed. Detail `{ reason: 'escape' | 'close' | 'outside', returnValue: string | null }` — `'outside'` only under `light-dismiss` — plus `altKey`, `shiftKey`, `metaKey` and `ctrlKey` when the close box closed it.",
               "name": "vf-close",
               "inheritedFrom": {
                 "name": "VfModalDialog",
@@ -4192,7 +4246,7 @@
                 "text": "boolean"
               },
               "default": "false",
-              "description": "Show the close box (left side of the title bar). Off by default — the\nbare movable-modal bar. Ignored with `frame=\"plain\"` (no bar). Clicking\nit closes the dialog and fires `vf-close` with `{ reason: 'close' }`.",
+              "description": "Show the close box (left side of the title bar). Off by default — the\nbare movable-modal bar. Ignored with `frame=\"plain\"` (no bar). Clicking\nit closes the dialog and fires `vf-close` with `{ reason: 'close' }` and\nthe modifier keys held on the click, as `vf-window`'s close box does.",
               "fieldName": "closable"
             },
             {
@@ -9309,7 +9363,7 @@
               "name": ""
             },
             {
-              "description": "Replaces the `label` text in the bar — e.g. a `vf-img` apple icon for the Apple menu. Keep the `label` attribute set too: it stays the menu's accessible name (the bar item's `aria-label` and the panel's) when the visible title is an image.",
+              "description": "Replaces the `label` text in the bar — e.g. a `vf-img` apple icon for the Apple menu. An icon (`vf-img`, `img`, `svg`, `picture` or `canvas`) is drawn in a 16×16 cell and placed for one: 6 system px into its plate, 6 short of the plate's end, on the plate's top row. Text keeps the text title's place. Keep the `label` attribute set too: it stays the menu's accessible name (the bar item's `aria-label` and the panel's) when the visible title is an image.",
               "name": "label"
             }
           ],
@@ -9386,6 +9440,21 @@
               },
               "privacy": "private"
             },
+            {
+              "kind": "field",
+              "name": "_artTitle",
+              "type": {
+                "text": "boolean"
+              },
+              "privacy": "private",
+              "default": "false",
+              "description": "Whether the title is art — only images in the `label` slot — rather than text."
+            },
+            {
+              "kind": "field",
+              "name": "#onLabelSlotChange",
+              "privacy": "private"
+            },
             {
               "kind": "field",
               "name": "_assignedItems",
@@ -9966,6 +10035,48 @@
                 }
               ]
             },
+            {
+              "kind": "method",
+              "name": "#fit",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "string"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "n",
+                  "type": {
+                    "text": "number"
+                  }
+                }
+              ],
+              "description": "`n` clamped and rounded to the step's precision, as text."
+            },
+            {
+              "kind": "method",
+              "name": "committedText",
+              "privacy": "protected",
+              "return": {
+                "type": {
+                  "text": "string"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "raw",
+                  "type": {
+                    "text": "string"
+                  }
+                }
+              ],
+              "description": "Typed text clamps and rounds when it is a number; otherwise it stays as typed.",
+              "inheritedFrom": {
+                "name": "VfTextControlBase",
+                "module": "src/text-control.ts"
+              }
+            },
             {
               "kind": "method",
               "name": "#commit",
@@ -9983,7 +10094,7 @@
                   }
                 }
               ],
-              "description": "Clamp + round to the step's precision, store, and announce a change — but\nonly when the value actually changes, so autorepeat held against a bound\n(or a keyboard step already at min/max) doesn't fire a redundant\n`vf-change` on every 60ms tick."
+              "description": "Step to `n`, clamped and rounded, and announce a change — but\nonly when the value actually changes, so autorepeat held against a bound\n(or a keyboard step already at min/max) doesn't fire a redundant\n`vf-change` on every 60ms tick."
             },
             {
               "kind": "method",
@@ -10005,8 +10116,8 @@
             },
             {
               "kind": "method",
-              "name": "#emit",
-              "privacy": "private",
+              "name": "emitValue",
+              "privacy": "protected",
               "return": {
                 "type": {
                   "text": "void"
@@ -10018,8 +10129,20 @@
                   "type": {
                     "text": "'vf-input' | 'vf-change'"
                   }
+                },
+                {
+                  "name": "detail",
+                  "default": "{ value: this.value, valueAsNumber: this.#parse() }",
+                  "type": {
+                    "text": "Record<string, unknown>"
+                  }
                 }
-              ]
+              ],
+              "description": "Every value event carries `valueAsNumber` too.",
+              "inheritedFrom": {
+                "name": "VfTextControlBase",
+                "module": "src/text-control.ts"
+              }
             },
             {
               "kind": "method",
@@ -10069,11 +10192,6 @@
               "name": "#onInput",
               "privacy": "private"
             },
-            {
-              "kind": "field",
-              "name": "#onChange",
-              "privacy": "private"
-            },
             {
               "kind": "field",
               "name": "top",
@@ -10186,6 +10304,21 @@
                 "module": "src/text-control.ts"
               }
             },
+            {
+              "kind": "field",
+              "name": "autoselect",
+              "type": {
+                "text": "boolean"
+              },
+              "default": "false",
+              "description": "Opens with the whole text selected, so typing replaces it. Implies\n`autofocus`: the first control carrying either takes the opening focus of\nits `vf-dialog`, or of a window the shell's window manager opens. A dialog\nselects the text on every open, a window on its first open only. A click\nstill places the caret.",
+              "attribute": "autoselect",
+              "reflects": true,
+              "inheritedFrom": {
+                "name": "VfTextControlBase",
+                "module": "src/text-control.ts"
+              }
+            },
             {
               "kind": "field",
               "name": "name",
@@ -10318,6 +10451,71 @@
                 "module": "src/text-control.ts"
               }
             },
+            {
+              "kind": "field",
+              "name": "committed",
+              "type": {
+                "text": "string | null"
+              },
+              "privacy": "protected",
+              "default": "null",
+              "description": "The text as last committed: taken when the field gains focus, then at\neach commit. A commit that brings nothing new isn't announced, so the\nnative `change` that follows a Return commit, or a step, is not a second\none.",
+              "inheritedFrom": {
+                "name": "VfTextControlBase",
+                "module": "src/text-control.ts"
+              }
+            },
+            {
+              "kind": "field",
+              "name": "control",
+              "type": {
+                "text": "HTMLInputElement | HTMLTextAreaElement | null"
+              },
+              "privacy": "protected",
+              "description": "The inner native control every field renders, tagged `vf-field`.",
+              "readonly": true,
+              "inheritedFrom": {
+                "name": "VfTextControlBase",
+                "module": "src/text-control.ts"
+              }
+            },
+            {
+              "kind": "method",
+              "name": "focus",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "options",
+                  "optional": true,
+                  "type": {
+                    "text": "FocusOptions"
+                  }
+                }
+              ],
+              "description": "Focuses the inner control, keeping its caret where it was. Chromium\nselects all of an input's text when the host hands the focus on, as a Tab\ndoes; `select()` and autoselect are how a field opens selected.",
+              "inheritedFrom": {
+                "name": "VfTextControlBase",
+                "module": "src/text-control.ts"
+              }
+            },
+            {
+              "kind": "method",
+              "name": "select",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "description": "Select all of the field's text, as a native field's `select()` does. With\na new value not yet rendered, once it has: writing the value into the\ninput drops its selection, so `field.value = x; field.select()` selects\n`x`, as on a native field.",
+              "inheritedFrom": {
+                "name": "VfTextControlBase",
+                "module": "src/text-control.ts"
+              }
+            },
             {
               "kind": "method",
               "name": "formResetCallback",
@@ -10372,7 +10570,7 @@
             },
             {
               "kind": "method",
-              "name": "emitValue",
+              "name": "handleInput",
               "privacy": "protected",
               "return": {
                 "type": {
@@ -10381,20 +10579,36 @@
               },
               "parameters": [
                 {
-                  "name": "type",
+                  "name": "event",
                   "type": {
-                    "text": "'vf-input' | 'vf-change'"
+                    "text": "Event"
                   }
-                },
+                }
+              ],
+              "description": "Mirror the native control's value into `value` and announce a keystroke.",
+              "inheritedFrom": {
+                "name": "VfTextControlBase",
+                "module": "src/text-control.ts"
+              }
+            },
+            {
+              "kind": "method",
+              "name": "commit",
+              "privacy": "protected",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "parameters": [
                 {
-                  "name": "detail",
-                  "default": "{ value: this.value }",
+                  "name": "raw",
                   "type": {
-                    "text": "Record<string, unknown>"
+                    "text": "string"
                   }
                 }
               ],
-              "description": "Dispatch a bubbling, composed value event (SPEC §4). Text fields use the\ndefault `{ value }` detail; `vf-number-field` passes an enriched detail that\nalso carries `valueAsNumber`.",
+              "description": "Commit typed text: its committed form into `value`, announced unless it is what was last committed.",
               "inheritedFrom": {
                 "name": "VfTextControlBase",
                 "module": "src/text-control.ts"
@@ -10402,7 +10616,7 @@
             },
             {
               "kind": "method",
-              "name": "handleInput",
+              "name": "handleChange",
               "privacy": "protected",
               "return": {
                 "type": {
@@ -10417,7 +10631,7 @@
                   }
                 }
               ],
-              "description": "Mirror the native control's value into `value` and announce a keystroke.",
+              "description": "The native control's commit.",
               "inheritedFrom": {
                 "name": "VfTextControlBase",
                 "module": "src/text-control.ts"
@@ -10425,7 +10639,7 @@
             },
             {
               "kind": "method",
-              "name": "handleChange",
+              "name": "submitOnEnter",
               "privacy": "protected",
               "return": {
                 "type": {
@@ -10436,11 +10650,11 @@
                 {
                   "name": "event",
                   "type": {
-                    "text": "Event"
+                    "text": "KeyboardEvent"
                   }
                 }
               ],
-              "description": "Mirror the native control's value into `value` and announce a commit.",
+              "description": "A plain Return in a single-line field with a form: commit, then the\nform's implicit submission, the order a native input keeps (its `change`\ncomes before the submission). The keydown is cancelled, so an enclosing\nmodal does not route the same press to its default button as well.",
               "inheritedFrom": {
                 "name": "VfTextControlBase",
                 "module": "src/text-control.ts"
@@ -11105,6 +11319,19 @@
                 "module": "src/text-control.ts"
               }
             },
+            {
+              "name": "autoselect",
+              "type": {
+                "text": "boolean"
+              },
+              "default": "false",
+              "description": "Opens with the whole text selected, so typing replaces it. Implies\n`autofocus`: the first control carrying either takes the opening focus of\nits `vf-dialog`, or of a window the shell's window manager opens. A dialog\nselects the text on every open, a window on its first open only. A click\nstill places the caret.",
+              "fieldName": "autoselect",
+              "inheritedFrom": {
+                "name": "VfTextControlBase",
+                "module": "src/text-control.ts"
+              }
+            },
             {
               "name": "name",
               "type": {
@@ -11498,7 +11725,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "`<vf-paragraph>` — a paragraph of copy on the kit's body face and grid.\n\nThe installer's welcome text, a dialog's explanation, an article's prose:\nanything a page would otherwise set with a `<p>` and hope the leading landed\nsomewhere sensible. What it adds over that `<p>`:\n\n- the **Geneva body face** by default (`face=\"display\"` switches to\n  the Chicago-style chrome face);\n- a **whole-system-pixel line box at the face's native pitch** —\n  `--vf-paragraph-line-height`: 12px for the body face (Geneva 9's own\n  strike line) and 16px under `face=\"display\"` (Chicago 12's — ascent 12 +\n  descent 3 + leading 1, the pitch a real dialog wrapped its copy on).\n  Whole pixels are the point of the component: line boxes are the single\n  biggest source of off-grid layout, because a ratio resolves to whatever\n  it resolves to (`1.65 × 17px = 28.05px`) and every line of prose nudges\n  everything after it further off the device-pixel grid, smearing 1-bit\n  borders and bitmap glyph stems (docs/SIZING.md rule 2). A\n  whole-pixel line box accumulates whole offsets;\n- its own GridSnapController, so it holds its own origin\n  wherever the page puts it;\n- a **declared box** when the layout wants one — `width`/`height` in whole\n  system px (VfSized). In flow a paragraph takes its container's\n  width, which is usually right; a *placed* one (`top`/`left`) shrink-wraps\n  its longest line instead — a fractional glyph-run width, wrapped wherever\n  the parent's edge happens to fall — so a DITL-style layout states the\n  measure the copy wraps to, whole and on the grid.\n\nThe shadow root renders a real `<p>`, so the copy keeps paragraph semantics\nfor assistive tech, and — unlike the kit's chrome — the text is selectable.\nThere is no margin: per SPEC §2 a component adds nothing outside its own box,\nso paragraph spacing is the page's (a `gap` on the column, or a margin on the\nhost — kept a whole number of pixels, like everything else in the contract).",
+          "description": "`<vf-paragraph>` — a paragraph of copy on the kit's body face and grid.\n\nThe installer's welcome text, a dialog's explanation, an article's prose:\nanything a page would otherwise set with a `<p>` and hope the leading landed\nsomewhere sensible. What it adds over that `<p>`:\n\n- the **Geneva body face** by default (`face=\"display\"` switches to\n  the Chicago-style chrome face);\n- a **whole-system-pixel line box at the face's native pitch** —\n  `--vf-paragraph-line-height`: 12px for the body face (Geneva 9's own\n  strike line) and 16px under `face=\"display\"` (Chicago 12's — ascent 12 +\n  descent 3 + leading 1, the pitch a real dialog wrapped its copy on).\n  Whole pixels are the point of the component: line boxes are the single\n  biggest source of off-grid layout, because a ratio resolves to whatever\n  it resolves to (`1.65 × 17px = 28.05px`) and every line of prose nudges\n  everything after it further off the device-pixel grid, smearing 1-bit\n  borders and bitmap glyph stems (docs/SIZING.md rule 2). A\n  whole-pixel line box accumulates whole offsets;\n- its own GridSnapController, so it holds its own origin\n  wherever the page puts it;\n- a **declared box** when the layout wants one — `width`/`height` in whole\n  system px (VfSized). In flow a paragraph takes its container's\n  width, which is usually right; a *placed* one (`top`/`left`) shrink-wraps\n  its longest line instead — a fractional glyph-run width, wrapped wherever\n  the parent's edge happens to fall — so a DITL-style layout states the\n  measure the copy wraps to, whole and on the grid.\n\nThe shadow root renders a real `<p>`, so the copy keeps paragraph semantics\nfor assistive tech, and — unlike the kit's chrome — the text is selectable,\nselected text inverting to the 1-bit highlight (`--vf-highlight` /\n`--vf-highlight-text`) as a field's does.\nThere is no margin: per SPEC §2 a component adds nothing outside its own box,\nso paragraph spacing is the page's (a `gap` on the column, or a margin on the\nhost — kept a whole number of pixels, like everything else in the contract).",
           "name": "VfParagraph",
           "cssProperties": [
             {
@@ -13397,7 +13624,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "`<vf-scroll-area>` — a container whose scrollbars look like System 7.\n\nWhite box with a 1px black frame, an inner scrolling viewport, and scroll\nrails the kit draws itself as shadow DOM (the shared `vfScrollRail` recipe):\nboxed arrow buttons at each end, a loose 1-bit dot-dither trough, and the\nclassic fixed 16px thumb. The native scrollbar is hidden, never the native\nscrolling — wheel, trackpad momentum, keyboard, touch and assistive-tech\nscrolling stay the platform's, and ScrollRailController keeps the\nrail in sync while driving the classic interactions (thumb drag, trough\npaging, arrow stepping with auto-repeat). Every engine renders the same\nrail — there is no Firefox fallback skin anymore.\n\nEach reserved scroll rail is a permanent placeholder: arrow buttons on an\nempty white channel sit in the gutter even when the content fits, the\ndither and thumb filling in only once that axis overflows (System 7 drew\nan active window's no-overflow bar as arrows on a bare channel; driven\nby ScrollStateController). Which rails are reserved is set by\naxis; when both are reserved the bottom-right corner joins them,\nand corner reserves that cell on a single-axis rail too — the\nrail stops 15px short of the frame, for a grow box to land in.\n\nSize the host (width/height) from the outside; the viewport fills it.\nContent runs to the frame and the rails — the area adds no inset of its\nown; an inset is the content's (a `vf-stack pad`).\n\nThe scrolled plane sizes to its content — never narrower than the\nviewport, as wide as content that cannot wrap — so the rails follow a row\nthat grows sideways the way they follow copy that grows down, and a\n`slotchange` re-measures. A placed child moved through `top`/`left` is\nheard too: every such write is announced as `vf-placement-change`\n(src/position.ts), and the area re-measures on it — a drop, an arrow\nnudge, a page's own `icon.left = …`, with no code on the page. * measure covers a scroll range that changes with no box and no placement\nchanging (a transform).\n\nplacementAt converts a viewport point into the plane's own\nplacement coordinates, for a drop that lands in this area from elsewhere.",
+          "description": "`<vf-scroll-area>` — a container whose scrollbars look like System 7.\n\nWhite box with a 1px black frame, an inner scrolling viewport, and scroll\nrails the kit draws itself as shadow DOM (the shared `vfScrollRail` recipe):\nboxed arrow buttons at each end, a loose 1-bit dot-dither trough, and the\nclassic fixed 16px thumb. The native scrollbar is hidden, never the native\nscrolling — wheel, trackpad momentum, keyboard, touch and assistive-tech\nscrolling stay the platform's, and ScrollRailController keeps the\nrail in sync while driving the classic interactions (thumb drag, trough\npaging, arrow stepping with auto-repeat). Every engine renders the same\nrail — there is no Firefox fallback skin anymore.\n\nEach reserved scroll rail is a permanent placeholder: arrow buttons on an\nempty white channel sit in the gutter even when the content fits, the\ndither and thumb filling in only once that axis overflows (System 7 drew\nan active window's no-overflow bar as arrows on a bare channel; driven\nby ScrollStateController). Which rails are reserved is set by\naxis; when both are reserved the bottom-right corner joins them,\nand corner reserves that cell on a single-axis rail too — the\nrail stops 15px short of the frame, for a grow box to land in.\n\nSize the host (width/height) from the outside; the viewport fills it.\nContent runs to the frame and the rails — the area adds no inset of its\nown; an inset is the content's (a `vf-stack pad`). `pattern` fills the\nscrolled plane with a 1-bit pattern, as on `vf-container`.\n\nThe scrolled plane sizes to its content — never narrower than the\nviewport, as wide as content that cannot wrap — so the rails follow a row\nthat grows sideways the way they follow copy that grows down, and a\n`slotchange` re-measures. A placed child moved through `top`/`left` is\nheard too: every such write is announced as `vf-placement-change`\n(src/position.ts), and the area re-measures on it — a drop, an arrow\nnudge, a page's own `icon.left = …`, with no code on the page. * measure covers a scroll range that changes with no box and no placement\nchanging (a transform).\n\nplacementAt converts a viewport point into the plane's own\nplacement coordinates, for a drop that lands in this area from elsewhere.",
           "name": "VfScrollArea",
           "cssProperties": [
             {
@@ -13471,27 +13698,64 @@
             },
             {
               "kind": "field",
-              "name": "viewport",
+              "name": "pattern",
               "type": {
-                "text": "HTMLElement | null"
+                "text": "string | null | undefined"
               },
-              "privacy": "private"
+              "description": "A 1-bit fill for the scrolled plane, as on `vf-container`: a library\npattern by name (docs/PATTERNS.md) or sixteen hex digits. It fills the\nvisible area, runs on past the content, and scrolls with it, its phase\nanchored at the content's top-left. Unset, the plane stays white; an\nunrecognized value paints nothing and warns once.",
+              "attribute": "pattern"
             },
             {
               "kind": "field",
-              "name": "content",
+              "name": "_pattern",
               "type": {
-                "text": "HTMLElement | null"
+                "text": "Pattern | null"
               },
-              "privacy": "private"
-            },
-            {
-              "kind": "field",
-              "name": "scrollState",
               "privacy": "private",
-              "readonly": true,
-              "default": "new ScrollStateController( this, () => this.viewport, () => this.content, (overflow) => { this._scrollable = overflow.x || overflow.y } )",
-              "description": "Reports overflow per axis so the reserved rail(s) activate on overflow."
+              "default": "null",
+              "description": "`pattern`, resolved — what the fill paints; null paints nothing."
+            },
+            {
+              "kind": "field",
+              "name": "#warnedPattern",
+              "privacy": "private",
+              "type": {
+                "text": "boolean"
+              },
+              "default": "false",
+              "description": "One warning per element for an unrecognized `pattern`, not per render."
+            },
+            {
+              "kind": "field",
+              "name": "viewport",
+              "type": {
+                "text": "HTMLElement | null"
+              },
+              "privacy": "private"
+            },
+            {
+              "kind": "field",
+              "name": "content",
+              "type": {
+                "text": "HTMLElement | null"
+              },
+              "privacy": "private"
+            },
+            {
+              "kind": "field",
+              "name": "patternFill",
+              "privacy": "private",
+              "readonly": true,
+              "default": "new PatternFillController(this, { getBox: () => this.content, getPattern: () => this._pattern, })",
+              "description": "The pattern fill, painted on the scrolled plane (src/pattern-fill.ts)."
+            },
+            {
+              "kind": "field",
+              "name": "scrollState",
+              "privacy": "private",
+              "readonly": true,
+              "default": "new ScrollStateController( this, () => this.viewport, () => this.content, (overflow) => { this._scrollable = overflow.x || overflow.y } )",
+              "description": "Reports overflow per axis so the reserved rail(s) activate on overflow."
             },
             {
               "kind": "field",
@@ -13671,6 +13935,14 @@
               "description": "Accessible name for the scrolling viewport, applied as its `aria-label`\n(an `aria-label` on the host would not reach into the shadow DOM). The\nviewport is keyboard-focusable while its content overflows, so without a\nname it is announced only as an anonymous scrollable group; setting\n`label` also promotes it to a named `role=\"region\"` landmark. While\n`label` is empty the viewport is a plain `group` when scrollable (an\nunnamed region is inert) and role-less when not.",
               "fieldName": "label"
             },
+            {
+              "name": "pattern",
+              "type": {
+                "text": "string | null | undefined"
+              },
+              "description": "A 1-bit fill for the scrolled plane, as on `vf-container`: a library\npattern by name (docs/PATTERNS.md) or sixteen hex digits. It fills the\nvisible area, runs on past the content, and scrolls with it, its phase\nanchored at the content's top-left. Unset, the plane stays white; an\nunrecognized value paints nothing and warns once.",
+              "fieldName": "pattern"
+            },
             {
               "name": "top",
               "type": {
@@ -13760,7 +14032,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "`<vf-select>` — the classic System 7 popup menu control (\"Macintosh HD ▼\").\n\nChildren are `<vf-option>` elements in the default slot. The closed control\nis a white box with a 1px black border, the small 1px hard shadow, the\nselected option's label on the left and a solid black ▼ triangle on the\nright. The open panel uses the shared `.vf-panel` recipe and is positioned\n`position: fixed` (computed from `getBoundingClientRect()`) so it escapes\nclipping containers; when possible the currently-selected item opens\ndirectly over the control, like the real popup menu.\n\nPointer — two interaction styles are supported and disambiguated by the\ngesture itself, resolved at the first pointer release:\n  - System 7 press-drag-release: press the pill (the list appears under the\n    pointer), drag onto an item, release over it to pick — one continuous\n    press. Releasing over the current item or off the list closes with no\n    change.\n  - Modern click-to-open: a quick in-place click (no drag, released within\n    PRESS_HOLD_MS) leaves the list open; a second, independent click\n    then picks an item.\nThe two share one opening trigger (pointerdown) and diverge only on how the\npress ends — whether the pointer travelled to another item, and (for an\nin-place release) whether it was a quick tap or a held press. The pull-down\nmenus drive themselves the same way, on the same threshold; that half lives\nin src/menu-press.ts, because one menu press may travel across a whole bar.\n\nA list too tall for the screen is **clipped**, never scrolled: the edge slot\nwith items beyond it shows a solid arrow instead of a row, which rolls the\nlist one row at a time while the pointer rests on it. The clamp is quantized\nto the pill lattice, so a clipped popup still opens with its selected row\nover the closed pill — and the panel keeps every slot the list asked for, so\na box that had to slide to fit the screen opens with *blank rows* at whichever\nend the list no longer reaches: the exact travel it will roll through, in\neither direction. See src/popup-overflow.ts.\n\n`size=\"small\"` sets the pill and its rows in the body face: a 12px pill\n(`--vf-popup-height-small`) over 10px rows, the baseline 8 rows down so the\nface's 2-row descenders end on the last content row. Its ▼ and scroll\narrows are the 9×5 `CARET_DOWN_SMALL` / `CARET_UP_SMALL`; the ✓ and the\nhorizontal insets are the regular pill's. Marks above a capital (É, Å, Ñ)\nreach past the 8 rows above the baseline and are clipped.\n\n`no-shadow` draws the closed pill without its 1px hard shadow, and the focus\nrule moves up the row the shadow took. The open list keeps its shadow.\n\nKeyboard: Space/Enter/ArrowDown open; while open ArrowUp/ArrowDown move the\nhighlight, Home/End jump, Enter/Space select, Escape cancels. Selecting an\nitem plays the classic inversion blink (~250 ms) before closing. Keyboard\nfocus is marked with the kit's 1px dashed rule under the closed pill\n(`vfFocusUnderline`) rather than a ring around it — keyboard only, which\nhere means the page's input modality rather than `:focus-visible` (the pill\ndrives its own focus, and Blink reads that as visible either way).\n\nForm-associated: submits `value` under `name`.",
+          "description": "`<vf-select>` — the classic System 7 popup menu control (\"Macintosh HD ▼\").\n\nChildren are `<vf-option>` elements in the default slot. The closed control\nis a white box with a 1px black border, the small 1px hard shadow, the\nselected option's label on the left and a solid black ▼ triangle on the\nright. The open panel uses the shared `.vf-panel` recipe and is a manual\npopover in the top layer, positioned `position: fixed` (computed from\n`getBoundingClientRect()`), so it escapes clipping containers and paints\nover every window, palettes included; when possible the currently-selected\nitem opens directly over the control, like the real popup menu.\n\nPointer — two interaction styles are supported and disambiguated by the\ngesture itself, resolved at the first pointer release:\n  - System 7 press-drag-release: press the pill (the list appears under the\n    pointer), drag onto an item, release over it to pick — one continuous\n    press. Releasing over the current item or off the list closes with no\n    change.\n  - Modern click-to-open: a quick in-place click (no drag, released within\n    PRESS_HOLD_MS) leaves the list open; a second, independent click\n    then picks an item.\nThe two share one opening trigger (pointerdown) and diverge only on how the\npress ends — whether the pointer travelled to another item, and (for an\nin-place release) whether it was a quick tap or a held press. The pull-down\nmenus drive themselves the same way, on the same threshold; that half lives\nin src/menu-press.ts, because one menu press may travel across a whole bar.\n\nA list too tall for the screen is **clipped**, never scrolled: the edge slot\nwith items beyond it shows a solid arrow instead of a row, which rolls the\nlist one row at a time while the pointer rests on it. The clamp is quantized\nto the pill lattice, so a clipped popup still opens with its selected row\nover the closed pill — and the panel keeps every slot the list asked for, so\na box that had to slide to fit the screen opens with *blank rows* at whichever\nend the list no longer reaches: the exact travel it will roll through, in\neither direction. See src/popup-overflow.ts.\n\n`size=\"small\"` sets the pill and its rows in the body face: a 12px pill\n(`--vf-popup-height-small`) over 10px rows, the baseline 8 rows down so the\nface's 2-row descenders end on the last content row. Its ▼ and scroll\narrows are the 9×5 `CARET_DOWN_SMALL` / `CARET_UP_SMALL`; the ✓ and the\nhorizontal insets are the regular pill's. Marks above a capital (É, Å, Ñ)\nreach past the 8 rows above the baseline and are clipped.\n\n`no-shadow` draws the closed pill without its 1px hard shadow, and the focus\nrule moves up the row the shadow took. The open list keeps its shadow.\n\nKeyboard: Space/Enter/ArrowDown open; while open ArrowUp/ArrowDown move the\nhighlight, Home/End jump, Enter/Space select, Escape cancels. Selecting an\nitem plays the classic inversion blink (~250 ms) before closing. Keyboard\nfocus is marked with the kit's 1px dashed rule under the closed pill\n(`vfFocusUnderline`) rather than a ring around it — keyboard only, which\nhere means the page's input modality rather than `:focus-visible` (the pill\ndrives its own focus, and Blink reads that as visible either way).\n\nForm-associated: submits `value` under `name`.",
           "name": "VfSelect",
           "cssProperties": [
             {
@@ -18132,6 +18404,21 @@
                 "module": "src/text-control.ts"
               }
             },
+            {
+              "kind": "field",
+              "name": "autoselect",
+              "type": {
+                "text": "boolean"
+              },
+              "default": "false",
+              "description": "Opens with the whole text selected, so typing replaces it. Implies\n`autofocus`: the first control carrying either takes the opening focus of\nits `vf-dialog`, or of a window the shell's window manager opens. A dialog\nselects the text on every open, a window on its first open only. A click\nstill places the caret.",
+              "attribute": "autoselect",
+              "reflects": true,
+              "inheritedFrom": {
+                "name": "VfTextControlBase",
+                "module": "src/text-control.ts"
+              }
+            },
             {
               "kind": "field",
               "name": "name",
@@ -18264,6 +18551,71 @@
                 "module": "src/text-control.ts"
               }
             },
+            {
+              "kind": "field",
+              "name": "committed",
+              "type": {
+                "text": "string | null"
+              },
+              "privacy": "protected",
+              "default": "null",
+              "description": "The text as last committed: taken when the field gains focus, then at\neach commit. A commit that brings nothing new isn't announced, so the\nnative `change` that follows a Return commit, or a step, is not a second\none.",
+              "inheritedFrom": {
+                "name": "VfTextControlBase",
+                "module": "src/text-control.ts"
+              }
+            },
+            {
+              "kind": "field",
+              "name": "control",
+              "type": {
+                "text": "HTMLInputElement | HTMLTextAreaElement | null"
+              },
+              "privacy": "protected",
+              "description": "The inner native control every field renders, tagged `vf-field`.",
+              "readonly": true,
+              "inheritedFrom": {
+                "name": "VfTextControlBase",
+                "module": "src/text-control.ts"
+              }
+            },
+            {
+              "kind": "method",
+              "name": "focus",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "options",
+                  "optional": true,
+                  "type": {
+                    "text": "FocusOptions"
+                  }
+                }
+              ],
+              "description": "Focuses the inner control, keeping its caret where it was. Chromium\nselects all of an input's text when the host hands the focus on, as a Tab\ndoes; `select()` and autoselect are how a field opens selected.",
+              "inheritedFrom": {
+                "name": "VfTextControlBase",
+                "module": "src/text-control.ts"
+              }
+            },
+            {
+              "kind": "method",
+              "name": "select",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "description": "Select all of the field's text, as a native field's `select()` does. With\na new value not yet rendered, once it has: writing the value into the\ninput drops its selection, so `field.value = x; field.select()` selects\n`x`, as on a native field.",
+              "inheritedFrom": {
+                "name": "VfTextControlBase",
+                "module": "src/text-control.ts"
+              }
+            },
             {
               "kind": "method",
               "name": "formResetCallback",
@@ -18346,6 +18698,52 @@
                 "module": "src/text-control.ts"
               }
             },
+            {
+              "kind": "method",
+              "name": "committedText",
+              "privacy": "protected",
+              "return": {
+                "type": {
+                  "text": "string"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "raw",
+                  "type": {
+                    "text": "string"
+                  }
+                }
+              ],
+              "description": "The committed form of typed text: as typed here; `vf-number-field` clamps and rounds it.",
+              "inheritedFrom": {
+                "name": "VfTextControlBase",
+                "module": "src/text-control.ts"
+              }
+            },
+            {
+              "kind": "method",
+              "name": "commit",
+              "privacy": "protected",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "raw",
+                  "type": {
+                    "text": "string"
+                  }
+                }
+              ],
+              "description": "Commit typed text: its committed form into `value`, announced unless it is what was last committed.",
+              "inheritedFrom": {
+                "name": "VfTextControlBase",
+                "module": "src/text-control.ts"
+              }
+            },
             {
               "kind": "method",
               "name": "handleChange",
@@ -18363,7 +18761,30 @@
                   }
                 }
               ],
-              "description": "Mirror the native control's value into `value` and announce a commit.",
+              "description": "The native control's commit.",
+              "inheritedFrom": {
+                "name": "VfTextControlBase",
+                "module": "src/text-control.ts"
+              }
+            },
+            {
+              "kind": "method",
+              "name": "submitOnEnter",
+              "privacy": "protected",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "event",
+                  "type": {
+                    "text": "KeyboardEvent"
+                  }
+                }
+              ],
+              "description": "A plain Return in a single-line field with a form: commit, then the\nform's implicit submission, the order a native input keeps (its `change`\ncomes before the submission). The keydown is cancelled, so an enclosing\nmodal does not route the same press to its default button as well.",
               "inheritedFrom": {
                 "name": "VfTextControlBase",
                 "module": "src/text-control.ts"
@@ -19012,6 +19433,19 @@
                 "module": "src/text-control.ts"
               }
             },
+            {
+              "name": "autoselect",
+              "type": {
+                "text": "boolean"
+              },
+              "default": "false",
+              "description": "Opens with the whole text selected, so typing replaces it. Implies\n`autofocus`: the first control carrying either takes the opening focus of\nits `vf-dialog`, or of a window the shell's window manager opens. A dialog\nselects the text on every open, a window on its first open only. A click\nstill places the caret.",
+              "fieldName": "autoselect",
+              "inheritedFrom": {
+                "name": "VfTextControlBase",
+                "module": "src/text-control.ts"
+              }
+            },
             {
               "name": "name",
               "type": {
@@ -19186,7 +19620,7 @@
                   }
                 }
               ],
-              "description": "Enter in a single-line field triggers the associated form's implicit\nsubmission. The native `<input>` is shadow-encapsulated, so its form owner\nis null and the browser won't do this itself. A press the form took is\ncancelled, so an enclosing modal does not route it again."
+              "description": "Enter in a single-line field commits, then triggers the associated\nform's implicit submission. The native `<input>` is shadow-encapsulated,\nso its form owner is null and the browser won't do this itself."
             },
             {
               "kind": "field",
@@ -19300,6 +19734,21 @@
                 "module": "src/text-control.ts"
               }
             },
+            {
+              "kind": "field",
+              "name": "autoselect",
+              "type": {
+                "text": "boolean"
+              },
+              "default": "false",
+              "description": "Opens with the whole text selected, so typing replaces it. Implies\n`autofocus`: the first control carrying either takes the opening focus of\nits `vf-dialog`, or of a window the shell's window manager opens. A dialog\nselects the text on every open, a window on its first open only. A click\nstill places the caret.",
+              "attribute": "autoselect",
+              "reflects": true,
+              "inheritedFrom": {
+                "name": "VfTextControlBase",
+                "module": "src/text-control.ts"
+              }
+            },
             {
               "kind": "field",
               "name": "name",
@@ -19417,37 +19866,51 @@
               }
             },
             {
-              "kind": "method",
-              "name": "formResetCallback",
-              "return": {
-                "type": {
-                  "text": "void"
-                }
+              "kind": "field",
+              "name": "committed",
+              "type": {
+                "text": "string | null"
               },
-              "description": "Restores the initial value when the associated form resets.",
+              "privacy": "protected",
+              "default": "null",
+              "description": "The text as last committed: taken when the field gains focus, then at\neach commit. A commit that brings nothing new isn't announced, so the\nnative `change` that follows a Return commit, or a step, is not a second\none.",
               "inheritedFrom": {
                 "name": "VfTextControlBase",
                 "module": "src/text-control.ts"
               }
             },
             {
-              "kind": "method",
-              "name": "isSubmitEnter",
+              "kind": "field",
+              "name": "control",
+              "type": {
+                "text": "HTMLInputElement | HTMLTextAreaElement | null"
+              },
               "privacy": "protected",
+              "description": "The inner native control every field renders, tagged `vf-field`.",
+              "readonly": true,
+              "inheritedFrom": {
+                "name": "VfTextControlBase",
+                "module": "src/text-control.ts"
+              }
+            },
+            {
+              "kind": "method",
+              "name": "focus",
               "return": {
                 "type": {
-                  "text": "boolean"
+                  "text": "void"
                 }
               },
               "parameters": [
                 {
-                  "name": "event",
+                  "name": "options",
+                  "optional": true,
                   "type": {
-                    "text": "KeyboardEvent"
+                    "text": "FocusOptions"
                   }
                 }
               ],
-              "description": "True for a plain Enter press (no modifiers, not IME-composing) — the key\nthat triggers a form's implicit submission. The native control is\nshadow-encapsulated (null form owner), so single-line fields call\n`internals.form?.requestSubmit()` themselves; this centralises the guard.",
+              "description": "Focuses the inner control, keeping its caret where it was. Chromium\nselects all of an input's text when the host hands the focus on, as a Tab\ndoes; `select()` and autoselect are how a field opens selected.",
               "inheritedFrom": {
                 "name": "VfTextControlBase",
                 "module": "src/text-control.ts"
@@ -19455,14 +19918,13 @@
             },
             {
               "kind": "method",
-              "name": "requestImplicitSubmit",
-              "privacy": "protected",
+              "name": "select",
               "return": {
                 "type": {
-                  "text": "boolean"
+                  "text": "void"
                 }
               },
-              "description": "Emulates the form's implicit submission for a plain Enter press. HTML\ndefines it as *activating the form's default button* — the first submit\nbutton in tree order — so the submission carries that button's submitter\nidentity and name/value. A bare `requestSubmit()` carries neither\n(`event.submitter === null`), which made Enter and a click on the same\nform produce different payloads. `click()` is the activation: a native\nbutton becomes the real submitter, and a `vf-button` forwards it to its\ninner button, which runs the same transient-proxy path a pointer does. A\ndisabled default button means no submission at all, as in HTML; a form\nwith no submit button falls back to the bare call, also as in HTML.\n\nOne departure: a submit `vf-button variant=\"default\"`, the button with\nthe ring, is the default button when the form has one, ahead of the\nfirst in tree order. A Cancel/OK row puts Cancel first, and Return\nshould press the button the ring marks — the one a modal's own Return\nrule presses (`VfModalDialog`).\n\nReturns whether a form owner took the press — true even when a disabled\ndefault button meant no submission, since HTML gave the press to the form\neither way. The callers cancel the keydown on true, so a modal shell\n(`VfModalDialog`) sees the press as spoken for and does not also route it\nto the dialog's default button; with no form the press goes on to the\ndialog untouched.",
+              "description": "Select all of the field's text, as a native field's `select()` does. With\na new value not yet rendered, once it has: writing the value into the\ninput drops its selection, so `field.value = x; field.select()` selects\n`x`, as on a native field.",
               "inheritedFrom": {
                 "name": "VfTextControlBase",
                 "module": "src/text-control.ts"
@@ -19470,25 +19932,77 @@
             },
             {
               "kind": "method",
-              "name": "emitValue",
-              "privacy": "protected",
+              "name": "formResetCallback",
               "return": {
                 "type": {
                   "text": "void"
                 }
               },
-              "parameters": [
-                {
-                  "name": "type",
-                  "type": {
-                    "text": "'vf-input' | 'vf-change'"
-                  }
-                },
-                {
-                  "name": "detail",
-                  "default": "{ value: this.value }",
-                  "type": {
-                    "text": "Record<string, unknown>"
+              "description": "Restores the initial value when the associated form resets.",
+              "inheritedFrom": {
+                "name": "VfTextControlBase",
+                "module": "src/text-control.ts"
+              }
+            },
+            {
+              "kind": "method",
+              "name": "isSubmitEnter",
+              "privacy": "protected",
+              "return": {
+                "type": {
+                  "text": "boolean"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "event",
+                  "type": {
+                    "text": "KeyboardEvent"
+                  }
+                }
+              ],
+              "description": "True for a plain Enter press (no modifiers, not IME-composing) — the key\nthat triggers a form's implicit submission. The native control is\nshadow-encapsulated (null form owner), so single-line fields call\n`internals.form?.requestSubmit()` themselves; this centralises the guard.",
+              "inheritedFrom": {
+                "name": "VfTextControlBase",
+                "module": "src/text-control.ts"
+              }
+            },
+            {
+              "kind": "method",
+              "name": "requestImplicitSubmit",
+              "privacy": "protected",
+              "return": {
+                "type": {
+                  "text": "boolean"
+                }
+              },
+              "description": "Emulates the form's implicit submission for a plain Enter press. HTML\ndefines it as *activating the form's default button* — the first submit\nbutton in tree order — so the submission carries that button's submitter\nidentity and name/value. A bare `requestSubmit()` carries neither\n(`event.submitter === null`), which made Enter and a click on the same\nform produce different payloads. `click()` is the activation: a native\nbutton becomes the real submitter, and a `vf-button` forwards it to its\ninner button, which runs the same transient-proxy path a pointer does. A\ndisabled default button means no submission at all, as in HTML; a form\nwith no submit button falls back to the bare call, also as in HTML.\n\nOne departure: a submit `vf-button variant=\"default\"`, the button with\nthe ring, is the default button when the form has one, ahead of the\nfirst in tree order. A Cancel/OK row puts Cancel first, and Return\nshould press the button the ring marks — the one a modal's own Return\nrule presses (`VfModalDialog`).\n\nReturns whether a form owner took the press — true even when a disabled\ndefault button meant no submission, since HTML gave the press to the form\neither way. The callers cancel the keydown on true, so a modal shell\n(`VfModalDialog`) sees the press as spoken for and does not also route it\nto the dialog's default button; with no form the press goes on to the\ndialog untouched.",
+              "inheritedFrom": {
+                "name": "VfTextControlBase",
+                "module": "src/text-control.ts"
+              }
+            },
+            {
+              "kind": "method",
+              "name": "emitValue",
+              "privacy": "protected",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "type",
+                  "type": {
+                    "text": "'vf-input' | 'vf-change'"
+                  }
+                },
+                {
+                  "name": "detail",
+                  "default": "{ value: this.value }",
+                  "type": {
+                    "text": "Record<string, unknown>"
                   }
                 }
               ],
@@ -19521,6 +20035,52 @@
                 "module": "src/text-control.ts"
               }
             },
+            {
+              "kind": "method",
+              "name": "committedText",
+              "privacy": "protected",
+              "return": {
+                "type": {
+                  "text": "string"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "raw",
+                  "type": {
+                    "text": "string"
+                  }
+                }
+              ],
+              "description": "The committed form of typed text: as typed here; `vf-number-field` clamps and rounds it.",
+              "inheritedFrom": {
+                "name": "VfTextControlBase",
+                "module": "src/text-control.ts"
+              }
+            },
+            {
+              "kind": "method",
+              "name": "commit",
+              "privacy": "protected",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "raw",
+                  "type": {
+                    "text": "string"
+                  }
+                }
+              ],
+              "description": "Commit typed text: its committed form into `value`, announced unless it is what was last committed.",
+              "inheritedFrom": {
+                "name": "VfTextControlBase",
+                "module": "src/text-control.ts"
+              }
+            },
             {
               "kind": "method",
               "name": "handleChange",
@@ -19538,7 +20098,30 @@
                   }
                 }
               ],
-              "description": "Mirror the native control's value into `value` and announce a commit.",
+              "description": "The native control's commit.",
+              "inheritedFrom": {
+                "name": "VfTextControlBase",
+                "module": "src/text-control.ts"
+              }
+            },
+            {
+              "kind": "method",
+              "name": "submitOnEnter",
+              "privacy": "protected",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "event",
+                  "type": {
+                    "text": "KeyboardEvent"
+                  }
+                }
+              ],
+              "description": "A plain Return in a single-line field with a form: commit, then the\nform's implicit submission, the order a native input keeps (its `change`\ncomes before the submission). The keydown is cancelled, so an enclosing\nmodal does not route the same press to its default button as well.",
               "inheritedFrom": {
                 "name": "VfTextControlBase",
                 "module": "src/text-control.ts"
@@ -20077,7 +20660,7 @@
               "name": "vf-input"
             },
             {
-              "description": "On commit (native `change`). `detail: { value: string }`.",
+              "description": "On commit: the native `change`, leaving the field, or Return in a form, before its submission. `detail: { value: string }`.",
               "name": "vf-change"
             },
             {
@@ -20187,6 +20770,19 @@
                 "module": "src/text-control.ts"
               }
             },
+            {
+              "name": "autoselect",
+              "type": {
+                "text": "boolean"
+              },
+              "default": "false",
+              "description": "Opens with the whole text selected, so typing replaces it. Implies\n`autofocus`: the first control carrying either takes the opening focus of\nits `vf-dialog`, or of a window the shell's window manager opens. A dialog\nselects the text on every open, a window on its first open only. A click\nstill places the caret.",
+              "fieldName": "autoselect",
+              "inheritedFrom": {
+                "name": "VfTextControlBase",
+                "module": "src/text-control.ts"
+              }
+            },
             {
               "name": "name",
               "type": {
@@ -20292,7 +20888,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "`<vf-window>` — the System 7 desktop-window shell.\n\nStriped title bar with optional close box (left) and zoom box (right), a\nsolid-white frame with a hard offset shadow, an optional grow box for\nresizing, optional edge scroll rails (`scrollbars`), and the slim windoid\nchrome (`variant=\"utility\"`). The HIG's window archetypes are parameter\nrecipes over this shell rather than fixed anatomies — the component enables\nHIG compliance, it doesn't enforce it (see docs/LAYOUT.md \"Window archetypes\"):\nthe full document window is `closable zoomable movable resizable\nscrollbars=\"both\"`, a modeless dialog box is `closable movable`, a utility\nwindow is `variant=\"utility\" movable`. Place inside `<vf-desktop>` to get\nclick-to-front stacking and automatic `active` management (utility windows\nfloat above the document tier).\n\nEvery recipe also declares `width` AND `height` (VfSized), in whole\nsystem px — the art's own unit, so the window keeps its proportions to the\nchrome inside it at every display density (a CSS-px size stays put while\nthe components in it triple). A window is a fixed box in both axes, the way\nthe WIND resource carried it: left to layout it takes whatever its\ncontainer or content hands it, which is how a title bar ends up wider than\nthe screen or a dialog reflows as it moves — and a window that grows with\nits body is one the user can neither predict nor (via the grow box) own.\nContent taller than the declared box is clipped at the frame the way the\nclassic content region was; `scrollbars` lets the user reach the rest.\nUnset, the window still renders — normal block layout, as before — and\nsays so once in the console.\n\n**Opening from a rect.** show clears `hidden`, and given `from` — a\nbox in viewport CSS px, an icon's `cellRect()` or a button's rect — opens\nthe window from it: dotted rectangles grow from that box toward the\nwindow's frame, four on screen at a time, bunched at the box and opening\nout toward the window, drawn with the icon drag outline's XOR pen on the\ndesktop's drag surface; the window draws once they have drained, eighteen\nsteps later. Until then it matches `:state(opening)` and paints nothing —\nstill laid out, focusable and a hit target, so a page can place it, raise\nit and focus into it at once, and a press finishes the rects and lands on\nthe window. Under `prefers-reduced-motion`, with no `vf-desktop` on its\npath, or without `from`, the window shows at once.\n\n**Closing to a rect.** hide sets `hidden`, and given `to` closes\nthe window to it: the same rectangles run the other way, from where the\nframe was in toward the box, the window gone from the first step. A press\nfinishes them, and removing the window leaves them running. Under\n`prefers-reduced-motion`, with no `vf-desktop` on its path, or without\n`to`, the window hides at once. The window knows nothing about icons:\n`from` and `to` are any rect.\n\n**Dragging as an outline.** A `movable` window moves live under the\npointer. With `outline-drag` a press on the title bar draws a dotted\noutline around the window on the desktop's drag surface instead, with the\nsame pen; the drag moves the outline, held where the window can land, and\nthe window moves there on the release. Escape cancels.",
+          "description": "`<vf-window>` — the System 7 desktop-window shell.\n\nStriped title bar with optional close box (left) and zoom box (right), a\nsolid-white frame with a hard offset shadow, an optional grow box for\nresizing, optional edge scroll rails (`scrollbars`), and the slim windoid\nchrome (`variant=\"utility\"`). The HIG's window archetypes are parameter\nrecipes over this shell rather than fixed anatomies — the component enables\nHIG compliance, it doesn't enforce it (see docs/LAYOUT.md \"Window archetypes\"):\nthe full document window is `closable zoomable movable resizable\nscrollbars=\"both\"`, a modeless dialog box is `closable movable`, a utility\nwindow is `variant=\"utility\" closable movable`. Place inside `<vf-desktop>` to get\nclick-to-front stacking and automatic `active` management (utility windows\nfloat above the document tier).\n\nEvery recipe also declares `width` AND `height` (VfSized), in whole\nsystem px — the art's own unit, so the window keeps its proportions to the\nchrome inside it at every display density (a CSS-px size stays put while\nthe components in it triple). A window is a fixed box in both axes, the way\nthe WIND resource carried it: left to layout it takes whatever its\ncontainer or content hands it, which is how a title bar ends up wider than\nthe screen or a dialog reflows as it moves — and a window that grows with\nits body is one the user can neither predict nor (via the grow box) own.\nContent taller than the declared box is clipped at the frame the way the\nclassic content region was; `scrollbars` lets the user reach the rest.\nUnset, the window still renders — normal block layout, as before — and\nsays so once in the console.\n\n**Opening from a rect.** show clears `hidden`, and given `from` — a\nbox in viewport CSS px, an icon's `cellRect()` or a button's rect — opens\nthe window from it: dotted rectangles grow from that box toward the\nwindow's frame, four on screen at a time, bunched at the box and opening\nout toward the window, drawn with the icon drag outline's XOR pen on the\ndesktop's drag surface; the window draws once they have drained, eighteen\nsteps later. Until then it matches `:state(opening)` and paints nothing —\nstill laid out, focusable and a hit target, so a page can place it, raise\nit and focus into it at once, and a press finishes the rects and lands on\nthe window. Under `prefers-reduced-motion`, with no `vf-desktop` on its\npath, or without `from`, the window shows at once.\n\n**Closing to a rect.** hide sets `hidden`, and given `to` closes\nthe window to it: the same rectangles run the other way, from where the\nframe was in toward the box, the window gone from the first step. A press\nfinishes them, and removing the window leaves them running. Under\n`prefers-reduced-motion`, with no `vf-desktop` on its path, or without\n`to`, the window hides at once. The window knows nothing about icons:\n`from` and `to` are any rect.\n\n**Dragging as an outline.** A `movable` window moves live under the\npointer. With `outline-drag` a press on the title bar draws a dotted\noutline around the window on the desktop's drag surface instead, with the\nsame pen; the drag moves the outline, held where the window can land, and\nthe window moves there on the release. Escape cancels.",
           "name": "VfWindow",
           "cssProperties": [
             {
@@ -20413,8 +21009,8 @@
               "type": {
                 "text": "boolean"
               },
-              "default": "true",
-              "description": "Show the close box (left side of the title bar).",
+              "default": "false",
+              "description": "Show the close box (left side of the title bar). Off by default, like\nevery other boolean attribute, so markup can leave it out; the document\nwindow and the modeless dialog box recipes say `closable`.",
               "attribute": "closable",
               "reflects": true
             },
@@ -20526,6 +21122,35 @@
               "description": "The header's height in whole system px, rule included — the way every\nkit bar counts its rule (an 18px title bar is 17 + 1). Unset, the header\nis as tall as what is slotted into it, plus the rule. Only matters while\nthe `header` slot is populated.",
               "attribute": "header-height"
             },
+            {
+              "kind": "field",
+              "name": "pattern",
+              "type": {
+                "text": "string | null | undefined"
+              },
+              "description": "A 1-bit fill for the body, as on `vf-container`: a library pattern by\nname (docs/PATTERNS.md) or sixteen hex digits, under the content and\nanchored at the content region's corner. Under `scrollbars` it fills the\nscrolled plane and scrolls with it (`vf-scroll-area`'s `pattern`). Unset,\nthe body stays white; an unrecognized value paints nothing and warns\nonce.",
+              "attribute": "pattern"
+            },
+            {
+              "kind": "field",
+              "name": "_pattern",
+              "type": {
+                "text": "Pattern | null"
+              },
+              "privacy": "private",
+              "default": "null",
+              "description": "`pattern`, resolved — what the body's fill paints; null paints nothing."
+            },
+            {
+              "kind": "field",
+              "name": "#warnedPattern",
+              "privacy": "private",
+              "type": {
+                "text": "boolean"
+              },
+              "default": "false",
+              "description": "One warning per element for an unrecognized `pattern`, not per render."
+            },
             {
               "kind": "field",
               "name": "_hasHeader",
@@ -20608,6 +21233,14 @@
               "default": "new RepeatTileController(this, { getBox: () => this.renderRoot?.querySelector<HTMLElement>('.vf-dots'), getArt: () => (this.variant === 'utility' && !this._dotsPattern ? DOTS : null), property: '--_vf-dots-tile', })",
               "description": "The kit dots: the utility bar's `.vf-dots` layer carries the repeating\ntile as `--_vf-dots-tile` (`vfDots`), whatever the window's width."
             },
+            {
+              "kind": "field",
+              "name": "#bodyFill",
+              "privacy": "private",
+              "readonly": true,
+              "default": "new PatternFillController(this, { getBox: () => this.body, getPattern: () => (this.scrollbars ? null : this._pattern), })",
+              "description": "The body's pattern fill (src/pattern-fill.ts). Under `scrollbars` the\nbuilt-in scroll area paints it on its scrolled plane instead."
+            },
             {
               "kind": "method",
               "name": "_dotsTexture",
@@ -21085,7 +21718,15 @@
                 "type": {
                   "text": "void"
                 }
-              }
+              },
+              "parameters": [
+                {
+                  "name": "event",
+                  "type": {
+                    "text": "MouseEvent"
+                  }
+                }
+              ]
             },
             {
               "kind": "method",
@@ -21236,7 +21877,7 @@
           ],
           "events": [
             {
-              "description": "Close box clicked. Detail `{ reason: 'close' }` (shape- compatible with vf-dialog's `vf-close`). The window does NOT remove itself; the consumer decides what closing means.",
+              "description": "Close box clicked. Detail `{ reason: 'close', altKey, shiftKey, metaKey, ctrlKey }`, the modifier keys held on the click (shape-compatible with vf-dialog's `vf-close`), so an Option-click can mean more than a click. The window does NOT remove itself; the consumer decides what closing means.",
               "name": "vf-close"
             },
             {
@@ -21280,8 +21921,8 @@
               "type": {
                 "text": "boolean"
               },
-              "default": "true",
-              "description": "Show the close box (left side of the title bar).",
+              "default": "false",
+              "description": "Show the close box (left side of the title bar). Off by default, like\nevery other boolean attribute, so markup can leave it out; the document\nwindow and the modeless dialog box recipes say `closable`.",
               "fieldName": "closable"
             },
             {
@@ -21368,6 +22009,14 @@
               "description": "The header's height in whole system px, rule included — the way every\nkit bar counts its rule (an 18px title bar is 17 + 1). Unset, the header\nis as tall as what is slotted into it, plus the rule. Only matters while\nthe `header` slot is populated.",
               "fieldName": "headerHeight"
             },
+            {
+              "name": "pattern",
+              "type": {
+                "text": "string | null | undefined"
+              },
+              "description": "A 1-bit fill for the body, as on `vf-container`: a library pattern by\nname (docs/PATTERNS.md) or sixteen hex digits, under the content and\nanchored at the content region's corner. Under `scrollbars` it fills the\nscrolled plane and scrolls with it (`vf-scroll-area`'s `pattern`). Unset,\nthe body stays white; an unrecognized value paints nothing and warns\nonce.",
+              "fieldName": "pattern"
+            },
             {
               "name": "width",
               "type": {
@@ -22419,7 +23068,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "Shared base for the kit's editable text fields — `vf-text-field`,\n`vf-text-area` and `vf-number-field`. Builds on\nVfShadowRoleControl (form association, the disabled-value guard and\nthe name/description bridge every field needs, its role sitting on the inner\nnative control) and adds the value/label scaffolding\nevery field repeated: the reflected `name`, the `value`/`placeholder`/\n`readonly`/`label` props, the captured default restored on form reset, the\n`updated()` → VfShadowRoleControl.syncFormValue funnel, and the display-\nscaling controller. Pairs with the `vfField` css fragment (the white-well\nskin) in styles/base.ts.\n\nSubclasses render their own native control (`<input>`/`<textarea>` plus any\nadornments), tag it `class=\"vf-field\"`, and may enrich the emitted event\ndetail via emitValue.",
+          "description": "Shared base for the kit's editable text fields — `vf-text-field`,\n`vf-text-area` and `vf-number-field`. Builds on\nVfShadowRoleControl (form association, the disabled-value guard and\nthe name/description bridge every field needs, its role sitting on the inner\nnative control) and adds the value/label scaffolding\nevery field repeated: the reflected `name`, the `value`/`placeholder`/\n`readonly`/`autoselect`/`label` props, the captured default restored on\nform reset, the `updated()` → VfShadowRoleControl.syncFormValue\nfunnel, `select()` and `focus()` on the inner control, and the display-\nscaling controller. Pairs with the `vfField` css fragment (the white-well\nskin) in styles/base.ts.\n\nSubclasses render their own native control (`<input>`/`<textarea>` plus any\nadornments), tag it `class=\"vf-field\"`, and may enrich the emitted event\ndetail via emitValue.",
           "name": "VfTextControlBase",
           "members": [
             {
@@ -22463,6 +23112,17 @@
               "attribute": "readonly",
               "reflects": true
             },
+            {
+              "kind": "field",
+              "name": "autoselect",
+              "type": {
+                "text": "boolean"
+              },
+              "default": "false",
+              "description": "Opens with the whole text selected, so typing replaces it. Implies\n`autofocus`: the first control carrying either takes the opening focus of\nits `vf-dialog`, or of a window the shell's window manager opens. A dialog\nselects the text on every open, a window on its first open only. A click\nstill places the caret.",
+              "attribute": "autoselect",
+              "reflects": true
+            },
             {
               "kind": "field",
               "name": "name",
@@ -22563,6 +23223,55 @@
               "description": "Classes for the `.vf-field-well` wrapper every field renders around its\nnative control: the shared skin hook (`vfField`), the grid-snap target, and\nthe focus rule's own gate. Assembled here so the three fields state the\nwrapper once and can't drift on what turns the rule on.",
               "readonly": true
             },
+            {
+              "kind": "field",
+              "name": "committed",
+              "type": {
+                "text": "string | null"
+              },
+              "privacy": "protected",
+              "default": "null",
+              "description": "The text as last committed: taken when the field gains focus, then at\neach commit. A commit that brings nothing new isn't announced, so the\nnative `change` that follows a Return commit, or a step, is not a second\none."
+            },
+            {
+              "kind": "field",
+              "name": "control",
+              "type": {
+                "text": "HTMLInputElement | HTMLTextAreaElement | null"
+              },
+              "privacy": "protected",
+              "description": "The inner native control every field renders, tagged `vf-field`.",
+              "readonly": true
+            },
+            {
+              "kind": "method",
+              "name": "focus",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "options",
+                  "optional": true,
+                  "type": {
+                    "text": "FocusOptions"
+                  }
+                }
+              ],
+              "description": "Focuses the inner control, keeping its caret where it was. Chromium\nselects all of an input's text when the host hands the focus on, as a Tab\ndoes; `select()` and autoselect are how a field opens selected."
+            },
+            {
+              "kind": "method",
+              "name": "select",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "description": "Select all of the field's text, as a native field's `select()` does. With\na new value not yet rendered, once it has: writing the value into the\ninput drops its selection, so `field.value = x; field.select()` selects\n`x`, as on a native field."
+            },
             {
               "kind": "method",
               "name": "formResetCallback",
@@ -22648,6 +23357,44 @@
               ],
               "description": "Mirror the native control's value into `value` and announce a keystroke."
             },
+            {
+              "kind": "method",
+              "name": "committedText",
+              "privacy": "protected",
+              "return": {
+                "type": {
+                  "text": "string"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "raw",
+                  "type": {
+                    "text": "string"
+                  }
+                }
+              ],
+              "description": "The committed form of typed text: as typed here; `vf-number-field` clamps and rounds it."
+            },
+            {
+              "kind": "method",
+              "name": "commit",
+              "privacy": "protected",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "raw",
+                  "type": {
+                    "text": "string"
+                  }
+                }
+              ],
+              "description": "Commit typed text: its committed form into `value`, announced unless it is what was last committed."
+            },
             {
               "kind": "method",
               "name": "handleChange",
@@ -22665,7 +23412,26 @@
                   }
                 }
               ],
-              "description": "Mirror the native control's value into `value` and announce a commit."
+              "description": "The native control's commit."
+            },
+            {
+              "kind": "method",
+              "name": "submitOnEnter",
+              "privacy": "protected",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "event",
+                  "type": {
+                    "text": "KeyboardEvent"
+                  }
+                }
+              ],
+              "description": "A plain Return in a single-line field with a form: commit, then the\nform's implicit submission, the order a native input keeps (its `change`\ncomes before the submission). The keydown is cancelled, so an enclosing\nmodal does not route the same press to its default button as well."
             },
             {
               "kind": "field",
@@ -23222,6 +23988,15 @@
               "description": "Makes the field read-only (focusable, not editable).",
               "fieldName": "readonly"
             },
+            {
+              "name": "autoselect",
+              "type": {
+                "text": "boolean"
+              },
+              "default": "false",
+              "description": "Opens with the whole text selected, so typing replaces it. Implies\n`autofocus`: the first control carrying either takes the opening focus of\nits `vf-dialog`, or of a window the shell's window manager opens. A dialog\nselects the text on every open, a window on its first open only. A click\nstill places the caret.",
+              "fieldName": "autoselect"
+            },
             {
               "name": "name",
               "type": {
@@ -23541,7 +24316,7 @@
         },
         {
           "kind": "class",
-          "description": "Base class for the modal shell `vf-dialog` — and for a consumer's own\nmodal (an alert box, say) authored against the kit.\n\nOwns the native `<dialog>` lifecycle every modal shares: `open` sync, `show()` /\n`close()`, the top/left placement (stated or centered) and the\nsingle `close` funnel that drops the written origin and fires `vf-close` with\nthe reason. Because every close path — Escape, `close()`, the opt-in\nlightDismiss click outside — routes through the native `close`\nevent, an Escape-close no longer leaves a stale origin behind, so the next\nopen re-derives it.\n\nIt also owns the two keyboard rules every classic dialog followed (see\ndefaultButton and initialFocusTarget): Return or Enter\nactivates the default button from anywhere in the dialog, and the box opens\nwith the insertion point in its first text field — or, with none, focus on\nthe default button.\n\nRemoving an open modal from the DOM is a close path too. HTML's dialog\n*removing steps* take the element out of the top layer **without** running\nthe close algorithm — no `close` event, no focus restoration — which is\nexactly what the standard framework pattern of unmounting a dialog instead\nof calling `close()` does. `disconnectedCallback` routes that path through\nthe same funnel: the removed element still fires `vf-close` (heard by\nlisteners on the element itself — it has left the tree, so nothing\nbubbles), `open` and the pinned margins reconcile so a re-append mounts it\nclosed and re-centered, and focus returns to the element that was focused\nwhen the modal opened.\n\nA `<form method=\"dialog\">` inside the modal closes it with the submitting\nbutton's `value` as returnValue, as a form inside a native\n`<dialog>` does. The platform's own rule looks for a `<dialog>` around the\nform, and this one is in the shadow root, so the modal listens for the\nsubmit itself.\n\nSubclasses supply only the frame chrome: a `render()` returning\n`<dialog",
+          "description": "Base class for the modal shell `vf-dialog` — and for a consumer's own\nmodal (an alert box, say) authored against the kit.\n\nOwns the native `<dialog>` lifecycle every modal shares: `open` sync, `show()` /\n`close()`, the top/left placement (stated or centered) and the\nsingle `close` funnel that drops the written origin and fires `vf-close` with\nthe reason. Because every close path — Escape, `close()`, the opt-in\nlightDismiss click outside — routes through the native `close`\nevent, an Escape-close no longer leaves a stale origin behind, so the next\nopen re-derives it.\n\nIt also owns the two keyboard rules every classic dialog followed (see\ndefaultButton and initialFocusTarget): Return or Enter\nactivates the default button from anywhere in the dialog, and the box opens\nwith the insertion point in its first text field — or, with none, focus on\nthe default button. A field marked `autoselect` takes the focus with its\ntext selected, on every open.\n\nRemoving an open modal from the DOM is a close path too. HTML's dialog\n*removing steps* take the element out of the top layer **without** running\nthe close algorithm — no `close` event, no focus restoration — which is\nexactly what the standard framework pattern of unmounting a dialog instead\nof calling `close()` does. `disconnectedCallback` routes that path through\nthe same funnel: the removed element still fires `vf-close` (heard by\nlisteners on the element itself — it has left the tree, so nothing\nbubbles), `open` and the pinned margins reconcile so a re-append mounts it\nclosed and re-centered, and focus returns to the element that was focused\nwhen the modal opened.\n\nA `<form method=\"dialog\">` inside the modal closes it with the submitting\nbutton's `value` as returnValue, as a form inside a native\n`<dialog>` does. The platform's own rule looks for a `<dialog>` around the\nform, and this one is in the shadow root, so the modal listens for the\nsubmit itself.\n\nSubclasses supply only the frame chrome: a `render()` returning\n`<dialog",
           "name": "VfModalDialog",
           "members": [
             {
@@ -23678,6 +24453,16 @@
               "default": "null",
               "description": "The value `close(value)` gave, pending for the next native `close` event."
             },
+            {
+              "kind": "field",
+              "name": "#closeKeys",
+              "privacy": "private",
+              "type": {
+                "text": "VfCloseKeys | null"
+              },
+              "default": "null",
+              "description": "The modifier keys a close box's click held, pending for the next native `close` event."
+            },
             {
               "kind": "field",
               "name": "#onSubmit",
@@ -23719,7 +24504,7 @@
                 "text": "HTMLElement | null"
               },
               "privacy": "protected",
-              "description": "Where focus lands on open. The classic Dialog Manager put the insertion\npoint in the first editable text item and gave nothing else focus at all;\nthe web needs a focused control for the keyboard to have anywhere to be,\nso with no text field the default button takes it (which is also what\nmakes Return and Space work there without a Tab). In order:\n\n1. a slotted control carrying `autofocus` — the author's say;\n2. the first enabled text-entry control (`vf-text-field`,\n   `vf-number-field`, `vf-text-area`, or a native text input/textarea);\n3. the defaultButton;\n4. null — leave the browser's own choice alone.\n\nLeft to itself, `showModal()` focuses the first focusable thing in flat\ntree order, which for a Cancel/OK row is Cancel, and for a body with a\nlink in it is the link — so Return did the one thing a classic dialog's\nReturn never did. Override to choose differently.",
+              "description": "Where focus lands on open. The classic Dialog Manager put the insertion\npoint in the first editable text item and gave nothing else focus at all;\nthe web needs a focused control for the keyboard to have anywhere to be,\nso with no text field the default button takes it (which is also what\nmakes Return and Space work there without a Tab). In order:\n\n1. the first slotted control carrying `autofocus` or `autoselect` — the\n   author's say;\n2. the first enabled text-entry control (`vf-text-field`,\n   `vf-number-field`, `vf-text-area`, or a native text input/textarea);\n3. the defaultButton;\n4. null — leave the browser's own choice alone.\n\nLeft to itself, `showModal()` focuses the first focusable thing in flat\ntree order, which for a Cancel/OK row is Cancel, and for a body with a\nlink in it is the link — so Return did the one thing a classic dialog's\nReturn never did. Override to choose differently. A target marked\n`autoselect` has its text selected once `vf-show` has fired.",
               "readonly": true
             },
             {
@@ -23728,10 +24513,10 @@
               "privacy": "private",
               "return": {
                 "type": {
-                  "text": "void"
+                  "text": "HTMLElement | null"
                 }
               },
-              "description": "Hand focus to initialFocusTarget, right after `showModal()`'s own\nfocusing steps have run (so this is the last word, not a race)."
+              "description": "Hand focus to initialFocusTarget, right after `showModal()`'s own\nfocusing steps have run (so this is the last word, not a race). Returns\nthe element focused, for `vf-show`."
             },
             {
               "kind": "field",
@@ -23795,6 +24580,25 @@
               ],
               "description": "Close the modal, with `returnValue` as its answer when one is given.\nFires `vf-close` with `{ reason: 'close', returnValue }`."
             },
+            {
+              "kind": "method",
+              "name": "closeFromBox",
+              "privacy": "protected",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "keys",
+                  "type": {
+                    "text": "VfCloseKeys"
+                  }
+                }
+              ],
+              "description": "Close from a close box, its `vf-close` carrying the modifier keys held on the click."
+            },
             {
               "kind": "method",
               "name": "#viewport",
@@ -23975,6 +24779,10 @@
             }
           ],
           "events": [
+            {
+              "description": "The modal opened: it is in the top layer, placed, and its initial focus is set. `detail: { focus }`, the element focused. The page's moment to finish composing it, such as measuring copy that varies. A field marked `autoselect` has its text selected after the event, so a value set in a handler is the one selected. Fired inside `show()` once the modal has rendered, else at its first render.",
+              "name": "vf-show"
+            },
             {
               "description": "The modal closed. `detail: { reason: 'escape' | 'close' | 'outside', returnValue: string | null }`.",
               "name": "vf-close"