@kouji-ui/components 0.9.3 → 0.9.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kouji-ui/components",
-  "version": "0.9.3",
+  "version": "0.9.4",
   "description": "Opinionated styled Angular components built on @kouji-ui/core directives. Themed at runtime via @kouji-ui/themes.",
   "license": "MIT",
   "repository": {

package/types/kouji-ui-components.d.ts

@@ -9109,6 +9109,25 @@ declare class KjCommandPaletteComponent {
     private stackHandle;
     private wrapper;
     constructor();
+    /**
+     * Dismiss-by-scrim is a press the backdrop owns from the start. The
+     * backdrop spans the viewport underneath every overlay opened from
+     * inside the palette, so the browser hands it clicks it never saw the
+     * start of: commit a NEW value in a nested `<kj-select>` and its option
+     * list re-renders, the clicked option leaves the document before the
+     * pointer is released, and the engine retargets the `click` to what is
+     * under the pointer by then — this scrim. Committing the SAME value
+     * re-renders nothing, so the option stays put and the palette survived,
+     * which is what made the bug look value-dependent.
+     *
+     * Arming on `pointerdown` — dispatched at the true origin, before any
+     * re-render can move it — is what separates the two.
+     */
+    private readonly backdropPress;
+    /** @internal — template listener; the press began on the scrim. */
+    protected onBackdropPress(): void;
+    /** @internal — template listener. */
+    protected onBackdropClick(event: MouseEvent): void;
     /** Programmatically close the palette. */
     close(): void;
     /**