@synopackageland/ui 0.25.15 → 0.25.17

package/dist/lib/nativeShell.d.ts

@@ -1,8 +1,40 @@
-/** Whether this page runs in the phone app and may go back to its App list. */
-export declare function canCloseToShell(): boolean;
 /**
- * Asks the phone app to go back to its App list. Call it from a tap: the app
+ * The Package Land launcher (the "shell") as seen from an App page in it. Its
+ * Home request, `{ v: 1, type: 'close' }`, takes the user back to the
+ * launcher's home. Two shells offer it:
+ *
+ * - The phone app injects `window.SynoPkgNative` (SynoPkgNative v1) into a
+ *   registered App's main frame only; its optional `features` lists the
+ *   requests it understands beyond the v1 baseline, `close` among them. The
+ *   request goes through the bridge's `post`.
+ * - The browser launcher opens each App in a same-origin frame named
+ *   `synopkg-shell:1:<features>` (comma-separated, e.g. `synopkg-shell:1:close`).
+ *   The request is posted to the parent window at this page's own origin.
+ *
+ * In a plain browser tab, a DSM window or any other frame there is no shell
+ * and nothing here offers anything. The shell honors a request only right
+ * after a tap, so call it from a click.
+ */
+type CloseMessage = {
+    v: 1;
+    type: 'close';
+};
+type ShellBridge = {
+    protocol: number;
+    features?: readonly unknown[];
+    post(message: CloseMessage): void;
+};
+type ShellWindow = Pick<Window, 'name' | 'parent' | 'top' | 'location'> & {
+    SynoPkgNative?: Partial<ShellBridge>;
+};
+/** The name the browser launcher gives an App's frame, and the features it lists. */
+export declare const SHELL_FRAME_PREFIX = "synopkg-shell:1:";
+/** Whether this page runs in the launcher (phone app or browser) and may go back to its home. */
+export declare function canCloseToShell(view?: ShellWindow | undefined): boolean;
+/**
+ * Asks the launcher to go back to its home. Call it from a tap: the launcher
  * ignores a request without a recent user gesture. Returns false when there is
- * no phone app to ask.
+ * no launcher to ask.
  */
-export declare function closeToShell(): boolean;
+export declare function closeToShell(view?: ShellWindow | undefined): boolean;
+export {};

package/dist/reka-runtime.json

@@ -3,7 +3,7 @@
   "version": "2.11.0",
   "delivery": "bundled-patched-esm",
   "patchManifestSha256": "9c5b9c9a162fa584b4695a683368a4484b3ac6e70177fd063b77aa618c051627",
-  "bundleSha256": "abe34cf2578a7517d653b2d5efb3338ecce0562d845477aefc6158a18df763b1",
+  "bundleSha256": "0613c4649ba3a597c7c6d972e93541034089c6176d953a0a7d2426dc0fe6165a",
   "sourceHashes": {
     "shared/useBodyScrollLock.js": "287bfb604318c4202769e4b5191896eaf0e52a952e1de898967cbe09467fcfda",
     "DismissableLayer/DismissableLayer.js": "3c8d248f0a32e01f89ca1f6202b1bb691bf5d0e4012a92535e161c35e69cdc32",

package/docs/adaptive-layout.md

@@ -141,16 +141,46 @@ state keys are copied through). The Android back button or the iOS edge swipe
 calls `close` for the top surface only; closing by code removes the entry.
 Pass `enabled: false` where the surface is a popover or inside a DSM window.
 
