@smartbit4all/ng-client 7.3.0 → 7.3.2

package/HTML-WIDGET.md

@@ -461,6 +461,7 @@ megy le, és egy újra-feloldás már a leküldött erőforrások közül válas
 ```html
 <div class="card" data-sb4-action="OPEN_ENTRY">…</div>
 <li data-sb4-action="REMOVE_MEMBER" data-sb4-action-identifier="{{id}}">…</li>
+<div data-sb4-action="OPEN_MEMBER" data-sb4-action-identifier="{{id}}" data-sb4-action-direct>…</div>
 ```
 
 Bármely elem hordozhat triggert: a kattintás (vagy Enter / Space) azt az akciót futtatja, amelynek
@@ -487,6 +488,11 @@ függetlenül**. Hiányzó `data-sb4-action-identifier` = identifier nélküli a
   állapot a lista változását a html újraírása nélkül követi.
 - **Nem kínált akció** (a sor / nézet nem adja): az elem nem interaktív, `sb4-action-inert` osztályt
   kap, a kliens egyszer warn-ol, a kattintás a körülötte lévő triggerre vagy a kártyára jut.
+- **Direkt trigger** (`data-sb4-action-direct`): akkor is lő, ha a lista nem kínálja az akciót —
+  ilyenkor a kliens maga rakja össze a `{ code, identifier }` akciót az attribútumokból. Ha a lista
+  kínál egyező akciót, az nyer (letiltás, descriptor a listából jön). Nem inert és nem warn-ol.
+  Mivel a kínált-akció lista már nem kapuzza, **a szerver handlere maga ellenőrizze a
+  jogosultságot**. Java: `Tag.directAction(code)` / `Tag.directAction(code, identifier)`.
 - Paraméter-attribútum nincs: az identifier és a sor-scope (`params.model` = a sor) fedi az
   eseteket.
 

package/MIGRATION-7.0.md

@@ -2070,8 +2070,84 @@ selection carried are not sent again and late responses are always applied.
     not the array. `SmarttreeGenericService` writes a reload into the node objects a host holds
     (same objects, new data) and sets `treeFromBackend` to the merged nodes.
 
