/* Device Display Card widget (ADO #124642, SRS Part14).
   Scoped under .udd — rendered by Views/Widgets/DeviceDisplay.cshtml.
   Fonts 'Unbeatable' / 'UMobile Display' are loaded globally; only font-family is declared here. */

.udd {
    font-family: 'Unbeatable', 'UMobile Display', sans-serif;
    padding: 40px 0;
    overflow: hidden;
}

.udd .udd-inner {
    max-width: 1280px;
    margin: 0 auto;
    padding: 0 24px;
}

.udd .udd-header {
    text-align: center;
    margin-bottom: 24px;
}

.udd .udd-title {
    margin: 0 0 8px;
    font-size: 32px;
    line-height: 1.15;
    font-weight: 700;
    color: #1A1A1A;
}

.udd .udd-subtitle {
    margin: 0;
    font-size: 16px;
    line-height: 1.5;
    color: #4D4D4D;
}

/* ── Carousel ──────────────────────────────────────────────────────────── */

/* The carousel bleeds into the container gutter (the -24px mirrors .udd-inner's padding).
   Without it the track is 1232px wide and four 294px cards + three 16px gaps already eat
   1224px — the 5th card would peek by ~8px instead of the partial preview SRS #1 asks for.
   Bleeding both gutters puts the 5th card ~40px into view. */
.udd .udd-viewport {
    position: relative;
    margin: 0 -24px;
}

/* Flex row + stretch: within one carousel every card stretches to the tallest (SRS #11).
   No scrollbar (AB#139713 round 2). Round 1 added one for the desktop mouse, but it sits at
   the BOTTOM of a ~470px-tall track, so reaching it still meant scrolling the page past a
   whole card — which is the complaint the bug was filed over, and QC bounced the fix for it.
   Navigation is the arrow pair below the list (SRS #2, positioned there by #134520) plus the
   mouse drag that `cursor: grab` advertises and the JS implements alongside sync(). */
.udd .udd-track {
    display: flex;
    align-items: stretch;
    gap: 16px;
    overflow-x: auto;
    /* `proximity`, not `mandatory`: mandatory snaps the 5th card's partial preview back to
       the edge the moment the user lets go, which defeats the preview. */
    scroll-snap-type: x proximity;
    scroll-behavior: smooth;
    -webkit-overflow-scrolling: touch;
    padding: 4px 24px 8px 0;    /* back to 8: the extra 6px only existed to clear the bar */
    cursor: grab;
    scrollbar-width: none;      /* Firefox */
}

/* Set only while the JS drag handler is actually dragging — `user-select: none` here (not
   on the base rule) because shoppers still need to select the name/price text otherwise. */
.udd .udd-track--dragging {
    cursor: grabbing;
    user-select: none;
}

/* Fewer cards than a full row: centre them instead of hugging the left edge (Figma).
   Toggled from JS only while the track does NOT overflow — hard-coding
   `justify-content: center` would clip the leading cards once it does. */
.udd .udd-track--center {
    justify-content: center;
    padding-left: 24px; /* symmetric padding so "centred" really is centred */
}

.udd .udd-track::-webkit-scrollbar {
    display: none;              /* Chrome/Safari — arrows, drag and swipe are the navigation */
}

/* ── Card (SRS #3: 294px wide, radius 8, white surface, height from content) ── */

.udd .udd-card {
    flex: 0 0 294px;
    width: 294px;
    scroll-snap-align: start;
    display: flex;
    flex-direction: column;
    background: #FFFFFF;
    border: 1px solid #E6E6E6;
    border-radius: 8px;
    /* No top padding — the badge is a tab that hangs off the card's top edge (Figma header
       frame: 18px L/R, 0 top, 12px bottom). */
    padding: 0 18px 18px;
    cursor: pointer;
}

/* ── Badge (SRS #4) ────────────────────────────────────────────────────── */

/* Full-width row so the badge pill centres horizontally and straddles the card's top edge. */
.udd .udd-badge-slot {
    display: flex;
    justify-content: center;
    min-height: 26px;
    margin-bottom: 12px;
}

.udd .udd-badge-slot--empty {
    visibility: hidden; /* reserves the badge box so card tops stay aligned */
}

