/* ===========================================================================
   The skin of the OneTrust banner.

   OneTrust brings its own sheet from its CDN, after ours, and wins by
   cascade: the !important rules here are mandatory, and this is the only place
   in the landing where they belong. It is few lines on purpose — font, corners,
   the two buttons — because OneTrust already dresses the rest of the banner
   well, and every extra rule is something that breaks when OneTrust changes its DOM.

   The selectors are the public ids of their SDK. The colours come from tokens.css:
   that way the banner ages with the page instead of on its own.
   =========================================================================== */

#onetrust-banner-sdk,
#onetrust-pc-sdk {
    font-family: var(--bbx-font-sans) !important;
    border-radius: var(--lp-radius-card) !important;
    box-shadow: var(--bbx-shadow-lg) !important;
}

#onetrust-banner-sdk button,
#onetrust-pc-sdk button { border-radius: var(--lp-radius-pill) !important; }

/* The fill starts from -press and not from -accent, and it is not a matter of
   taste: the text inside is white at 11.4px, and white on --lp-accent is 3.88:1 —
   below the 4.5 required. On --lp-accent-press it is 5.39. Measured on the real
   banner, not estimated (PageSpeed on 18 September 2026 failed both).
   The page CTAs have the same problem and were NOT changed: the colour of the
   landing buttons is a product decision, this is system chrome. */
#onetrust-accept-btn-handler,
#onetrust-reject-all-handler {
    background-color: var(--lp-accent-press) !important;
    border-color: var(--lp-accent-press) !important;
    color: var(--lp-ink-invert) !important;
}
#onetrust-accept-btn-handler:hover,
#onetrust-reject-all-handler:hover {
    background-color: var(--lp-accent-deep) !important;
    border-color: var(--lp-accent-deep) !important;
}

/* «Cookie policy» inside the banner text. The link comes with OneTrust's
   blue (#0098ea), which on white is 3.14:1: it is their light blue, not
   ours, and it passes nothing. The selector has to match their
   `#onetrust-banner-sdk a[href]` — an attribute weighs as much as a class — and
   it comes before their sheet, which their SDK injects once the page is running:
   hence the important. */
#onetrust-banner-sdk a.ot-cookie-policy-link {
    color: var(--lp-accent-press) !important;
}

/* The banner shows at the bottom, not at the top. The position would be chosen
   in the OneTrust console, which cannot be touched from here: until it is changed
   there, this rule decides it. */
/* The banner shows at the bottom, off the edge, and as wide as the page frame
   instead of narrow in the middle. The translate is still needed — but only on
   X, to keep it centred: the one on Y was what held it mid-screen. */
#onetrust-banner-sdk {
    top: auto !important;
    bottom: 24px !important;
    left: 50% !important;
    right: auto !important;
    transform: translateX(-50%) !important;
    width: calc(100% - 40px) !important;
    max-width: 1100px !important;
}
@media (max-width: 600px) {
    #onetrust-banner-sdk { bottom: 12px !important; width: calc(100% - 20px) !important; }
}

/* The footer button that reopens the preference centre: OneTrust fills it
   with text when present, here it takes the look of the legal links next
   to it. The rule was written on the `.ft__cookie` class alone and never
   won: OneTrust comes later with its own `#ot-sdk-btn`, and in the dark blue
   footer the button showed GREEN among light-blue links — green is their
   default colour. Their id is needed.

   `transition-property` declared: their sheet sets `transition: all`, and
   with `all` the browser has to repaint every frame instead of handing the
   animation to the GPU (PageSpeed flags it with fourteen properties in a row
   on this button). */
#ot-sdk-btn.ft__cookie {
    background: none !important;
    border: 0 !important;
    padding: 0 !important;
    font: inherit !important;
    color: var(--bbx-blue-200) !important;
    cursor: pointer;
    /* Important here too: without it, `transition: all` stays — tested. */
    transition-property: color !important;
    transition-duration: .15s !important;
}
#ot-sdk-btn.ft__cookie:hover { color: var(--lp-ink-invert) !important; }