+### New in 7.3.2: keybindings (#19122)
+
+Additive: a host without a keymap gets one binding, Escape closes a dialog that offers
+`DEFAULT_CLOSE`. Needs the matching platform (`Keybinding`, `View.keybindings`,
+`ComponentModel.keybindings`); release the two together.
+
+- **The keymap.** Properties files on the server, `CODE=chord[,chord]` binds every action of
+  that code, `viewName.CODE=chord[,chord]` only in that view and wins over `CODE`; an empty
+  `viewName.CODE=` disables the chord in that view. The host lists its own file before the
+  platform's, the first file with the key wins:
+  `spring.keybindings.basename=keybindings-<app>,keybindings-platform`. The platform's file binds
+  Escape to `DEFAULT_CLOSE`, `CANCEL` and `CLOSE_SEARCH_PAGE`, which close the view on every
+  platform page offering them; without the property only that file is read.
+- **Chord grammar.** Modifiers, then one key, joined by `+`: `Mod+Shift+S`. `Mod` is Cmd on a Mac
+  and Ctrl elsewhere, so one chord serves both; `Ctrl`, `Alt`, `Shift`, `Meta` are the literal
+  keys. The server writes every chord canonically (modifier order `Mod`, `Ctrl`, `Alt`, `Shift`,
+  `Meta`, letters upper case), so the order and case in the file do not matter. The key is the
+  browser's `KeyboardEvent.key` name (`Escape`, `Enter`, `ArrowUp`, `F2`, `Delete`), the space
+  bar is `Space`. A letter or digit also matches by its physical key when a modifier changes the
+  character (Option+N on a Mac). Chords the browser keeps for itself (`Mod`/`Ctrl` with `W`,
+  `T`, `N`, `Q`, `R`, `Tab`, and `F5`) and unparsable ones are dropped with an ERROR log.
+- **Bindings in code.** A page binds its own actions on the view, typically in `initModel`:
+  ```java
+  view.addKeybindingsItem(new Keybinding()
+      .chord(KeyChord.of(KeyboardKeys.MOD, KeyboardKeys.SHIFT, KeyboardKeys.ARROW_UP))
+      .uiActionCode(MOVE_UP)
+      .uiActionIdentifier(rowId)); // optional: without it every MOVE_UP action is bound
+  ```
+  Per action the code level wins over `viewName.CODE`, which wins over `CODE`; a code-level entry
+  replaces the keymap of its action, they are not merged. Only the code level can name an
+  identifier. When two actions of a view share a chord, the more specific source keeps it, then
+  the earlier action, with a WARN log. The server resolves all this into
+  `ComponentModel.keybindings`; a keymap entry of an action the view does not offer yields
+  nothing.
+- **Which view gets the key.** One document listener serves every view. The key goes to the view
+  holding the focus, the innermost one when views are nested; when nothing has the focus, to the
+  view that had it last (the focus is lost when a pushed layout re-renders the field), else the
+  top-most dialog, else the current page. If that view has no enabled binding for the chord, the key
+  bubbles to the enclosing views, but never out of a dialog: the page behind it does not react
+  while a dialog is open. A NORMAL view opened by the user's action takes the focus, a view
+  restored on reload does not.
+- **What does not fire.** Unmodified typing in an editable element (text inputs, textareas,
+  selects, contenteditable): letters, digits, editing and caret keys, and `Enter` in a multi-line
+  field stay the element's; `Escape`, the function keys, chords with Ctrl, Alt or Cmd, and `Enter`
+  in a single-line input reach the bindings. A disabled or not offered action does not fire: the
+  key bubbles on and reaches the browser when nothing takes it. Auto-repeated keys, a key a panel
+  already handled (`defaultPrevented`) and a key pressed in an overlay of no view (an open select
+  or menu panel) fire nothing. An unmodified `Enter` or `Space` on a focused button, link or
+  ARIA-interactive control stays with that control (the browser activates it), and the `Enter`
+  that confirms an IME composition fires nothing. A fired chord is `preventDefault`ed.
+- **Tooltip and accessibility.** A toolbar button shows its chords in its tooltip, formatted for
+  the platform (`⌘⇧S` on a Mac, `Ctrl+Shift+S` elsewhere), after the server tooltip or alone; the
+  tooltip also opens on keyboard focus. The button names them in `aria-keyshortcuts`.
+- **Two host rules.** Do not bind `Enter` on a view whose form uses `SmartForm.submitOnEnter`:
+  both would run. With `dialogDisableClose: false` MatDialog closes the dialog on Escape itself,
+  as before; the `DEFAULT_CLOSE=Escape` binding is what closes it under the default `true`.
+- **Focus survives a push.** When a push re-renders the field being edited, the view focuses it
+  again: the field with the same widget key (`data-testid`) at the same position within the view,
+  with the caret or selection of a native input or textarea and of a Quill editor. Nothing
+  happens when the field left the layout or the focus moved elsewhere meanwhile (a dialog, a click).
+- **Pending edits are saved first.** A fired action (a key, a toolbar click, an HTML trigger)
+  waits until the view's widgets have saved what was typed into them — today the filter editor,
+  which saves its fields on blur — so a query bound to `Enter` runs with the value just typed. If
+  that save fails, the action is not sent.
+- **Messages.** A message with a single option focuses it and sends it on Escape. Otherwise the
+  first `confirm`-typed option gets the initial focus (Enter presses it) and Escape sends the first
+  `cancel`-typed option. A `reject` option is never chosen by a key, and untyped options (a YES/NO
+  without types) get neither: Escape does nothing, the focus stays on the first button.
+- **Out of scope.** Row actions (grid, table, card rows) and actions inside widgets have no
+  keybindings; only the view's own actions do.
+- **New in the public API:** model `Keybinding`, `View.keybindings`,
+  `ComponentModel.keybindings`; Java `KeyChord`, `KeyboardKeys`, `KeybindingSettingApi`.
+
 ### Bugfixes shipped with 7.0
 
+- (7.3.2) A view dialog no longer disappears on the browser's back button. MatDialog's default
+  `closeOnNavigation` disposed every dialog on a Location change without any action, so the
+  backend kept the views open and a reload brought them back; view dialogs now open with it off.
 - `SmartformwidgetComponent.ngAfterViewInit` no longer crashes with
   `Cannot read properties of undefined (reading 'valueChanges')` when the form
   contains a `MONTH_PICKER` widget (it wrongly subscribed to the non-existent

package/README.md

@@ -165,6 +165,13 @@ A `UiActionModel` is **frozen**: build an entry, never edit one. To change how a
 looks, rebuild the array — `actions.map(a => a.uiAction.code === c ? { ...a, cssClass: 'x' } : a)`
 — because it is the array reference changing that re-renders the toolbar.
 
+### Keybindings
+
+The server binds key chords (`Mod+Shift+S`, `Mod` = Cmd/Ctrl) to a view's actions, from a
+keymap file and from code; the client fires them in the focused view and shows them in the
+button's tooltip. Nothing to wire on the client. The keymap format, the chord grammar and the
+rules for which view gets a key: `MIGRATION-7.0.md`, *New in 7.3.2: keybindings*.
+
 ## Change detection
 
 7.0 runs without zone.js and every library component is `OnPush`. Nothing forces your host to