.udd .udd-badge {
    display: inline-flex;
    align-items: center;
    gap: 4px;
    margin-top: -1px;           /* swallow the card border so the pill sits flush on it */
    padding: 4px 8px;
    background: #FFFFFF;
    border: 1px solid #E6E6E6;
    border-top: 0;
    border-radius: 0 0 4px 4px; /* Figma: only the bottom corners are rounded */
    box-shadow: 0 2px 4px rgba(0, 0, 0, .06);
    font-size: 14px;
    line-height: 18px;
    font-weight: 600;
    white-space: nowrap;
    color: #00253D;
}

.udd .udd-badge-icon {
    width: 16px;
    height: 16px;
    object-fit: contain;
}

/* ── Device image (SRS #5: 256×192 frame, object-fit contain, no cropping) ── */

.udd .udd-media {
    width: 256px;
    height: 192px;
    max-width: 100%;
    margin: 0 auto 12px;
    border-radius: 8px;
    overflow: hidden;
    display: flex;
    align-items: center;
    justify-content: center;
}

.udd .udd-image {
    max-width: 100%;
    max-height: 100%;
    width: auto;
    height: auto;
    object-fit: contain;
}

/* ── Product name (SRS #6) ─────────────────────────────────────────────── */

.udd .udd-name {
    margin: 0 0 10px;
    min-height: 48px;
    font-size: 20px;
    line-height: 24px;
    font-weight: 600;
    letter-spacing: -0.01em;
    text-align: center;
    color: #1A1A1A;
}

/* ── Variant chips (SRS #8: max 6, wrap, one selected) ─────────────────── */

.udd .udd-chips {
    display: flex;
    flex-wrap: wrap;
    justify-content: center;
    gap: 8px;
    margin-bottom: 12px;
}

.udd .udd-chips--single { display: none; }

.udd .udd-chip {
    padding: 8px 12px;
    border-radius: 8px;
    border: 1px solid #E6E6E6;
    background: #FFFFFF;
    color: #1A1A1A;
    font-family: inherit;
    font-size: 14px;
    line-height: 1;
    font-weight: 600;
    cursor: pointer;
    transition: border-color .15s, color .15s, background .15s;
}

