/* =====================================================================
   ERP shop fixes — build #255 (shop mobile audit 2026-10-23).
   CP's own theme sheets stay byte-identical (ditto rule); every repair
   lives here, loaded LAST in the layout head. Rules are phone-scoped
   (@media max-width 767px) unless the defect is width-independent
   (the loader cap and the login email rule — see their comments).
   ===================================================================== */

/* X1 — CP's #Page_loader veil only lifts when the hero slider's
   window-load chain completes; when anything in that chain stalls it
   blocks every tap for seconds. Cap its lifetime at ~1.5s on every
   width: the element stays (CP chrome), it just can never outstay
   the load. Final rendered pages are unchanged. */
#Page_loader {
  animation: erpLoaderKill .4s ease 1.5s forwards;
}
@keyframes erpLoaderKill {
  to { opacity: 0; visibility: hidden; pointer-events: none; }
}

/* T5 — the theme styles .login_form text/password/date/file inputs
   but never [type=email] (CP's field was type=text; the port made it
   type=email and the box styling fell off, on every width). Give the
   email field the theme's own box, identical to the password rule. */
.login_form input[type="email"] {
  background: #fff;
  border: #ccc 1px solid;
  padding: 12px 18px;
  width: 100%;
  border-radius: 10px;
}

/* T9 — the cookie bar has no colour rule of its own and inherits dark
   body text onto the navy footer. Match the footer's light text.
   (The duplicated copyright line was composition, fixed in #255's
   fragment rename — not CSS.) */
.ck_bar, .ck_bar p {
  color: #fff;
}

/* Cookie notice bar (#255 addendum; mechanics + wording follow the
   legal check hidden_files/shop-cookie-legal-20261023/REPORT.md).
   CP's .ck_bar was an unstyled block at the foot of the page; it is
   a slim strip at the TOP of the page that stays until the visitor
   clicks Accept. Non-blocking by design: no veil, no scroll/click
   lock, and the page stays fully usable underneath.
   Build #272 mechanism change: the bar markup moved to the START
   of <body> (layout cookieBar fragment) and the bar became
   position:sticky in normal flow, replacing the #255 fixed overlay
   whose JS-applied body offset only landed at DOMContentLoaded —
   the fixed bar had covered the whole header, hamburger included,
   for the first seconds of every load (investigation:
   hidden_files/shop-menu-latency-20261024/REPORT.md).
   Build #274 mechanism change (owner catch 2026-10-25: the page
   scrolled into screens of blank below the footer on BOTH shops;
   investigation: hidden_files/shop-overscroll-20261025/REPORT.md):
   WebKit folds a <body>-child sticky element with a document-
   height constraint rectangle into the document's scrollable
   overflow, so the sticky bar fed the overscroll. The bar is
   therefore position:fixed again (its pre-#272 geometry), and its
   place in the flow is held by the #ck_spacer placeholder rendered
   right after it in the same fragment: a pure-CSS in-flow block
   whose per-breakpoint heights (below) are the bar's own rendered
   heights, measured live at every width. The header thus starts
   below the bar from the first parse — no JS offset, no cover, no
   jump; every #272 guarantee survives. Same z-index and visuals;
   ditto.js keeps only show/hide (Accept / footer re-open) and
   toggles bar AND spacer together; hiding is display:none so the
   space simply closes. For returning visitors the head's pre-paint
   script sets data-ck="off" on <html> and the rule below hides
   bar and spacer before first paint — no flash, no cover, no
   jump. */
#ck.ck_bar {
  position: fixed;
  top: 0;
  left: 0;
  right: 0;
  z-index: 2000;
  display: flex;
  align-items: center;
  justify-content: center;
  flex-wrap: wrap;
  gap: 6px 14px;
  padding: 8px 12px;
  background: #173f5f;
  box-shadow: 0 1px 6px rgba(0, 0, 0, 0.3);
}
#ck.ck_bar p {
  margin: 0;
  font-size: 14px;
}
#ck.ck_bar a {
  color: #fff;
  text-decoration: underline;
}
#ck.ck_bar .ck_btn {
  white-space: nowrap;
  padding: 6px 20px;
}

