@brickclay-org/ui 0.1.90 → 0.1.91

package/index.d.ts

@@ -1579,7 +1579,7 @@ declare class BkSelect implements ControlValueAccessor, AfterViewInit, OnDestroy
      * existing click/Enter-to-open behaviour is unchanged.
      */
     openOnFocus: _angular_core.InputSignal<boolean>;
-    dropdownPosition: _angular_core.InputSignal<"top" | "bottom">;
+    dropdownPosition: _angular_core.InputSignal<"bottom" | "top">;
     hasError: boolean;
     errorMessage: string;
     /**
@@ -1618,7 +1618,7 @@ declare class BkSelect implements ControlValueAccessor, AfterViewInit, OnDestroy
     private gridDraftOptions;
     searchTerm: _angular_core.WritableSignal<string>;
     markedIndex: _angular_core.WritableSignal<number>;
-    placement: _angular_core.WritableSignal<"top" | "bottom">;
+    placement: _angular_core.WritableSignal<"bottom" | "top">;
     visibleCount: _angular_core.WritableSignal<number>;
     private resizeObserver?;
     /**
@@ -1868,6 +1868,19 @@ declare class BkInput implements OnInit, OnDestroy, AfterViewInit, ControlValueA
     phoneOverlay?: CdkConnectedOverlay;
     isFocused: boolean;
     inputValue: string;
+    /**
+     * What the template's `[value]` binding actually renders. Deliberately a separate property
+     * from `inputValue` (which still mirrors the live text for `isFilled`/bookkeeping on every
+     * keystroke): re-applying `[value]` to an element that already displays that exact text is a
+     * no-op on most inputs, but on `type="number"` it isn't - Chromium doesn't skip the write just
+     * because the string is unchanged, and since `type="number"` also refuses `setSelectionRange`
+     * (it throws), we have no way to put the caret back afterwards. So `displayValue` is only ever
+     * written by genuinely external changes (writeValue(), the phone country-prefix swap) - never
+     * from handleInput() or the "parent mutated the native value" resync, both of which are only
+     * echoing back text the DOM already has. That keeps every self-originated edit from re-touching
+     * `.value` at all, which is the only reliable fix here given number inputs can't be caret-restored.
+     */
+    displayValue: string;
     isDropdownOpen: boolean;
     private pendingMaskedValue;
     private isPropagatingViewValue;
@@ -2921,7 +2934,7 @@ declare class BkHierarchicalSelect implements ControlValueAccessor, AfterViewIni
      */
     appendToBody: _angular_core.InputSignal<boolean>;
     /** Open above or below the trigger (also used when appendToBody is true for fixed coordinates). */
-    dropdownPosition: _angular_core.InputSignal<"top" | "bottom">;
+    dropdownPosition: _angular_core.InputSignal<"bottom" | "top">;
     /** Key for option color (e.g. "color"). When set, option label and selected value use this color. */
     colorKey: _angular_core.InputSignal<string>;
     /**
@@ -2955,7 +2968,7 @@ declare class BkHierarchicalSelect implements ControlValueAccessor, AfterViewIni
     /** Index of the keyboard-highlighted option within the current level (`filteredItems`). */
     markedIndex: _angular_core.WritableSignal<number>;
     private el;
-    placement: _angular_core.WritableSignal<"top" | "bottom">;
+    placement: _angular_core.WritableSignal<"bottom" | "top">;
     /**
      * Panel width, kept equal to the control's — matches the old `dropdownStyle().width`
      * behaviour. Set on open and re-measured by a ResizeObserver on the control while open, so a
@@ -3719,7 +3732,7 @@ declare class BkPopover implements OnDestroy {
      * anything interactive. `hover` opens on the way in and closes on the way
      * out, with a grace period so the pointer can travel into the panel.
      */
-    trigger: _angular_core.InputSignal<"hover" | "click">;
+    trigger: _angular_core.InputSignal<"click" | "hover">;
     /** Optional heading. Empty hides the header row entirely. */
     title: _angular_core.InputSignal<string>;
     /** Show the × in the header. Ignored without a `title` to put it in. */
@@ -4566,7 +4579,7 @@ declare class BkTd extends BkCellBase implements AfterViewInit, OnDestroy {
      */
     protected readonly truncatedTooltip: _angular_core.WritableSignal<string>;
     /** Forwarded to the content wrapper's `bkTooltip`. Override on a column whose default 'right' would run into its neighbour. */
-    tooltipPosition: _angular_core.InputSignal<"right" | "left" | "top" | "bottom">;
+    tooltipPosition: _angular_core.InputSignal<"left" | "right" | "bottom" | "top">;
     /** Only present when `ellipsis()` is true — see the `@else` branch in the template. */
     private ellipsisTextRef?;
     checkbox: _angular_core.InputSignal<boolean>;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@brickclay-org/ui",
-  "version": "0.1.90",
+  "version": "0.1.91",
   "schematics": "./schematics/collection.json",
   "ng-add": {
     "save": "dependencies"

package/src/lib/toastr/toastr.css

@@ -14,8 +14,10 @@
   pointer-events: none;
 }
 
-/* Guarantee toasts stack above dialogs/popovers/etc. that also use CDK overlays — CDK's own
-   z-index otherwise just reflects creation order. Targets the pane CDK wraps this panel in. */
+/* Belt-and-braces: pins the pane itself in case some future overlay ever nests a pane inside
+   this one's wrapper. The stacking fight against *other* overlays (dialogs, selects, popovers)
+   actually happens one level up, at the wrapper CDK puts around the pane — see the
+   `hostElement.style.zIndex` line in toastr.service.ts, which is the real fix for that. */
 .cdk-overlay-pane.bk-toastr-panel {
   z-index: 2147483647 !important;
 }