@meshmakers/shared-ui 3.4.320 → 3.4.340

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@meshmakers/shared-ui",
-  "version": "3.4.320",
+  "version": "3.4.340",
   "peerDependencies": {
     "@angular/common": "^22.0.0",
     "@angular/core": "^22.0.0",

package/types/meshmakers-shared-ui.d.ts

@@ -1537,11 +1537,18 @@ type Quarter = 1 | 2 | 3 | 4;
  *   local timezone — e.g. year 2026 = `[Jan 1 00:00 local, Jan 1 next-year 00:00 local)`.
  * - `'utc'`: boundaries are wall-clock instants in UTC — e.g. year 2026 =
  *   `[2026-01-01T00:00:00Z, 2027-01-01T00:00:00Z)`.
+ * - any **IANA time-zone id** (e.g. `'Europe/Vienna'`, `'Europe/Lisbon'`): boundaries
+ *   are wall-clock instants in that zone, resolved DST-correctly regardless of the
+ *   browser's own zone — so "yesterday in `Europe/Lisbon`" is right even from a Vienna
+ *   browser (AB#4190). A local calendar day across a DST transition is 23 h or 25 h.
  *
  * Relative ranges (last N hours/days) are timezone-independent (a fixed offset
  * from "now") and ignore this setting.
+ *
+ * The `(string & {})` member keeps the `'local'` / `'utc'` literals in editor
+ * autocomplete while still accepting an arbitrary IANA id.
  */
-type TimeRangeZone = 'local' | 'utc';
+type TimeRangeZone = 'local' | 'utc' | (string & {});
 /**
  * Configuration for the time range picker
  */
@@ -1627,6 +1634,30 @@ declare const DEFAULT_TIME_RANGE_LABELS: TimeRangePickerLabels;
  * Utility functions for time range calculations
  */
 declare class TimeRangeUtils {
+    /**
+     * Offset (wall-clock − UTC), in milliseconds, of an IANA `zone` at the instant `utcMs`.
+     * Computed via `Intl.DateTimeFormat` so it is DST-correct and independent of the browser's
+     * own zone. Positive east of UTC (e.g. +7 200 000 for `Europe/Vienna` in summer).
+     */
+    private static zoneOffsetMs;
+    /**
+     * The UTC instant whose wall-clock time in IANA `zone` equals the given civil fields.
+     * Two-pass so DST transitions resolve correctly (the offset is re-read at the candidate
+     * instant, not just at the naive UTC guess). Field overflow normalizes like `Date.UTC`
+     * (e.g. month 12 ⇒ next January, day 32 ⇒ next month).
+     */
+    private static zonedCivilToUtc;
+    /**
+     * Build a calendar-boundary instant for the given civil fields in `zone`.
+     * `'utc'` and `'local'` keep the historical `Date.UTC` / browser-local-constructor
+     * behaviour byte-for-byte; any other value is treated as an IANA id (AB#4190).
+     */
+    private static boundary;
+    /**
+     * Extract the calendar year/month/day of `date` as seen in `zone`. Used to normalize
+     * custom ranges to that zone's civil-day boundaries.
+     */
+    private static civilDateParts;
     /**
      * Calculate time range for a specific year.
      * Uses exclusive end boundary (start of next year) for correct LESS_THAN filtering.
@@ -2136,6 +2167,17 @@ declare class WindowStateService {
     saveDimensions(dialogKey: string, dimensions: WindowDimensions): void;
     clearDimensions(dialogKey: string): void;
     resolveWindowSize(dialogKey: string, defaults: WindowDimensions, min?: WindowDimensions): WindowDimensions;
+    /**
+     * Keeps a dialog fully on screen: neither a large default nor a size stored
+     * on a bigger monitor may exceed the current viewport (minus a margin), or
+     * the action bar ends up unreachable below the fold on small resolutions.
+     * The clamp deliberately wins over the dialog's minWidth/minHeight — a
+     * slightly-too-small dialog is usable, an off-screen one is not. Stored
+     * sizes stay untouched, so returning to a larger screen restores them.
+     */
+    private clampToViewport;
+    /** Seam for tests — window.innerWidth/innerHeight are not assignable in Karma. */
+    protected viewportSize(): WindowDimensions;
     captureAndSave(dialogKey: string, windowElement: HTMLElement, min?: WindowDimensions): void;
     private parsePixels;
     /**