/* Build #274: the in-flow placeholder that holds the fixed bar's
   place (see the bar rule above). Heights are the bar's own
   rendered heights per width band, measured live with the shop's
   webfont loaded (hidden_files/build274/runs/ck-heights-*.json):
   the bar's text wraps to 3 lines at <=463px, 2 lines to 874px,
   1 line (button still stacked) to 987px, and one row beyond. */
#ck_spacer {
  height: 54px;
}
@media (max-width: 987px) {
  #ck_spacer {
    height: 82px;
  }
}
@media (max-width: 874px) {
  #ck_spacer {
    height: 104px;
  }
}
@media (max-width: 463px) {
  #ck_spacer {
    height: 126px;
  }
}

/* Build #272: pre-paint suppression for returning visitors — the
   inline <head> script sets data-ck="off" when cp_cookie_ok is
   already recorded, so the bar never paints for them. Build #274:
   the flag hides the placeholder too, so no space is reserved
   either. ditto.js mirrors the same state in the attribute when
   it shows/hides. */
html[data-ck="off"] #ck,
html[data-ck="off"] #ck_spacer {
  display: none;
}

/* The footer's "Cookie notice" withdraw link. */
.ck_notice {
  text-align: center;
  margin: 6px 0 0;
}
.ck_notice a {
  text-decoration: underline;
}

/* Product share links (AddThis replacement, #255): plain anchors
   completed by ditto.js; give them the spacing the toolbox had. */
.dtl-share a {
  display: inline-block;
  padding: 6px 8px;
  font-size: 16px;
}

/* Top bar — exactly ONE row (build #256, owner ask 2026-10-23).
   Root cause (measured on the live shop, 1280px): the strip rendered
   44px tall with ~12px of empty blue under the content and the phone
   and email sitting on different baselines. CP's theme rule
   .contct-dtl span { display:inline-block; margin: 7px 0 2px }
   applies recursively to the number span the port nests inside the
   phone span, inflating the left line box to ~40px of mixed-baseline
   inline-blocks. PRE-EXISTING, not a #255 regression: the same
   double-height strip is visible in the #255 audit's pre-build
   1280px screenshot (shots/trafa-home-1280.png); #255's cookie strip
   stacks cleanly above it (body padding == cookie height, strip
   directly beneath). Fix: flatten the strip into a single centred
   flex row — no wrap, content vertically centred, flush to the top
   of the header (and directly under the cookie strip while that
   shows, since the theme JS offsets the body by its height). */
.top-bg .row {
  flex-wrap: nowrap;
}
.top-bg .row > div {
  display: flex;
  align-items: center;
}
.top-bg .row > div:last-child {
  justify-content: flex-end;
}
/* The right column's two blocks were floats; as flex items their
   DOM order would flip them, so pin CP's visual order: the Wishlist
   block left, the social icons right. */
.top-bg .whislist {
  order: 1;
  float: none;
  margin: 0;
}
.top-bg .top_social {
  order: 2;
  float: none;
  margin: 0;
}
@media (min-width: 992px) {
  /* Desktop/tablet only: at <=991px .contct-dtl is the Call-Us
     dropdown panel (position:absolute, toggled) — never flatten it. */
  .top-bg .contct-dtl {
    display: flex;
    align-items: center;
    flex-wrap: nowrap;
    gap: 0 18px;
  }
  .top-bg .contct-dtl span {
    margin: 0;
    padding-left: 0;
    padding-right: 0;
    display: inline-flex;
    align-items: center;
    white-space: nowrap;
  }
}
@media (max-width: 767px) {
  /* Phone: the strip stays one slim row — compress, never wrap. */
  .top-bg .top_social a {
    margin: 0 3px;
    line-height: 24px;
  }
  .top-bg .whislist {
    padding: 3px 8px;
    white-space: nowrap;
  }
  .top-bg .shownext p {
    margin: 0;
    white-space: nowrap;
  }
}