.udd .udd-chip:hover { border-color: #FF9C40; }

/* Figma: the selected chip is a SOLID orange fill with white text — not an outlined chip.
   (SRS #8's colour list is self-contradictory and defers this to FE.) */
.udd .udd-chip.is-selected {
    border-color: #FF7300;
    background: #FF8F33;
    color: #FFFFFF;
}

/* ── RRP (SRS #7: strikethrough styling by slash type) ─────────────────── */

.udd .udd-rrp {
    min-height: 19px;
    margin-bottom: 12px;
    font-size: 16px;
    line-height: 1;
    font-weight: 500;
    text-align: center;
    color: #4D4D4D;
}

.udd .udd-slash-strikethrough { text-decoration: line-through; }

/* "Red Slash" / "Orange Slash" are a coloured DIAGONAL over the label, not a
   coloured horizontal rule — the schema hint on device-variant.slashType spells
   this out ("diagonal red" / "diagonal orange") and QC raised #134521 because
   text-decoration can only ever draw horizontally.
   The bar is a rotated pseudo-element so it tracks the label's width whatever
   the locale or price length. The box has to shrink-wrap the text for that:
   left/right are pinned to the element, so a full-width block would start the
   diagonal out in the card's padding. margin-inline keeps it centred.

   The diagonal is the WHOLE treatment: no text-decoration here. Keeping the
   plain strike underneath (as this rule first did) drew both marks at once, so
   one card read as two of the three slashType options at the same time —
   exactly what QC re-opened #134521 for. "Strikethrough" stays its own option
   above; picking a colour picks the diagonal instead of it, never as well. */
.udd .udd-slash-red,
.udd .udd-slash-orange {
    position: relative;
    width: -moz-fit-content;
    width: fit-content;
    max-width: 100%;
    margin-inline: auto;
    text-decoration: none;
}

.udd .udd-slash-red::after,
.udd .udd-slash-orange::after {
    content: "";
    position: absolute;
    left: -2px;
    right: -2px;
    top: 50%;
    height: 2px;
    border-radius: 1px;
    transform: translateY(-50%) rotate(4deg);
    pointer-events: none;
}

.udd .udd-slash-red::after    { background: #E4002B; }
.udd .udd-slash-orange::after { background: #FF7300; }

/* The markup always emits .udd-rrp (and JS always re-applies a slash class), so
   a variant with no RRP would otherwise render the bare 4px diagonal stub. */
.udd .udd-rrp:empty::after { content: none; }

/* ── Contract type toggle (SRS #9) ─────────────────────────────────────── */

.udd .udd-types {
    display: flex;
    gap: 8px;
    margin-bottom: 12px;
}

.udd .udd-types:empty { display: none; }

.udd .udd-type {
    flex: 1 1 0;
    display: flex;
    align-items: center;
    justify-content: center;
    gap: 12px;
    padding: 8px 10px;
    border-radius: 8px;
    border: 1px solid #E6E6E6;
    background: #FFFFFF;
    color: #000000;
    font-family: inherit;
    font-size: 14px;
    line-height: 1.2;
    font-weight: 500;
    cursor: pointer;
    transition: border-color .15s, color .15s, background .15s;
}

/* ── Radio indicator (Figma: every contract type / period row is a radio row) ──
   16px circle, 1px grey ring when unselected; solid #FF7300 ring with a 6px white
   centre when selected. Rendered as a pseudo-element so the JS re-render paths
   (renderTypes / renderOptions) need no extra markup. */
.udd .udd-type::before,
.udd .udd-option::before {
    content: '';
    flex: 0 0 16px;
    width: 16px;
    height: 16px;
    box-sizing: border-box;
    border: 1px solid #CCCCCC;
    border-radius: 50%;
    background: #FFFFFF;
    transition: border-color .15s, box-shadow .15s;
}

.udd .udd-type.is-selected::before,
.udd .udd-option.is-selected::before {
    border-color: #FF7300;
    box-shadow: inset 0 0 0 4px #FF7300; /* 1px border + 4px inset ⇒ 6px white centre */
}

/* ── Plan title / section title (SRS #9/#10) ───────────────────────────── */

.udd .udd-plan {
    font-size: 16px;
    line-height: 24px;
    font-weight: 700;
    color: #000000;
    margin-bottom: 4px;
}

.udd .udd-section-title {
    font-size: 15px;
    line-height: 20px;
    font-weight: 500;
    color: #000000;
    margin-bottom: 8px;
}

.udd .udd-plan:empty,
.udd .udd-section-title:empty { display: none; }

/* ── Contract options (SRS #11: rows, max 6, selectable → ?period=) ────── */

.udd .udd-options {
    list-style: none;
    margin: 0 0 12px;
    padding: 0;
    display: flex;
    flex-direction: column;
    gap: 9px;
}

.udd .udd-option {
    width: 100%;
    display: flex;
    align-items: center;
    gap: 12px;
    padding: 8px 12px;
    border-radius: 8px;
    border: 1px solid #E6E6E6;
    background: #FFFFFF;
    color: #000000;
    font-family: inherit;
    font-size: 15px;
    line-height: 20px;
    font-weight: 600;
    cursor: pointer;
    text-align: left;
    transition: border-color .15s;
}

/* Figma keeps the row border grey in both states — the radio dot carries the selection. */
.udd .udd-option-label { flex: 1 1 auto; }

.udd .udd-option-price { flex: 0 0 auto; white-space: nowrap; }

/* ── CTA section (SRS #12/#13: vertical stack, bottom of card) ─────────── */

.udd .udd-ctas {
    margin-top: auto; /* pins CTAs to the card bottom when cards stretch to equal height */
    display: flex;
    flex-direction: column;
    gap: 8px;
    padding-top: 8px;
}

.udd .udd-cta {
    display: flex;
    align-items: center;
    justify-content: center;
    min-height: 48px;
    padding: 12px 16px;
    border-radius: 24px;
    font-size: 16px;
    line-height: 24px;
    font-weight: 700;
    text-decoration: none;
    text-align: center;
    transition: opacity .15s;
}

.udd .udd-cta:hover { opacity: .9; }

.udd .udd-cta--orange {
    background: #FF7300;
    color: #FFFFFF;
    border: 1px solid #FF7300;
}

.udd .udd-cta--white {
    background: #FFFFFF;
    color: #FF7300;
    border: 1px solid #FF7300;
}

/* ── Navigation arrows (SRS #2: 36px, disabled at edges, no loop) ──────── */

/* SRS #2 places the pair under the device list, right-aligned (#134520). The row
   is a sibling of .udd-viewport, so it is free of the viewport's gutter bleed and
   the arrows need no absolute positioning to stay clear of the cards.
   Spacing lives on the arrow, not the row: when JS marks both [hidden] the row
   has no in-flow children and collapses to nothing, margin included. */
.udd .udd-nav {
    display: flex;
    justify-content: flex-end;
    gap: 10px;
}

.udd .udd-arrow {
    margin-top: 16px;
    width: 36px;
    height: 36px;
    padding: 0; /* svg centered via flex; spec paddings folded into the 36px hit area */
    box-sizing: border-box;
    display: flex;
    align-items: center;
    justify-content: center;
    border-radius: 50%;
    border: 1px solid #FF7300;
    background: #FFFFFF;
    color: #FF7300;
    cursor: pointer;
    transition: background-color .15s ease, border-color .15s ease, color .15s ease;
    /* Double-tapping the arrow used to zoom the page instead of paging twice: the browser waits for a
       possible second tap before dispatching click. `manipulation` opts out of double-tap-to-zoom on this
       element only — pinch-zoom and page zoom stay available (AB#139714). */
    touch-action: manipulation;
    -webkit-user-select: none;
    user-select: none;
}

/* SRS #2 hover: the usable direction fills solid orange. */
.udd .udd-arrow:not(:disabled):hover {
    background: #FF7300;
    border-color: #FF7300;
    color: #FFFFFF;
}

/* The JS hides the arrows with the `hidden` attribute when the track does not overflow
   (SRS #2: arrows only once the cards exceed the viewport). The rule above sets
   `display: flex` with class specificity, which outranks the user-agent `[hidden]`
   rule — so `hidden` has to be re-asserted here or the arrows stay visible on a
   single-card carousel. */
.udd .udd-arrow[hidden] { display: none; }

/* Edge state (SRS #2: no looping) — a flat grey circle, not a faded orange one. */
.udd .udd-arrow:disabled {
    color: #BBBBBB;
    border-color: #E6E6E6;
    background: #FFFFFF;
    cursor: default;
}

/* ── Mobile (one full card + 7px peek, arrows below-right, swipe by default) ── */

@media (max-width: 767px) {
    /* One knob for the page gutter. Three declarations below MUST stay equal to it —
       `.udd-inner`'s padding, `.udd-viewport`'s right bleed and `.udd-track`'s trailing
       pad — because the card is sized as 100% of the track's content box and the peek is
       whatever is left of the gutter after the gap. Editing one on its own detunes the
       layout silently: set the gutter to 18 here and leave the other two at 16, and the
       card still fills the column and the last card still rests correctly, but the
       viewport's right edge stops at vw-2, so the 7px sliver floats 2px inside the
       screen edge instead of touching it. */
    .udd { padding: 32px 0; --udd-gutter: 16px; }
    .udd .udd-inner { padding: 0 var(--udd-gutter); }
    .udd .udd-title { font-size: 26px; }

    /* AB#135776 (third and fourth report; see AB#133658, AB#134520) — one full card
       plus a 7px peek. Body Table 7 ("Partial next card visible at the right edge")
       and the SRS Part14 *Review comments* both hold: the card is full, and a sliver
       of the next one still shows. What was wrong all along was the SIZE of that
       sliver — the original 80% card exposed ~20% of card 2, which is what QC called
       "hiển thị quá nhiều" on 07/09. The review comments say:
         C32 (PO, 24/07):        "Best to show the full card display so it doesn't
                                  look like its left aligned. Can have this as a UI
                                  option for mobile view configuration"
         C33 → C34 (PO/BA):      arrows stay ("This widget has navigation button").
         C273406452 (BA, 31/07): "design updated. show full card, center aligned
                                  and navigation buttons below"
       Scope caveat, so nobody treats it as settled: the SRS md states its Word
       comments lost their positional anchors. C32, C33 and C34 do all fall between
       the `device-display` and `device-plans` markers; C273406452 does not — it sits
       in a later hash-id batch with no marker near it, and the same phrase "One full
       card display – Center aligned" is buy-1-free-1's own body table (Table 26).
       BA confirmation of scope is still open on AB#135776, as is C32's second sentence
       (a CMS option instead of a hard design change). Do not go back to the 80% card:
       "full card display" and Table 7's partial-next-card are both satisfied by a
       full-width card with a peek measured in single-digit px. */

    /* Bleed RIGHT only, by exactly the page gutter, so the track's overflow area
       reaches the screen edge and card 2 can show through it. The left side keeps
       the gutter: card 1's left edge is the page's content edge. */
    .udd .udd-viewport {
        margin: 0 calc(-1 * var(--udd-gutter)) 0 0;
    }

    /* Same leading-0 / trailing-pad idiom as the base rule, at the mobile gutter.
       `padding-left` MUST stay 0: the card snaps `start` (inherited from the base
       rule) and there is no `scroll-padding` here to cancel the offset, so under
       `x mandatory` any leading pad moves card 1's snap position to `padding-left` —
       measured scrollLeft = 16, which the JS reads as false for `scrollLeft <= 1`,
       leaving the prev arrow enabled on the first card (AB#133647). That is the
       leading-padding trap buy-1-free-1.css:62 documents; a TRAILING pad is safe.
       The trailing pad has ONE job: cancel the viewport's right bleed for the CONTENT
       box, which is what the 100% card measures against. Remove it and the card grows by
       a gutter to the bled width, card 2 starts past the clip edge, and the peek
       disappears — the exact defect this round is about, not a subtle regression.
       It is NOT what keeps the last card inside the gutter; an earlier version of this
       comment claimed that and was wrong. With the card at 100%, `max scrollLeft` works
       out to (N-1)(card + gap) either way, because the pad lands in both `scrollWidth`
       and `clientWidth` and cancels. Measured in Chrome on both variants: 734 = 2x(358+9)
       here, 748 = 2x(358+16) without the bleed. The pad has no say in it.
       The caveat that DOES rest on the pad, and that no check here covers: whether a
       trailing pad counts toward a scroll container's scrollable overflow has interop
       history (Chromium 505105, WebKit 105482). An engine that excludes it yields
       `max = (N-1)(card + gap) - gutter`, parking the last card one gutter short —
       doubled gutter on its left, flush to the screen edge on its right. Worth one pass
       on real iOS Safari; buy-1-free-1.css ships the same idiom and has been accepted.
       gap drops 16 -> 9 so that gap + peek fits the gutter; see the card rule.
       `--center` is listed as well (JS adds it when the track does not overflow) to
       drop its `padding-left: 24px`; plain `.udd .udd-track` already wins on source
       order, so this is belt-and-braces. */
    .udd .udd-track,
    .udd .udd-track--center {
        gap: 9px;
        padding: 4px var(--udd-gutter) 8px 0;
        scroll-snap-type: x mandatory;
    }

    /* 100% of the track's CONTENT box, which the -16px bleed and the +16px trailing
       pad cancel back to the page's content column — so card 1 spans exactly
       [gutter, viewport - gutter], the shape QC accepted on 08/09.
       Card 2 then starts one `gap` (9px) past card 1's right edge and runs into the
       track's right padding, leaving 16 - 9 = 7px of it visible at the screen edge.
       That 7px is the peek AB#135776 is actually about: QC's 07/09 wording was
       "card 2 hiển thị QUÁ NHIỀU" (the old 80% card showed ~20% of it), and the
       08/09 round over-corrected it to zero.
       Read off Figma (Consumer / Web Responsive, mobile frame `3119:135540`, 392
       wide) rather than inferred from a screenshot:
         page content column   x 20 .. 372 (352 wide) — hero, section header, form
                               and FAQ all sit on it, so the gutter is 20/20
         carousel section      x 20, w 372 → runs to the frame's right edge, i.e. it
                               bleeds right by exactly the 20px gutter
         card 1 / card 2       x 0 / x 365 within it, both 353 wide
                               → gap 12, peek = 392 - 385 = 7
       The 20px design gutter is NOT adopted: no widget in this repo uses 20 (they
       are split 16 and 18), so a 20 here would leave this widget's left edge out of
       line with every neighbour on the page. Keeping 16 caps gap + peek at 16, so
       peek keeps the design's 7 (it is the strip QC circled) and gap absorbs the
       shortfall, 12 -> 9.
       `box-sizing` is declared on the rule rather than inherited, mirroring
       `.udd-arrow`. The card carries `padding: 0 18px 18px` plus a 1px border, so under
       `content-box` it is 38px (36 + 2) too wide at every width: card 1 clipped flush to
       the screen edge with no gutter and a negative peek. There is no global preflight to
       lean on here — `_Layout.cshtml` loads bootstrap / `coreclient.css` /
       `style-static.css` only inside `@if (!isAemMode)`, and this widget has
       `RequiresAbpCss = false` (the `WidgetAdapterBase` default), so a page carrying only
       AEM-style widgets takes the `else` branch. Nothing loaded there resets `box-sizing`
       universally: `layout-shell.css` and `nd-header.css` set it on their own selectors
       only. The universal reset then comes solely from the remote
       `clientlib-base.<lcToken>.min.css`, behind a hand-maintained cache token. That
       build does carry one today; this card should not be what breaks when it changes.
       `width` is not redundant with `flex-basis`: it supplies the specified size
       suggestion that clamps the flex item's automatic minimum size, so a long
       `white-space: nowrap` badge label cannot widen the card. Do not remove it. */
    .udd .udd-card {
        flex: 0 0 100%;
        width: 100%;
        box-sizing: border-box;
    }

    /* No `.udd-nav` override on mobile — the base rule's `justify-content: flex-end`
       is what mobile wants too, so the arrows sit flush with the card's right edge.
       Two earlier values were both wrong and are recorded so neither comes back:
         `padding-right: calc((100% - min(80%, 294px)) / 2)` — the offset for a card
           resting CENTRED, but scrollLeft clamps at 0 so card 1 rested flush-left and
           the arrows landed half the leftover width PAST it (35.8px at 390, 44px at
           414, 220.5px at 767). Dead once the card became 100% wide.
         `justify-content: center` — shipped 08/09 reading the SRS review comment
           C273406452 ("show full card, center aligned and navigation buttons below")
           as covering the buttons. QC re-opened the same day with the Figma: the
           card is centred (it is full-width, so trivially so), the ARROWS are right.
           Measured on QC's Figma capture: next-arrow right edge x=395, card right
           edge x=394-396 — flush. So "center aligned" describes the card only.
       This works because `.udd-nav` and `.udd-card` resolve against the SAME box: the
       nav is a sibling of `.udd-viewport`, so it sits on the page content column
       directly, and the card lands on that column too because the viewport's right bleed
       and the track's trailing pad CANCEL (-gutter then +gutter). They are not both zero
       — an earlier version of this comment said so, which inverts the invariant.
       Dropping either breaks it in a different direction: without the bleed the peek is
       clipped away, without the pad the card grows past the column and the arrows end up
       short of its visible edge. */

    .udd .udd-arrow { margin-top: 12px; }
}

/* AB#113536 (BA retest 06/11, "Device Display lệch"): on tablet layout-shell caps .udd at the AEM box + 2 x 24
   (--uiw-tab-box, gutter 24). Where the page is narrower than that (768-783, 1024-1039) .udd is just the page
   width, the fixed 24 gutter put the title and arrows 8px inside the box at 768. The gutter is now what is left
   either side of the box (0-24, cqw = the .udd width), and the bleed / centring pad follow it, so the three keep
   cancelling as described above. 784+ in each band still gets 24, i.e. no change there.
   QC retest 09/11: the bleed is on BOTH sides but the track only padded the left for --center, so an
   overflowing row started card 1 at the bled edge, `pad` px outside the box the title and arrows sit on
   (0 vs 16 at 768, 88 vs 112 at 960). The leading pad now mirrors the trailing one, and scroll-padding
   takes it back out of card 1's snap position, so scrollLeft rests at 0 and the prev arrow stays disabled
   on the first card (the AB#133647 trap described in the mobile block). Desktop keeps its bleed. */
@media (min-width: 768px) and (max-width: 1279.98px) {
    .page-content--widgets .udd { container-type: inline-size; }
    .page-content--widgets .udd .udd-inner {
        --udd-tab-pad: clamp(0px, calc((100cqw - var(--uiw-tab-box, 100cqw)) / 2), 24px);
        padding-left: var(--udd-tab-pad);
        padding-right: var(--udd-tab-pad);
    }
    .page-content--widgets .udd .udd-viewport { margin-left: calc(-1 * var(--udd-tab-pad)); margin-right: calc(-1 * var(--udd-tab-pad)); }
    .page-content--widgets .udd .udd-track {
        padding-left: var(--udd-tab-pad);
        padding-right: var(--udd-tab-pad);
        scroll-padding-left: var(--udd-tab-pad);
    }
    .page-content--widgets .udd .udd-track--center { padding-left: var(--udd-tab-pad); }
}
