@synopackageland/ui 0.25.14 → 0.25.16

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/component-defaults.md

@@ -21,6 +21,8 @@ placeholders; all nine dictionaries contain the same keys and placeholders.
 | ToastProvider | Close action, Reka announcement prefix and viewport hotkey hint; new optional `announcementLabel`/`viewportLabel` overrides; existing forwarded `label` still overrides the viewport |
 | Spinner, LoadingIndicator, LoadingArea, LoadingMask | Accessible loading state |
 | RepeatRow, Tag | Remove action |
+| TagPicker, TagPickerList | Choose tags / Choose a tag / Add tag placeholders and name, tag search placeholder, create row, no-match and loading text, the max message, clear and remove actions |
+| ExpandAllButtons | Expand all / Collapse all tooltips and names |
 | CopyCutField | Copy/cut actions |
 | SplitButton, OverflowToolbar | More/options actions, including hidden measurement text |
 | Card, Breadcrumb | Content toggle and show-full-path controls |

package/docs/theme-hooks.md

@@ -132,6 +132,9 @@ own browser tab) may follow `prefers-color-scheme` (see [Dark theme](color-syste
 | `data-ui-facet-panel` | `FacetPanel` (`data-presentation` `panel`, `sheet`) | present |
 | `data-ui-facet-group` (`data-key`), `-group-toggle`, `data-ui-facet-value` (`aria-pressed`), `data-ui-facet-count`, `data-ui-facet-panel-clear`, `-trigger`, `-count` | `FacetPanel` parts | present |
 | `data-ui-tag-editor` (`data-editing`), `-read`, `-field`, `-input`, `-list`, `-option` (`data-kind` `option`, `create`) | `TagEditor` parts | present |
+| `data-ui-tag-picker` (`data-ui-tag-picker-inline` for the inline variant), `-more`, `-add`, `-placeholder`, `-count` | `TagPicker` trigger and its parts | present |
+| `data-ui-tag-picker-list`, `-panel`, `-search`, `-status`, `-full`, `-clear`, `-options`, `-empty`, `data-ui-tag-option` (value), `data-ui-tag-create` (name) | `TagPickerList` (in the TagPicker dropdown or sheet, or on its own) | present |
+| `data-ui-expand-all` (buttons `data-action` `expand-all`, `collapse-all`) | `ExpandAllButtons` | present |
 | `data-ui-fieldset` | `Fieldset` | present |
 | `data-fieldset-description` | `Fieldset` description under the title | present |
 | `data-ui-form-group` | `FormGroup` (`data-disabled` while disabled) | present |

package/package.json

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