/* Login / forgot / reset form rhythm (build #256, owner ask
   2026-10-23). Measured against CP's live login (1280px): CP
   separates the stacked inputs by 8px (its fields sit in mt-2
   wrappers), leaves 16px above the Remember-me row, aligns the
   custom checkmark 2px below the label top (on the text line), and
   18px between the label and the submit. The port dropped CP's
   wrappers, and the theme's .login_form input rules carry no
   margins — so the ERP form stacked flush: Email bottom == Password
   top == row top == submit top, all gaps 0, checkmark riding 2px
   high against its label. Restore CP's rhythm here. Scoped to
   .login_box (login/forgot/reset): the register form lives in
   .reg_box on a padded grid and does not have the defect. */
.login_box .login_form input[type="email"],
.login_box .login_form input[type="password"] {
  margin-bottom: 8px;
}
.login_box .login_form form > .row {
  margin-top: 8px;
}
.login_box .login_form .checkmark {
  top: 2px;
}
.login_box .login_form input[type="submit"] {
  margin-top: 8px;
}
@media (max-width: 767px) {
  /* Keep #255's T5 phone breathing room (12px) for the stacked
     login fields — same value it has today at phone widths. */
  .login_box .login_form input[type="email"],
  .login_box .login_form input[type="password"] {
    margin-bottom: 12px;
  }
  /* CP keeps Remember-me and Forgot-password on ONE line at phone
     widths too; Bootstrap's col-sm-6 stacks them below 576px in the
     port. Hold the row at 50/50, link right-aligned, never wrap. */
  .login_box .login_form form > .row {
    flex-wrap: nowrap;
  }
  .login_box .login_form form > .row > div {
    flex: 0 0 50%;
    max-width: 50%;
  }
  .login_box .login_form form > .row > div:last-child {
    text-align: right;
  }
}

/* =====================================================================
   Build #264 — shop mobile cards + click feedback & load performance
   (owner catches 2026-10-24 04:32–04:48 EDT).
   ===================================================================== */

/* M1 — CARD PRICE OVERLAP (owner screenshot: the two-line
   "Wholesale Price Request" text spilled over the Category line).
   CP's conditional.css pins .pro_price to height:20px with a 22px
   line-height; a price treatment that wraps to two lines at phone
   widths (the wholesale-request and enquiry links) overflows the
   fixed slot onto .pro_cate, whose own height is likewise pinned.
   On CP the same treatment is a contained button that wraps inside
   itself and pushes the lines below it down. Containment, then:
   both blocks size to their content with the old heights as
   minimums — single-line cards render exactly as before (the old
   heights), wrapped treatments grow the card instead of
   overlapping. Width-independent on purpose: the wrap depends on
   the card's column width, not on one breakpoint. */
.pro_price {
  height: auto;
  min-height: 20px;
}
.pro_cate {
  height: auto;
  min-height: 31px;
}

/* M2 — the phone header's cart (build #264 template addition in
   mainHeader): CP shows the cart icon + count badge inline on
   phones; the panel cart (.top_item_sec) is display:none at
   <=991px, so the phone-only anchor mirrors the panel badge's own
   styling (.item_lst em) and is hidden wherever the panel shows. */
.mob_cart {
  display: none;
}
@media (max-width: 991px) {
  .mob_cart {
    display: inline-block;
    position: relative;
    padding: 4px 6px;
    line-height: 1;
  }
  .mob_cart img {
    width: 26px;
    height: auto;
    vertical-align: middle;
  }
  .mob_cart em {
    position: absolute;
    width: 20px;
    height: 20px;
    border-radius: 50%;
    background: #d83457;
    font-size: 10px;
    color: #fff;
    text-align: center;
    line-height: 20px;
    font-style: normal;
    font-weight: 700;
    right: -4px;
    top: -4px;
  }
}

