@elasticias/ui 1.0.44 → 1.0.45

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elasticias/ui",
-  "version": "1.0.44",
+  "version": "1.0.45",
   "peerDependencies": {
     "@angular/common": "^21.0.0",
     "@angular/core": "^21.0.0",

package/styles/_comptoir.scss

@@ -115,6 +115,15 @@
   --hit-touch:  48px;  /* POS / mobile primary actions */
   --hit-pos:    64px;  /* POS number pad, big totals */
 
+  /* ── Layers ──────────────────────────────────────────────────── */
+  /* Toasts sit above every modal and overlay. PrimeNG numbers its layers
+     at runtime (ZIndexUtils): each new layer takes the last one's value
+     plus 1, plus the base of its own kind when the kind changes (modal
+     1100, overlay 1000). A dialog is 1101, a select opened inside it
+     2102, a dialog opened over that 3203, so no value near PrimeNG's
+     bases stays on top. 100000 is about ninety mixed layers away. */
+  --z-toast:    100000;
+
   /* ── Motion ──────────────────────────────────────────────────── */
   --t-fast: 140ms;
   --t-base: 260ms;

package/styles/_patterns.scss

@@ -1539,11 +1539,17 @@
 }
 
 .row-actions__trigger {
+  /* Read again by the touch tier, which reserves the 48px footprint
+     around this box. */
+  --ef-row-trigger-w: 34px;
+  --ef-row-trigger-h: 28px;
   appearance: none;
   background: var(--paper-alt);
   border: 1px solid var(--rule);
-  width: 34px;
-  height: 28px;
+  box-sizing: border-box;
+  width: var(--ef-row-trigger-w);
+  height: var(--ef-row-trigger-h);
+  flex-shrink: 0;
   border-radius: var(--r-pill);
   display: inline-grid;
   place-items: center;
@@ -2243,6 +2249,15 @@
   line-height: 1;
 }
 
+/* The back and month arrows are icon-font glyphs, which bidi never
+   mirrors. In Arabic the header runs right to left, so "previous" sits on
+   the right and must point right. (Text arrows such as the pager's
+   ‹ › « » are Bidi_Mirrored and already flip on their own.) */
+[dir='rtl'] .dp__back i,
+[dir='rtl'] .dp__cal-nav i {
+  transform: scaleX(-1);
+}
+
 .dp__cal-title {
   display: inline-flex;
   align-items: center;
@@ -2519,7 +2534,10 @@
   position: fixed;
   top: var(--s-4);
   inset-inline-end: var(--s-4);
-  z-index: 1000;
+  /* Above every PrimeNG modal mask and overlay, so an error raised by a
+     dialog's save is readable and its ✕ clickable while the dialog is
+     open. The token explains the number. */
+  z-index: var(--z-toast);
   display: grid;
   gap: var(--s-2);
   align-content: start;
@@ -3593,6 +3611,9 @@ input.ef-input[type='number'] {
 
 .es.p-select,
 .es.p-multiselect {
+  /* The gap between label, clear ✕ and caret. The touch tier reads it to
+     keep the ✕'s 48px target between the label and the caret. */
+  --es-gap: 10px;
   width: 100%;
   min-width: 200px;
   background: var(--paper-alt);
@@ -3602,7 +3623,7 @@ input.ef-input[type='number'] {
   padding: 0 10px 0 14px;
   display: inline-flex;
   align-items: center;
-  gap: 10px;
+  gap: var(--es-gap);
   color: var(--text);
   font-size: 14px;
   cursor: pointer;
@@ -3686,11 +3707,14 @@ input.ef-input[type='number'] {
    clearable control (input, number, select, typeahead) is identical. */
 .ef-clear,
 .es .es-clear {
+  /* One size, read again by the touch tier below to size the target and
+     the space it reserves, so the two cannot drift apart. */
+  --ef-clear-size: 22px;
   display: inline-grid;
   place-items: center;
   box-sizing: border-box;
-  width: 22px;
-  height: 22px;
+  width: var(--ef-clear-size);
+  height: var(--ef-clear-size);
   border: 0;
   padding: 0;
   background: transparent;
@@ -4621,32 +4645,55 @@ input.ef-input[type='number'] {
      made room for. The trigger's overhang adds its 1px border, since an
      absolute box is measured from the padding edge. */
   .row-actions__trigger,
-  .ef-clear {
+  .ef-clear,
+  .es .es-clear {
     position: relative;
   }
 
   .row-actions__trigger {
-    margin-block: calc((var(--hit-touch) - 28px) / 2);
-    margin-inline: calc((var(--hit-touch) - 34px) / 2);
+    margin-block: calc((var(--hit-touch) - var(--ef-row-trigger-h)) / 2);
+    margin-inline: calc((var(--hit-touch) - var(--ef-row-trigger-w)) / 2);
   }
 
   .ef-clear {
-    margin: calc((var(--hit-touch) - 22px) / 2);
+    margin: calc((var(--hit-touch) - var(--ef-clear-size)) / 2);
+  }
+
+  /* The select / multiselect ✕ sits in the trigger's flex row, between the
+     label and the caret, 10px (--es-gap) from each. It reserves only the
+     inline room its 48px target still lacks after that gap, so the target
+     ends exactly at the label's edge and at the caret's, and a tap on the
+     caret opens the panel instead of clearing the value. No block margin:
+     the trigger is 40px whether it holds a value or not, and the target's
+     extra 4px above and below overhangs the trigger the way the input ✕
+     does. */
+  .es .es-clear {
+    margin-inline: calc((var(--hit-touch) - var(--ef-clear-size)) / 2 - var(--es-gap));
   }
 
   .row-actions__trigger::after,
-  .ef-clear::after {
+  .ef-clear::after,
+  .es .es-clear::after {
     content: '';
     position: absolute;
   }
 
+  /* A fixed 48px box centred on the trigger, not an inset derived from
+     its size. The inset version measured from the padding edge and from
+     whatever size the row laid the trigger out at, and a phone row drew a
+     47.75px-wide target. The centred box is 48x48 whatever the painted
+     size, border or sub-pixel layout. */
   .row-actions__trigger::after {
-    inset-block: calc((var(--hit-touch) - 28px) / -2 - 1px);
-    inset-inline: calc((var(--hit-touch) - 34px) / -2 - 1px);
+    top: 50%;
+    left: 50%;
+    width: max(var(--hit-touch), 100%);
+    height: max(var(--hit-touch), 100%);
+    transform: translate(-50%, -50%);
   }
 
-  .ef-clear::after {
-    inset: calc((var(--hit-touch) - 22px) / -2);
+  .ef-clear::after,
+  .es .es-clear::after {
+    inset: calc((var(--hit-touch) - var(--ef-clear-size)) / -2);
   }
 
   /* Written as `.pager .pg` to match the base rule's specificity: a bare