/* ============================================================================
   theme-switch.css - the appearance switch control, and ONLY that.

   ---------------------------------------------------------------------------
   WHY THIS IS ITS OWN FILE
   ---------------------------------------------------------------------------
   The switch lives on the sign-in screen, and the sign-in screen must NOT be
   re-skinned - the brief is explicit that its layout stays as it is.

   These rules started inside components.css, which was wrong in a way that
   would have shipped a visible fault: components.css restyles .btn, and the
   sign-in button is <input class="btn btn-block loginbtn">. Loading it there
   to get the switch would have restyled that button the moment anyone chose
   Modern - and worse, it would have done so with UNDEFINED custom properties,
   because design-system.css (which defines every --bz-* token) is deliberately
   not loaded on that page. var(--bz-primary) with no value makes the whole
   declaration invalid and it is dropped, so the result is not a themed button
   but a half-styled one: border and padding applied, background and shadow
   silently gone.

   Split out, the sign-in screen loads exactly what it needs and nothing else.

   ---------------------------------------------------------------------------
   NO --bz-* TOKENS ARE USED BELOW, ON PURPOSE
   ---------------------------------------------------------------------------
   Every colour here is a literal. This file has to render correctly on a page
   that has never loaded design-system.css - which is every sign-in screen, and
   is also the Standard theme, where a user first meets the control. A token
   here would be the same bug in a smaller costume.
   ============================================================================ */

.bz-theme-switch {
    display: inline-flex;
    align-items: center;
    padding: 3px;
    border-radius: 999px;
    background: rgba(148, 163, 184, .16);
    border: 1px solid rgba(148, 163, 184, .26);
}

.bz-theme-switch__btn {
    -webkit-appearance: none;
    appearance: none;
    border: 0;
    background: transparent;
    padding: 6px 14px;
    border-radius: 999px;
    font-family: inherit;
    font-size: 12px;
    font-weight: 600;
    line-height: 1.4;
    color: #64748B;
    cursor: pointer;
    transition: background .18s ease, color .18s ease, box-shadow .18s ease;
}