-Inside the Package Land phone app, a root page also gets Back to the App list.
-The app's bridge (`window.SynoPkgNative`, protocol 1) lists `close` in its
-`features`; AppLayout then leads the phone bar with the shared back arrow, and
-a tap posts `{ v: 1, type: 'close' }`, which the app honors only right after a
-tap. A browser, a sub-page (which has its own Back) and anything wider than a
-phone never show it. When the page hides the bar (`phone-bar-title="none"`
-without a menu), the first `PageToolbar` or `SectionTabs` row on the page holds
-the button at its start, so it costs no row; with no such row the bar is drawn
-for it. The arrow is `app-layout/back-arrow.json`, a byte copy of the phone
-app's drawing; `tests/ShellBack.test.ts` pins its SHA-256, as the phone app
+Inside the Package Land launcher, every page leads with Home, sub-pages
+included: Home goes back to the launcher's home, as the launcher's own bars do.
+Stepping back is the system Back's job (Android's back button, the browser's
+back or swipe). The page finds the launcher in one of two ways:
+
+- **Phone app.** Its bridge (`window.SynoPkgNative`, protocol 1) lists `close`
+  in its `features`. A tap posts `{ v: 1, type: 'close' }` through the bridge.
+- **Browser launcher.** It opens the App in a same-origin frame named
+  `synopkg-shell:1:close` (`SHELL_FRAME_PREFIX` followed by its features,
+  comma-separated). A tap posts the same message to the parent window, at the
+  page's own origin.
+
+Either launcher honors the request only right after a tap. A plain browser
+tab, a DSM window and anything wider than a phone never show Home; there a
+sub-page keeps its Back arrow.
+
+In the launcher, a sub-page has no Back button, so each one is a history entry
+of the App (`useBackDismiss`):
+- the layout's `back`, or a `PageHeader` with `back`, takes one entry while it
+  is shown;
+- a `PushTransition` page already owns one.
+
+The system Back pops that entry and runs the sub-page's back (`back`, or
+`pop`). The launcher goes through an App's own entries before it leaves the
+App: in the browser, the frame's entries come first in the tab's history; on
+Android, the WebView's history comes first. A sub-page the App closes itself
+takes its entry back off.
+
+An App whose sub-pages are router addresses still works: the Back pops the
+layout's entry, and the App's back handler then goes back through the
+router.
+
+AppLayout leads the phone bar with a 44px home icon; on a sub-page it comes
+before the sub-page's title. When a root page hides the
+bar (`phone-bar-title="none"` without a menu), the first `PageToolbar` or
+`SectionTabs` row on the page holds the button at its start, so it costs no
+row. With no such row the bar is drawn for it.
+
+A sub-page's Back draws `app-layout/back-arrow.json`, a byte copy of the phone
+app's drawing. `tests/ShellBack.test.ts` pins its SHA-256, as the phone app
 does, so change both copies together.
 
 `node scripts/check-keyboard.mjs [out-dir]` (after `pnpm build`) checks all of

package/docs/ux-grid.md

@@ -20,13 +20,35 @@ props (`getEditText`, `cell-commit`); cell painters are in `useGridCells`.
 | Shift+click, Shift+arrow | Keep the anchor, move the head; Cmd/Ctrl+Shift+arrow jumps to the edge |
 | Cmd/Ctrl+A | All cells |
 | Column header click / Shift / Cmd | Select columns, extend, toggle |
-| Row checkbox / Shift, corner checkbox | Select rows, a run of rows, all rows |
+| Row checkbox / Shift, corner checkbox | Select rows, a run of rows, all rows (a click on the row number opens the record: see Row header) |
 | Esc | Keeps the selection; cancels a drag, a resize or a fill in progress |
 
 Hit-testing is arithmetic over cached column offsets and row heights: a
 pointer move reads nothing from the DOM. Past the last column or row, over a
 header or over blank space, a drag head clamps to the nearest data cell.
 
+## Row header
+
+The row header shows the row number; on hover or on a checked row its
+`rowControls` replace the number.
+
+| Click (mouse or pen) | Result |
+|---|---|
+| The row number (the header outside its controls) | Emits `row-expand(row)`: open the record, as the `expand` control and Space on a selected cell do. Pointer cursor |
+| The checkbox | Toggles the row in the selection, as before (Shift selects a run). Never opens the record |
+| The expand control | `row-expand(row)` |
+
+Fallback: with no `row-expand` listener bound, a click on the row number
+keeps the old behaviour. It opens nothing and changes no selection, and the
+cursor stays the default. Apps that do not open records are unaffected. With
+only a `checkbox` control the checkbox sits where the number is drawn, so a
+click there selects. `GridHostController` asks the optional
+`canExpandRow()` hook at click time; `GridHost` answers it from its listeners.
+
+The row header takes no keyboard focus: the grid's one focus owner sits on the
+active cell. To open a record from the keyboard, press Space on a selected
+cell.
+
 `selectionBlock(state, { rowCount, columnCount })` gives the rows and columns
 a selection covers (a row selection covers every column, a column selection
 every row); `cellRange` gives the rectangle of a cell selection.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@synopackageland/ui",
-  "version": "0.25.15",
+  "version": "0.25.17",
   "description": "Shared Vue 3 UI component library with a DSM 7 inspired application theme",
   "license": "MIT",
   "type": "module",