/* sks-global.css — loaded by templates/layout/base.html on EVERY page, right after theme.css (render-blocking):
   the layout-critical rules must be present at first paint. Until 2026-09-14 the container escape lived only in
   sks-bc-page.css, loaded inside the page body → the page first painted inside Cornerstone's 1280 px container
   and widened once that file arrived (the "shrinks, then loads" flash). */

/* Cornerstone wraps the page block in .body > .container (max-width 1280px, side padding); the ported Shopify
   pages are full-bleed → neutralise the container for them (same rule as sks-bc-page.css, here for first paint). */
.body > .container:has(.sks-pdp, .sks-plp, #sks-choose-kilt) { padding-left: 0; padding-right: 0; max-width: none; }
.body:has(.sks-pdp, .sks-plp, #sks-choose-kilt) { margin-top: 0 !important; padding-top: 0 !important; }

/* No horizontal scrollbar anywhere: `100vw` includes the vertical scrollbar on Windows (17 px) — the footer's
   full-bleed hack and the two page stylesheets that used it are fixed at the source, this is the safety net.
   `clip` does not create a scroll container (sticky headers keep working). */
html, body { overflow-x: clip; }

/* SKS — Dawn font variables.
 * The ported section CSS refers to var(--font-heading-family) / var(--font-body-family).
 * Those were only declared on .sks-pdp and .sks-plp (assets/sks/css/sks-bc-page.css), so on
 * any page without one of those wrappers the variable was undefined, the font-family
 * declaration became invalid and the text fell back to BigCommerce's Karla / Montserrat.
 * Declared here at the root so they resolve everywhere. This only sets the variables — it
 * does not change the font of anything that does not already ask for them.
 */
:root {
  --font-body-family: Assistant, sans-serif;
  --font-heading-family: Assistant, sans-serif;
  --font-body-scale: 1.0;
  --font-heading-scale: 1.0;
}

/* ---- Reviews.io floating widget: right edge -------------------------------
 * The widget's own stylesheet (assets.reviews.io/css/widgets/floating-widget.css)
 * puts the vertically-centred tab on the RIGHT by default; the per-widget settings
 * saved in Reviews.io (June 2023) override that to the left with these same
 * variables, injected as "[data-widget-id=…] .FloatingWidget-prefix .FloatingWidget".
 * The owner wants it on the right (2026-09-17), so the right-side defaults are put
 * back here with a more specific selector. The launcher's corner rounding is set
 * inline by the script from the same left-side setting, hence the important.
 * Remove this block if the position is ever changed to Right inside Reviews.io.
 */
.reviews-io-floating-widget[data-widget-id] .FloatingWidget-prefix .FloatingWidget.FloatingWidget--positionVerticalCenter {
  --launcher-position-left: auto;
  --launcher-position-right: 0px;
  --panel-position-left: auto;
  --panel-position-right: 0px;
}

.reviews-io-floating-widget[data-widget-id] .FloatingWidget-prefix .FloatingWidget--positionVerticalCenter .R-LauncherButton {
  border-radius: 2px 0 0 2px !important;
  /* owner 2026-09-17: a slimmer tab — the script sets min-width 160px / min-height 155px inline */
  height: auto !important;
  max-width: 150px !important;
  min-height: 0 !important;
  min-width: 150px !important;
  width: 150px !important;
}