/* M3 — the cookie bar must never overlay the OPEN mobile menu
   (owner, 2026-10-24; the OFN audit proved the layering failure by
   hit-test on the sister shop). ditto.js flags <body> with
   .shop-nav-open while the nav collapse is open; the bar slides
   out of the way and returns when the menu closes (if still
   unaccepted). The bar otherwise keeps its #255 layering. */
#ck.ck_bar {
  transition: transform 0.25s ease;
}
body.shop-nav-open #ck.ck_bar {
  transform: translateY(-110%);
}

/* M4 — CLICK FEEDBACK (the platform standard of app-ui.js #237/#242,
   ported to the shop by ditto.js): a top progress bar runs on any
   navigation click / form submit; the watchdog asserts the same
   bar + a busy cursor when a click produces no movement within
   ~0.5s, escalating to a "Still working..." toast; AJAX controls
   wear .zx-pending (spinner at the click point); the cart region
   dims under .shop-loading while its morph is in flight; POST
   submit buttons wear .shop-busy-btn and the form refuses a
   second submit. */
#shop-progress {
  position: fixed;
  top: 0;
  left: 0;
  height: 3px;
  width: 0;
  background: #d83457;
  z-index: 3000;
  opacity: 0;
  pointer-events: none;
}
#shop-progress.shop-on {
  opacity: 1;
  width: 82%;
  transition: width 9s cubic-bezier(.08, .82, .17, 1), opacity .25s ease;
}
/* Build #276: on touch viewports the 3px bar hides under the
   browser's own chrome — the owner's dead-feel report (§3.5) had
   the bar firing yet invisible in practice. 5px on coarse pointers
   keeps it perceptible; mouse viewports keep 3px. */
@media (pointer: coarse) {
  #shop-progress {
    height: 5px;
  }
}
html.shop-stalled, html.shop-stalled * {
  cursor: progress !important;
}
#shop-toast {
  position: fixed;
  left: 50%;
  bottom: 26px;
  transform: translateX(-50%);
  max-width: calc(100vw - 32px);
  background: rgba(23, 43, 66, 0.95);
  color: #fff;
  font-size: 14px;
  padding: 10px 18px;
  border-radius: 24px;
  box-shadow: 0 4px 18px rgba(0, 0, 0, 0.35);
  z-index: 3000;
  text-align: center;
}
/* Build #274: fixed, not absolute — ditto.js appends the aria-live
   region at the end of <body>, where its absolute 1px box sat ~1px
   below the footer's bottom and was the one measured overhang past
   the footer (hidden_files/shop-overscroll-20261025/REPORT.md).
   A fixed 1px box never feeds document scrollable overflow in any
   engine; the aria-live function is unchanged. */
.shop-visually-hidden {
  position: fixed;
  top: 0;
  left: 0;
  width: 1px;
  height: 1px;
  overflow: hidden;
  clip: rect(0 0 0 0);
  white-space: nowrap;
}
.zx-pending {
  position: relative;
  pointer-events: none;
  opacity: 0.65;
}
.zx-pending::after,
.shop-busy-btn::after {
  content: "";
  display: inline-block;
  vertical-align: -2px;
  width: 13px;
  height: 13px;
  margin-left: 8px;
  border-radius: 50%;
  border: 2px solid currentColor;
  border-top-color: transparent;
  animation: shop-spin .7s linear infinite;
}
.shop-busy-btn {
  position: relative;
}
@keyframes shop-spin {
  to { transform: rotate(360deg); }
}
#crt_container.shop-loading {
  position: relative;
  opacity: 0.55;
  pointer-events: none;
}

