updates on the ui changes and more things

src/pages/doormile/dispatch/Dispatch.css

@@ -59,12 +59,34 @@
   background: var(--bg);
   border-bottom: 1px solid var(--border);
   z-index: 1010;
+  /* Nothing in this row may breach the padding above.
+
+     It is a nowrap flex row — logo/batch group, .hdr-stats, #clock — and none
+     of the three declared a shrink priority, so once the intrinsic content
+     width passed the container the whole row spilled past the 24px gutter and
+     the clock ended up ~8px from the window edge. Width goes missing here
+     without the viewport changing: Dispatch renders inside .dai-page, which
+     body.dai-docked narrows by the assistant dock, so opening MileTruth is
+     what takes the room.
+
+     `min-width: 0` on a flex CONTAINER does nothing by itself; it is set on
+     the children below. This declares the intent the three rules share. */
+  gap: 12px;
+  min-width: 0;
 }
 
 .dispatch-container .logo {
   display: flex;
   align-items: center;
   gap: 12px;
+  /* First to give up space, and deliberately so. This group holds the page
+     title, the hub selector and the batch label — the batch label can
+     truncate and still be read, whereas a half-clipped date or a cut-off
+     clock is just broken. A flex item defaults to min-width:auto and refuses
+     to go below its content width, which is what forced the overflow onto
+     the items to its right. */
+  min-width: 0;
+  overflow: hidden;
 }
 
 /* The badge is sized to the D ITSELF, not to the image file.
@@ -283,6 +305,25 @@
   margin-right: 16px;
   min-width: 0;
   flex-wrap: nowrap;
+  /* Shrinkable, but only after the logo group has given up what it can — and
+     never below the date chip, which is the one control in here an operator
+     has to be able to read and click. The chip declares its own
+     flex-shrink: 0 below; the revenue and orders chips absorb the squeeze
+     first, which is right: they are readouts, not controls. */
+  flex: 0 1 auto;
+}
+
+/* The date chip is a control, not a readout. It keeps its size while the
+   readouts beside it compress. */
+.dispatch-container .hdr-stats .date-chip {
+  flex-shrink: 0;
+}
+
+/* The clock is last in the row and outside .hdr-stats. Fixed size so the
+   gutter above holds: a shrinking clock clips its own digits, which reads as
+   a rendering fault rather than a tight layout. */
+.dispatch-container #clock {
+  flex: 0 0 auto;
 }
 
 /* Tabs */
@@ -10671,4 +10712,23 @@
     transform: scale(2.2);
     opacity: 0;
   }
-}
+}
+/* --------------------------------------------------------------------------
+   Sideways scrollbars, hidden — Firefox fallback for this page's own
+   horizontal-only containers.
+
+   Chrome, Edge and Safari are already covered globally by the
+   ::-webkit-scrollbar:horizontal rule in globalPolish.css. Firefox has no
+   per-axis scrollbar control, so these three are named explicitly. Each is
+   safe: .batch-scroll and #strat-row both set overflow-y: hidden, and the
+   compare timeline only ever scrolls sideways — none of them has a vertical
+   bar that `scrollbar-width: none` could take away.
+
+   Scrolling itself is untouched. overflow-x stays `auto`.
+   -------------------------------------------------------------------------- */
+.dispatch-container .batch-scroll,
+.dispatch-container #strat-row,
+.dispatch-container .compare-timeline-scrollable {
+  scrollbar-width: none;
+  -ms-overflow-style: none;
+}