.bz-theme-switch__btn:hover { color: #2563EB; }

/* aria-pressed is the selected state - the same attribute a screen reader
   announces, so the visual and the accessible state cannot drift apart. */
.bz-theme-switch__btn[aria-pressed="true"] {
    background: #FFFFFF;
    color: #14213D;
    box-shadow: 0 1px 3px rgba(15, 27, 54, .18);
}

.bz-theme-switch__btn:focus-visible {
    outline: 2px solid #2563EB;
    outline-offset: 2px;
}

.bz-theme-switch__label {
    display: block;
    font-size: 11px;
    font-weight: 600;
    text-transform: uppercase;
    letter-spacing: .7px;
    color: #94A3B8;
    margin-bottom: 6px;
    text-align: center;
}

/* Dark. Keyed off data-theme as well as data-bz-theme: the sign-in screens
   already run on data-theme (login-modern.css owns it), and bz-theme.js sets
   both, so the control follows the page it is sitting on either way. */
[data-bz-theme="dark"] .bz-theme-switch,
[data-theme="dark"] .bz-theme-switch {
    background: rgba(148, 163, 184, .12);
    border-color: rgba(148, 163, 184, .20);
}

/* [2026-09-11] #94A3B8 -> #A7B4C8. The unselected options are the two thirds of
   this control that are NOT highlighted, so they carry its legibility. #94A3B8
   scores 6.6:1 on the sign-in card (#131C2E) - it passes AA, and it still read
   as dull next to the white-on-blue selected pill, because a three-way switch
   is compared against ITSELF rather than against a threshold. #A7B4C8 is
   8.1:1, the same secondary ink the sign-in card already uses for --lg-ink-2,
   so the whole footer cluster now sits at one weight. */
[data-bz-theme="dark"] .bz-theme-switch__btn,
[data-theme="dark"] .bz-theme-switch__btn { color: #A7B4C8; }

[data-bz-theme="dark"] .bz-theme-switch__btn:hover,
[data-theme="dark"] .bz-theme-switch__btn:hover { color: #93C5FD; }

[data-bz-theme="dark"] .bz-theme-switch__btn[aria-pressed="true"],
[data-theme="dark"] .bz-theme-switch__btn[aria-pressed="true"] {
    background: #1E293B;
    color: #E6EDF8;
    box-shadow: 0 1px 3px rgba(0, 0, 0, .50);
}

/* Placement on the sign-in card: centred, above the footer, quiet enough that
   it does not compete with the Sign in button. It is a preference, not a step
   in signing in. */
.lg-theme-pick {
    margin: 18px 0 6px;
    text-align: center;
}

.lg-theme-pick .bz-theme-switch { margin: 0 auto; }

/* ---------------------------------------------------------------------------
   AMBIENT DARK (Standard on a dark-configured OS)
   [2026-09-11] Added after RCA.

   Standard deliberately leaves data-theme ABSENT so the sign-in screen keeps
   its original behaviour of following the OS (login-modern.css carries six
   @media (prefers-color-scheme: dark) blocks keyed on
   :root:not([data-theme="light"])). That is correct - but it meant the switch
   itself stayed in its light skin on a card the OS had just turned dark, so
   the control was the one light object on a dark panel.

   This mirrors login-modern.css's own selector shape exactly, so the two
   cannot disagree about when "dark" applies:
     * the media query limits it to a dark OS
     * :not([data-theme="light"]) backs off the moment the user explicitly
       picks Standard-with-light or Modern
   [data-theme="dark"] above still covers the explicit Dark choice.
--------------------------------------------------------------------------- */
@media (prefers-color-scheme: dark) {
    :root:not([data-theme="light"]) .bz-theme-switch {
        background: rgba(148, 163, 184, .12);
        border-color: rgba(148, 163, 184, .20);
    }

    :root:not([data-theme="light"]) .bz-theme-switch__btn { color: #A7B4C8; }

    :root:not([data-theme="light"]) .bz-theme-switch__btn:hover { color: #93C5FD; }

    :root:not([data-theme="light"]) .bz-theme-switch__btn[aria-pressed="true"] {
        background: #1E293B;
        color: #E6EDF8;
        box-shadow: 0 1px 3px rgba(0, 0, 0, .50);
    }
}

/* ---------------------------------------------------------------------------
   IN-SESSION PLACEMENT (portal header profile dropdown)
   [2026-09-11] The switch was sign-in only, so changing appearance meant
   signing out. This is the in-app home for it.

   NOT theme-scoped, for the same reason as everything else in this file: the
   dropdown exists under Standard too, and that is where most users will meet
   the control. Literal colours only - design-system.css is loaded in the
   portal, but this file must never depend on it.
--------------------------------------------------------------------------- */
.bz-appearance-item {
    padding: 10px 16px 12px;
    border-top: 1px solid rgba(148, 163, 184, .22);
    margin-top: 4px;
    /* The parent is a Bootstrap 3 dropdown <li>, which expects an <a> child and
       styles on hover. This row is not actionable as a whole - only the buttons
       inside it are - so the hover affordance is suppressed. */
    cursor: default;
}

.bz-appearance-item:hover { background: transparent; }

.bz-appearance-item .bz-theme-switch__label {
    text-align: left;
    margin-bottom: 7px;
}

/* The dropdown is narrower than the sign-in card, so the three buttons share
   the width evenly instead of overflowing it. */
.bz-appearance-item .bz-theme-switch { display: flex; width: 100%; }

.bz-appearance-item .bz-theme-switch__btn {
    flex: 1 1 0;
    padding: 6px 4px;
    text-align: center;
    white-space: nowrap;
}

/* ===========================================================================
   VIBRANCE PASS  [2026-09-11]
   ---------------------------------------------------------------------------
   The control worked but read as a grey segmented strip - three words in a
   pale capsule, easy to miss entirely on the sign-in card, which is where most
   users meet it. Since it is the ONLY entry point to the whole appearance
   feature, being overlooked is a functional defect, not a cosmetic one.

   Still literal colours only, for the reason given at the top of this file:
   this control renders on pages that never load design-system.css, so a
   var(--bz-*) here would resolve to nothing and silently drop the whole
   declaration.
--------------------------------------------------------------------------- */

.bz-theme-switch {
    padding: 4px;
    background: linear-gradient(180deg, rgba(241, 245, 252, .95) 0%, rgba(226, 234, 246, .95) 100%);
    border: 1px solid rgba(148, 163, 184, .34);
    box-shadow: inset 0 1px 2px rgba(15, 27, 54, .06);
}

.bz-theme-switch__btn {
    padding: 7px 15px;
    letter-spacing: .15px;
}

/* A swatch per option, so the choice is legible before it is made: the dot
   shows what each theme looks like rather than relying on the word alone. */
.bz-theme-switch__btn::before {
    content: "";
    display: inline-block;
    width: 9px;
    height: 9px;
    margin-right: 7px;
    border-radius: 50%;
    vertical-align: -1px;
    border: 1px solid rgba(15, 27, 54, .22);
}

.bz-theme-switch__btn[data-bz-set="standard"]::before {
    background: #E2E8F0;
}

.bz-theme-switch__btn[data-bz-set="nextgen"]::before {
    background: linear-gradient(135deg, #2F6BF6 0%, #1D4ED8 100%);
    border-color: rgba(29, 78, 216, .45);
}

.bz-theme-switch__btn[data-bz-set="dark"]::before {
    background: linear-gradient(135deg, #334155 0%, #0B1220 100%);
    border-color: rgba(15, 23, 42, .55);
}

/* Selected. The brand gradient plus a lifted shadow - this is the one element
   on the control that should read as "pressed and active". White ink is fixed
   rather than inherited because the fill is saturated in every theme. */
.bz-theme-switch__btn[aria-pressed="true"] {
    background: linear-gradient(135deg, #2F6BF6 0%, #1D4ED8 100%);
    color: #FFFFFF;
    box-shadow: 0 4px 12px rgba(37, 99, 235, .34), 0 1px 2px rgba(15, 27, 54, .16);
}

.bz-theme-switch__btn[aria-pressed="true"]::before {
    border-color: rgba(255, 255, 255, .85);
    box-shadow: 0 0 0 2px rgba(255, 255, 255, .28);
}

.bz-theme-switch__btn:hover {
    color: #1D4ED8;
}

/* Hover must not repaint the SELECTED button - it already carries the brand
   fill, and a hover colour on top of it turns the label mid-blue on blue. */
.bz-theme-switch__btn[aria-pressed="true"]:hover {
    color: #FFFFFF;
    box-shadow: 0 6px 16px rgba(37, 99, 235, .42), 0 1px 2px rgba(15, 27, 54, .16);
}

.bz-theme-switch__label {
    color: #64748B;
    letter-spacing: .9px;
}

/* ------------------------------------------------------------------ dark -- */
[data-bz-theme="dark"] .bz-theme-switch,
[data-theme="dark"] .bz-theme-switch {
    background: linear-gradient(180deg, rgba(30, 41, 59, .92) 0%, rgba(15, 23, 42, .92) 100%);
    border-color: rgba(148, 163, 184, .26);
    box-shadow: inset 0 1px 2px rgba(0, 0, 0, .34);
}

[data-bz-theme="dark"] .bz-theme-switch__btn[aria-pressed="true"],
[data-theme="dark"] .bz-theme-switch__btn[aria-pressed="true"] {
    background: linear-gradient(135deg, #3B82F6 0%, #2563EB 100%);
    color: #FFFFFF;
    box-shadow: 0 4px 14px rgba(37, 99, 235, .46);
}

[data-bz-theme="dark"] .bz-theme-switch__btn[aria-pressed="true"]:hover,
[data-theme="dark"] .bz-theme-switch__btn[aria-pressed="true"]:hover {
    color: #FFFFFF;
}

[data-bz-theme="dark"] .bz-theme-switch__btn::before,
[data-theme="dark"] .bz-theme-switch__btn::before {
    border-color: rgba(226, 232, 240, .30);
}

[data-bz-theme="dark"] .bz-theme-switch__label,
[data-theme="dark"] .bz-theme-switch__label {
    /* "APPEARANCE" is 11px uppercase with .9px tracking - small, spaced type
       needs more contrast than body text, not less. Matched to the buttons. */
    color: #A7B4C8;
}

/* Give the control room on the sign-in card - it was tucked against the
   footer link and read as part of it. */
.lg-theme-pick {
    margin: 22px 0 8px;
}

/* ===========================================================================
   DROPDOWN VARIANT  [2026-09-11]  - RCA fix, must stay LAST in this file
   ---------------------------------------------------------------------------
   THE BUG: in the profile dropdown the control overflowed its container and
   the "Dark" button was clipped in half.

   WHY. .profDrop is `min-width: 185px`. The pre-existing dropdown rule pins
   the three buttons to `flex: 1 1 0; padding: 6px 4px; white-space: nowrap`,
   so each button can shrink no further than its text. The VIBRANCE PASS above
   then added a ::before swatch worth 9px + 7px margin + 2px border = 18px to
   EVERY button. Three buttons x 18px = 54px of new minimum width against a
   185px box that was already close to full. The overflow was inevitable and
   is invisible on the sign-in card, which is wide - so it only showed in the
   menu.

   THE FIX is not to shrink the swatch or drop it: horizontal is simply the
   wrong layout for a 185px box holding "Standard", "Modern" and "Dark". The
   dropdown gets a VERTICAL list instead - one row per theme, swatch and label
   left-aligned, the active row filled. It fits the width with room to spare,
   the labels can never truncate, and the swatch stays, which is what makes
   the choice legible before it is made.

   The sign-in card keeps the horizontal segmented control - it has the width,
   and a segmented control reads better there.

   Specificity is (0,2,0) throughout so these beat the single-class rules in
   the vibrance pass above without needing !important.
--------------------------------------------------------------------------- */

.bz-appearance-item .bz-theme-switch {
    display: block;
    width: 100%;
    padding: 4px;
    border-radius: 12px;
}

.bz-appearance-item .bz-theme-switch__btn {
    display: block;
    width: 100%;
    flex: none;
    text-align: left;
    padding: 8px 10px;
    margin: 2px 0;
    border-radius: 9px;
    white-space: nowrap;
    font-size: 12.5px;
}

.bz-appearance-item .bz-theme-switch__btn::before {
    width: 10px;
    height: 10px;
    margin-right: 9px;
    vertical-align: -1px;
}

/* The active row. A full-width fill reads as a selected list item rather than
   a pressed pill, which is the right affordance in a menu. */
.bz-appearance-item .bz-theme-switch__btn[aria-pressed="true"] {
    box-shadow: 0 2px 8px rgba(37, 99, 235, .30);
}

/* Hover on a NON-active row only. Without the :not() the active row loses its
   white label to the hover colour and the text vanishes into the fill. */
.bz-appearance-item .bz-theme-switch__btn:not([aria-pressed="true"]):hover {
    background: rgba(37, 99, 235, .08);
}

[data-bz-theme="dark"] .bz-appearance-item .bz-theme-switch__btn:not([aria-pressed="true"]):hover,
[data-theme="dark"] .bz-appearance-item .bz-theme-switch__btn:not([aria-pressed="true"]):hover {
    background: rgba(255, 255, 255, .07);
}

.bz-appearance-item .bz-theme-switch__label {
    text-align: left;
    margin-bottom: 6px;
}

/* ===========================================================================
   PROFILE MENU - UX PASS  [2026-09-11]   must stay LAST
   ---------------------------------------------------------------------------
   WHAT WAS WRONG, AS REPORTED: "easy logout access" and "appearance to be
   smartly selection".

   The vertical list above solved a real clipping bug (see DROPDOWN VARIANT)
   but solved it by spending VERTICAL SPACE: three full-width rows, ~120px,
   sitting directly above Logout. Logout is the thing people open this menu
   for, and it had been pushed to the bottom of a tall panel by a preference
   control they touch once. The information architecture was upside down.

   WHY HORIZONTAL IS NOW POSSIBLE, WHEN IT WAS NOT BEFORE. The clipping had
   one cause: .profDrop is `min-width: 185px` and the three buttons could not
   fit. The earlier fix accepted 185px as fixed. It is not - `min-width` is a
   FLOOR, and a dropdown grows to its content. Giving the appearance row its
   own min-width lets it set the panel's width from the inside, so the control
   gets the room it needs without .profDrop being touched at all - which
   matters, because .profDrop is shared with menus that must not change.

   A segmented control is also the right affordance: three mutually exclusive
   options, all visible, one tap - the pattern macOS, Windows and iOS all use
   for exactly this setting. The swatch stays, because it shows what each
   choice LOOKS like before it is made.

   Net effect: ~80px of vertical space returns to the menu and Logout rises
   with it.
   =========================================================================== */
.bz-appearance-item {
    /* Sets the panel width from the inside. Sized to the CONTENT, not guessed:
       at 11.5px/600 the three labels run ~50 + ~44 + ~25px, each button adds an
       8px swatch, a 5px gap and 12px of padding (+25), the row adds 4px of
       inter-button margin and 6px of its own padding, and the item adds 24px -
       about 228px. 248 leaves headroom for a font that measures wider, because
       the buttons are `nowrap` and would clip rather than reflow. */
    min-width: 248px;
    /* 12px matches `.prof .profDrop > li > a.dropdown-item`, so the control's
       left edge lines up with the labels of the items above it. */
    padding: 6px 12px 10px;
}

.bz-appearance-item .bz-theme-switch {
    display: flex;
    width: 100%;
    padding: 3px;
    border-radius: 10px;
}

/* flex-basis auto, not 0: equal thirds would size every segment to "Standard",
   the longest label, and leave "Dark" swimming in empty space. Sizing to
   content and sharing the remainder keeps the row tight and even-looking. */
.bz-appearance-item .bz-theme-switch__btn {
    display: flex;
    align-items: center;
    justify-content: center;
    flex: 1 1 auto;
    width: auto;
    text-align: center;
    padding: 7px 6px;
    margin: 0;
    border-radius: 8px;
    font-size: 11.5px;
    letter-spacing: .01em;
    white-space: nowrap;
}

.bz-appearance-item .bz-theme-switch__btn + .bz-theme-switch__btn {
    margin-left: 2px;
}

/* The swatch shrinks and loses its right margin - the flex gap below does that
   job now, and at 8px it still reads as a colour sample rather than a bullet. */
.bz-appearance-item .bz-theme-switch__btn::before {
    width: 8px;
    height: 8px;
    margin-right: 5px;
    vertical-align: 0;
    flex: none;
}

.bz-appearance-item .bz-theme-switch__label {
    text-align: left;
    margin-bottom: 5px;
    font-size: 10px;
    letter-spacing: .8px;
    opacity: .85;
}

/* ---------------------------------------------------------------------------
   SIGN OUT - the one destructive action in the menu
   ---------------------------------------------------------------------------
   Matched by href rather than by position or a new class: `li:last-child`
   breaks the moment somebody appends an item, and adding a class would mean
   editing four layouts for a purely presentational change. Every one of the
   four spells the link the same way.

   Danger colour is deliberately on the INK and the hover fill, not a solid
   red button. A filled red button in a menu reads as the primary action and
   invites the accidental click this is trying to avoid; a tinted row reads as
   "different, and final", which is what it is.
--------------------------------------------------------------------------- */
.prof .profDrop > li > a[href*="Logout" i],
.prof .profDrop > li > a[href*="SignOff" i],
.prof .profDrop > li > a[href*="LogOff" i] {
    color: #B91C1C;
    font-weight: 600;
}

.prof .profDrop > li > a[href*="Logout" i]:hover,
.prof .profDrop > li > a[href*="SignOff" i]:hover,
.prof .profDrop > li > a[href*="LogOff" i]:hover {
    background: rgba(220, 38, 38, .10);
    color: #991B1B;
}

/* A hairline above it, so the destructive action is visibly separated from
   the preferences rather than being the next row down. */
.prof .profDrop > li > a[href*="Logout" i],
.prof .profDrop > li > a[href*="SignOff" i],
.prof .profDrop > li > a[href*="LogOff" i] {
    border-top: 1px solid rgba(15, 23, 42, .08);
    margin-top: 4px;
    padding-top: 11px;
}

[data-bz-theme="dark"] .prof .profDrop > li > a[href*="Logout" i],
[data-bz-theme="dark"] .prof .profDrop > li > a[href*="SignOff" i],
[data-bz-theme="dark"] .prof .profDrop > li > a[href*="LogOff" i] {
    color: #FCA5A5;
    border-top-color: rgba(148, 163, 184, .18);
}

[data-bz-theme="dark"] .prof .profDrop > li > a[href*="Logout" i]:hover,
[data-bz-theme="dark"] .prof .profDrop > li > a[href*="SignOff" i]:hover,
[data-bz-theme="dark"] .prof .profDrop > li > a[href*="LogOff" i]:hover {
    background: rgba(248, 113, 113, .14);
    color: #FECACA;
}

/* ===========================================================================
   THE MENU MUST OPEN LEFTWARD   [2026-09-11]   must stay LAST
   ---------------------------------------------------------------------------
   THE BUG I CAUSED: widening the panel pushed "Dark" clean off the right of
   the viewport, so the third option could not be clicked at all.

   THE CAUSE was never the width. The profile menu is the LAST thing in the
   header, hard against the right edge, and Bootstrap 3 anchors every
   .dropdown-menu with `left: 0` - it grows RIGHTWARD from its trigger. At the
   old 185px it already ended within a few pixels of the viewport edge; any
   extra width had nowhere to go but off-screen. Widening simply exposed a
   latent bug: a menu at the right edge of the page must be anchored by its
   RIGHT edge.

   This is what Bootstrap's own .dropdown-menu-right does, applied here in CSS
   rather than by adding a class to four layouts.

   It changes Standard too, and that is deliberate: the menu opens from the
   opposite edge, the content is identical, and it can no longer leave the
   viewport at any width or zoom level. Leaving Standard anchored to an edge it
   overflows would be preserving a bug, not preserving behaviour.

   The max-width is a second belt: at heavy browser zoom or on a narrow laptop
   the header itself can be narrower than the panel, and a menu is useless the
   moment any part of it is unreachable.
   =========================================================================== */
.prof .dropdown-menu.profDrop {
    left: auto;
    right: 0;
    max-width: calc(100vw - 24px);
}

/* Graceful shrink rather than overflow. `min-width: 0` lets a flex item go
   below its content width - without it a flex child refuses to shrink past
   `max-content` and pushes the row wider than its container instead, which is
   exactly how the clipping happened. Paired with ellipsis so a squeezed label
   degrades to "Standa..." instead of disappearing behind an edge. */
.bz-appearance-item .bz-theme-switch {
    min-width: 0;
    overflow: hidden;
}

.bz-appearance-item .bz-theme-switch__btn {
    min-width: 0;
    overflow: hidden;
    text-overflow: ellipsis;
}

/* A comfortable target. 32px is the smallest a pointer target should be in a
   menu; the previous 7px padding gave about 28px. */
.bz-appearance-item .bz-theme-switch__btn {
    min-height: 32px;
}

/* The selected option has to be unmistakable at a glance - this is a menu the
   user opens, scans once and leaves. A fill plus white ink reads as "this one"
   far faster than a tint does. */
.bz-appearance-item .bz-theme-switch__btn[aria-pressed="true"] {
    background: linear-gradient(135deg, #3B82F6 0%, #2563EB 100%);
    color: #FFFFFF;
    box-shadow: 0 2px 8px rgba(37, 99, 235, .34);
}

.bz-appearance-item .bz-theme-switch__btn[aria-pressed="true"]::before {
    border-color: rgba(255, 255, 255, .85);
}

/* ===========================================================================
   ICON SWITCH + MENU ALIGNMENT   [2026-09-11]   must stay LAST
   ---------------------------------------------------------------------------
   TWO REPORTED FAULTS, ONE ROOT.

   "totally misaligned": the appearance row was a stacked block - a label on
   one line, a full-width control on the next - sitting between two ordinary
   menu items that are single rows of `icon + text`. It did not share their
   rhythm, their height or their left edge, so it read as a panel wedged into
   a list rather than part of it.

   "can the design be with smart icon so any layman can understand": the three
   text labels are what forced the row to be full-width in the first place.

   Both are answered by the same change. The row becomes what every other row
   in the menu already is - one line, label left, control right - and the
   control becomes three icons: a SUN, a SPARKLE and a MOON. A sun and a moon
   are understood without reading, in any language. The word "Nextgen" means
   nothing to a first-time user; a sparkle at least says "the new one".

   The text is hidden VISUALLY here and nowhere else: the sign-in card has room
   and keeps icon + label. Every button still carries title and aria-label, so
   a screen reader announces "Standard", "Nextgen", "Dark" exactly as before -
   this is a visual compaction, not a removal of information.
   =========================================================================== */
.bz-appearance-item {
    display: flex;
    align-items: center;
    justify-content: space-between;
    min-width: 0;                 /* the icons no longer force a wide panel */
    padding: 8px 12px;
}

.bz-appearance-item .bz-theme-switch__label {
    margin: 0 10px 0 0;
    flex: 0 1 auto;
    white-space: nowrap;
    text-transform: none;         /* sentence case sits better beside the items */
    font-size: 12.5px;
    letter-spacing: 0;
    font-weight: 500;
    color: inherit;
    opacity: .85;
}

.bz-appearance-item .bz-theme-switch {
    display: inline-flex;
    width: auto;
    flex: 0 0 auto;
    padding: 3px;
    border-radius: 999px;
}

/* Square icon buttons. 30px keeps the row the same height as a menu item, so
   the three rows finally line up. */
.bz-appearance-item .bz-theme-switch__btn {
    flex: 0 0 auto;
    width: 30px;
    height: 30px;
    min-height: 0;
    padding: 0;
    margin: 0;
    border-radius: 999px;
    display: inline-flex;
    align-items: center;
    justify-content: center;
}

.bz-appearance-item .bz-theme-switch__btn + .bz-theme-switch__btn {
    margin-left: 3px;
}

/* The label is hidden the accessible way - clipped, not `display:none`, which
   would take it out of the accessibility tree along with the button's name. */
.bz-appearance-item .bz-theme-switch__txt {
    position: absolute;
    width: 1px;
    height: 1px;
    padding: 0;
    margin: -1px;
    overflow: hidden;
    clip: rect(0 0 0 0);
    white-space: nowrap;
    border: 0;
}

/* The colour swatch was standing in for the icon that did not exist yet. With
   a sun, a sparkle and a moon it is one decoration too many in a 30px circle. */
.bz-appearance-item .bz-theme-switch__btn::before {
    display: none;
}

.bz-appearance-item .bz-theme-switch__btn svg {
    display: block;
    flex: none;
}

/* The sign-in card keeps icon AND text - it has the width, and on a page a
   user meets before logging in the names are worth spelling out. */
.lg-theme-pick .bz-theme-switch__btn {
    display: inline-flex;
    align-items: center;
    gap: 6px;
}

.lg-theme-pick .bz-theme-switch__btn svg { flex: none; }


/* ---------------------------------------------------------------------------
   THE SWATCH RETIRES   [2026-09-12]
   ---------------------------------------------------------------------------
   The ::before colour dot predates the icons. With a sun, a sparkle and a moon
   on every button it is a second indicator for the same fact, and on the
   sign-in card - where the label is also shown - each option rendered as
   "dot + icon + word". Three signals for one choice read as clutter and threw
   the row out of alignment, which is what was reported.

   The dropdown already hid it; this retires it everywhere, so the control is
   the same component in both places instead of two variants.
--------------------------------------------------------------------------- */
.bz-theme-switch__btn::before {
    display: none !important;
}