@media (max-width: 767px) {

  /* T1 — the product gallery image is a fixed 500px box (width/height
     attributes + MagicZoom) inside a full-width phone column, laying
     the whole page out ~545px wide. Constrain the gallery to its
     column; desktop markup/CSS untouched. */
  .dtl_lft, .dtl_img, .dtl_img figure, .dtl_img .MagicZoom,
  .dtl_images, .dtl_images figure {
    max-width: 100%;
  }
  .dtl_img img, .MagicZoom img, .mz-figure img, .dtl_images img {
    max-width: 100% !important;
    height: auto !important;
  }
  .thm_img img {
    max-width: 100%;
    height: auto;
  }

  /* T5 — stacked login fields need breathing room at phone widths so
     the remember-me checkmark row clears the password field; 16px
     inputs stop iOS zooming on focus. */
  .login_form input[type="email"],
  .login_form input[type="password"] {
    margin-bottom: 12px;
    font-size: 16px;
  }

  /* T6 — checkout delivery inputs render at 11px; 16px at phone
     widths kills the iOS focus zoom and is legible on Android. */
  #checkoutForm .form-control {
    font-size: 16px;
  }

  /* T4 (minor) — the header search keyword field is 14px. */
  .search_sec input[type="text"] {
    font-size: 16px;
  }

  /* T7 — commerce tap targets: qty steppers up to 40px boxes, cart
     row actions padded to ~36px touch boxes so wishlist and delete
     stop sitting a mis-tap apart. */
  .qty_action_creator,
  .cart_qty .qty_btn {
    min-width: 40px;
    min-height: 40px;
  }
  .cart_actions a {
    display: inline-block;
    padding: 9px;
  }

  /* T8 — product tabs fall back to a bulleted list on phones; render
     them as the tab row they are. */
  ul.tb_link, ul.tab_linkss {
    list-style: none;
    padding-left: 0;
  }
  ul.tb_link li, ul.tab_linkss li {
    display: inline-block;
  }
}

/* =====================================================================
   Build #272 — shop menu open latency (owner catch 2026-10-24
   21:55 EDT: the phone menu took seconds to show). Root cause and
   evidence: hidden_files/shop-menu-latency-20261024/REPORT.md. The
   bar half of the fix was the sticky rework at #ck.ck_bar above —
   superseded by build #274 (fixed bar + in-flow #ck_spacer; the
   sticky bar fed WebKit's scrollable-overflow accounting, see the
   bar rule's comment); every guarantee it bought survives via the
   spacer. This section is the early-toggle half, unchanged by
   #274: the inline handler in the layout's mainHeader fragment
   opens the panel with a zx-open class until Bootstrap's collapse
   machinery loads, then hands over.
   ===================================================================== */
@media (max-width: 991px) {
  /* The panel shown by the early handler (Bootstrap not loaded
     yet). CP's conditional.css hides .collapse with
     display:none !important and shows it as an absolutely
     positioned dropdown under .collapse.show (display:block
     !important, top 56px, right 10px, background #cb2044) — so
     zx-open mirrors the .show declarations exactly, and the
     early-opened panel renders identically to the Bootstrap-opened
     one. Bootstrap's own rules take over once its scripts arrive;
     the handler maps zx-open onto show at handover so the two
     never fight. */
  .nav-collapse.zx-open {
    display: block !important;
    position: absolute;
    z-index: 99;
    background: #cb2044;
    top: 56px;
    right: 10px;
  }
  /* Full-open should feel instant too: Bootstrap's stock height
     transition is 350ms; ~200ms reads as immediate while still
     animating. (First frame was never gated on this — cosmetic.) */
  .nav-collapse.collapsing {
    transition-duration: 0.2s;
  }
}

/* =====================================================================
   Build #353 — storefront fluid layout (owner screenshots 2026-11-09:
   the item detail buy panel cramped/colliding; the cart page's right
   rail cut off mid-button — "Checkou", "Clear Ca"). Measured on the
   pre-build tree against a restored Trafa book (Playwright, guest;
   full table in hidden_files/build353/RUN-REPORT.md):
   - CP's conditional.css pins .container to width:1230px (its own
     <=1280px media queries narrow it to 98%/100% there, so the pin
     itself is not what clips) — what clips is what inside assumed
     the fixed width:
   - .cart_right { width:22%; float:right } (conditional.css) nested
     by the port inside a Bootstrap col-lg-4: 22% OF THE COLUMN —
     ~90px at 1366px, ~65px at 1024px. Its w-100 buttons clip their
     own text at EVERY width (the owner's photo), and the page's
     scroll width grows +36..+56px across 1024-1280px.
   - .dtl_lft { width:580px } fixed inside col-lg-5 (~427px at
     1024px): the gallery overlaps the buy column; .dtl_rgt at
     39-50% OF col-lg-7 leaves the buy panel ~233px while its
     .dtl_btns row cannot wrap — .qnt_bg alone measured 69px past a
     1024px viewport, "Lead Time" colliding with the size pills.
   - .prod_list { margin: 0 -15px } (designed against a padded
     container; this one has padding:0) bleeds the listing/category
     grid past both edges in the fluid band (measured -4/+4px at
     800-1280px).
   Repairs are override-layer only (CP sheets byte-identical) and
   band-scoped where the wide-desktop rendering must not move.
   ===================================================================== */

/* The container itself, in the owner's fix shape: fluid with the
   1230px cap kept. (conditional.css's <=1280px rules carry
   !important and keep governing that band — 98%/100% there is
   fluid too; above it this rule replaces the fixed width with the
   same 1230px the layout was designed at, so nothing moves.) */
.container {
  width: 100%;
  max-width: 1230px;
}

/* The cart rail takes its column's full width at every width —
   CP's own <=767px block already sets exactly this shape; the
   defect was the band above it. */
.cart_right {
  width: 100%;
  float: none;
}

@media (max-width: 1280px) {
  /* Listing/category card grid: stop the -15px bleed past a fluid
     container's edges. The cards' own margins keep the rhythm. */
  .prod_list {
    margin-left: 0;
    margin-right: 0;
  }
  /* Item detail: the gallery takes its column's width (its 500px
     frame and image capped inside it) and the buy panel takes its
     full column instead of 39-50% of it; the buy button row may
     wrap instead of spilling past the panel. At <=991px the theme
     already stacks the columns and #255's phone rules agree with
     these values. */
  .dtl_lft {
    width: 100%;
  }
  .dtl_images, .dtl_images figure, .dtl_img, .dtl_img figure {
    max-width: 100%;
  }
  .dtl_images img, .dtl_img img {
    max-width: 100%;
    height: auto;
  }
  .dtl_rgt {
    width: 100%;
    float: none;
  }
  .dtl_btns {
    flex-wrap: wrap;
  }
  .qnt_bg {
    max-width: 100%;
  }
}

/* #353 checkout address picker: an element carrying [hidden] must
   stay hidden against the theme's display rules for these blocks
   (the picker script toggles the attribute). */
#deliveryAddressBox[hidden],
.addr-picker[hidden],
.addr-new-note[hidden],
#addrSummaryFallback[hidden],
#addrSummaryDefault[hidden] {
  display: none !important;
}
.addr-summary-line {
  margin-bottom: 10px;
}

/* =====================================================================
   Build #353 RIDER — phone-top parity with the live CP shop (owner
   photo + asks, 2026-11-13 22:35/22:37). At phone width the top of
   every Trafa shop page is: (1) a SLIM cookie strip — the #274 bar
   wrapped its text to three lines and stacked the Accept button,
   a 126px navy block over the header; the owner's standing rule is
   a slim fixed top strip; (2) the utility bar in ONE row — Call Us,
   Make Payment, Wishlist and the five social icons on a single
   line, nothing dropped (the #256 flex row still wrapped below
   ~460px: the icons spilled onto second and third lines inside the
   right column); (3) the logo/icon row, unchanged. Widths above
   767px render exactly as before, spacer bands included.
   ===================================================================== */
@media (max-width: 767px) {
  /* (1) Cookie strip, slim: a single flex line — compact text
     wrapping inside its own column (the legal wording is
     unchanged), the Accept button inline beside it, never stacked
     and never full-width. */
  #ck.ck_bar {
    flex-wrap: nowrap;
    gap: 4px 10px;
    padding: 6px 10px;
  }
  #ck.ck_bar p {
    font-size: 12.5px;
    line-height: 1.3;
  }
  #ck.ck_bar .ck_btn {
    padding: 4px 14px;
    font-size: 13px;
  }
  /* (2) Utility bar, one row: the right column's two blocks share
     one line, and the icon row cannot wrap inside its own box. */
  .top-bg .row > div:last-child {
    flex-wrap: nowrap;
    gap: 0 6px;
  }
  .top-bg .top_social {
    display: flex;
    align-items: center;
    flex-wrap: nowrap;
  }
  .top-bg .top_social a {
    font-size: 12.5px;
    line-height: 20px;
    margin: 0 2px;
  }
  .top-bg .whislist {
    display: flex;
    align-items: center;
    flex-wrap: nowrap;
    font-size: 12.5px;
    padding: 2px 4px;
  }
  .top-bg .whislist a {
    margin-right: 6px;
    white-space: nowrap;
  }
  .top-bg .whislist a:last-child {
    margin-right: 0;
  }
  .top-bg .shownext a {
    font-size: 13px;
    white-space: nowrap;
  }
}

/* The #274 spacer bands for the slim strip (the placeholder holds
   the fixed bar's exact rendered height). Measured live on the
   rider jar at 1px steps, the #274 method (see
   hidden_files/build353/RUN-REPORT-RIDER.md): the slim bar renders
   77px at <=374px, 61px at 375-513px and 45px at 514-767px. The
   768-987px bands keep their #274 heights above; these bands sit
   later in the sheet and override the <=874px band inside phone
   widths only. */
@media (max-width: 767px) {
  #ck_spacer {
    height: 45px;
  }
}
@media (max-width: 513px) {
  #ck_spacer {
    height: 61px;
  }
}
@media (max-width: 374px) {
  #ck_spacer {
    height: 77px;
  }
}

/* =====================================================================
   DOCS+RESTORE (2026-11-15): the address-batch riders' cart and
   stepper rules, preserved alongside the restored #353 sections
   above (they were written against the pre-restore sheet and their
   measured fixes stand). The riders' two-line phone-utility variant
   is deliberately NOT carried: it conflicted with the owner-approved
   #353 rider one-row utility bar restored above, which governs.
   ===================================================================== */

/* Cart fit: CP's legacy .cart_right { width:22%; float:right }
   (conditional.css) was written for CP's float layout; inside the
   clone's Bootstrap col-lg-4 it crushes the Order Summary into a
   sliver whose content then pushes the page wider than the viewport.
   The summary takes its full column at every width. */
.cart_area .cart_right {
  width: 100%;
  float: none;
}

/* Quantity steppers (cart .cart_qty, product .qnt_bg) render as ONE
   joined unit: one shared border, a fixed narrow centred input and
   real buttons — not a loose full-width input between two slivers. */
.cart_qty,
.qnt_bg {
  display: inline-flex;
  align-items: stretch;
  border: 1px solid #c9d4d8;
  border-radius: 6px;
  overflow: hidden;
  background: #fff;
  vertical-align: middle;
}
.cart_qty .qty_btn,
.qnt_bg .qty_action_creator {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  min-width: 40px;
  min-height: 38px;
  padding: 0 10px;
  background: #eef3f4;
  border: 0;
  cursor: pointer;
}
.cart_qty .zx_qty,
.qnt_bg .zx_qty {
  width: 52px;
  min-height: 38px;
  text-align: center;
  border: 0;
  border-left: 1px solid #c9d4d8;
  border-right: 1px solid #c9d4d8;
  border-radius: 0;
  box-shadow: none;
  outline: none;
}
