/* ---------------------------------------------------------------------------
   The dashboard and catalog shells.

   This was five tabs on one horizontal strip - Products, Brands & Categories,
   Quote Requests, Messages, Statistics - five siblings of equal rank, saying
   they were five of the same kind of thing. Two of them are not: managing the
   catalog is work you go looking for, while a request and a message are work
   that arrives, and the question those two answer is "has anything come in",
   which a strip of equal labels cannot answer without being clicked.

   A rail can carry the group names and the unread counts that make the
   difference visible, and it grows downward, which a strip that already held
   five labels on one line does not.

   Both pages share the same fixed rail and flexible content geometry. The page
   heading stays outside that split and therefore spans the full container.

   minmax(0, 1fr) on the content column, not 1fr: a grid item's automatic
   minimum size is its content, so a wide table or product row would otherwise
   push the column wider than the grid and take the page scrollbar with it.
   --------------------------------------------------------------------------- */
.dash-shell,
.catalog-shell {
    display: grid;
    gap: var(--s-5);
}

@media only screen and (min-width: 992px) {
    .dash-shell,
    .catalog-shell {
        grid-template-columns: 14rem minmax(0, 1fr);
        gap: var(--s-6);
    }

    .dash-rail {
        position: sticky;
        /* Clears the sticky masthead - 56px - with air under it. */
        top: 4.5rem;
        align-self: start;
    }
}

/* The catalog used Bootstrap's 3/9 columns with another .container nested in
   the content column. That second container added its own gutter, so the result
   controls and cards started one step in from the page heading. Its shell now
   follows the dashboard's fixed rail + minmax content geometry. */
.dash-shell__main,
.catalog-shell__rail,
.catalog-shell__main {
    min-width: 0;
}

/* Persistent explanations need to survive a quick scan of an operating
   screen. They use the shape of an alert without borrowing success/error
   colours or live-region semantics, both of which are reserved for outcomes. */
.admin-alert {
    display: grid;
    grid-template-columns: auto minmax(0, 1fr);
    gap: var(--s-3);
    align-items: start;
    margin-bottom: var(--s-5);
    padding: var(--s-3) var(--s-4);
    border: 1px solid var(--rule-strong);
    border-inline-start: 4px solid var(--bar);
    background-color: var(--surface);
    color: var(--ink);
}

.admin-alert__icon {
    margin-top: .125rem;
    color: var(--accent);
}

.admin-alert__copy,
.admin-alert__body {
    min-width: 0;
}

.admin-alert__title {
    margin-bottom: var(--s-1);
    font-family: var(--f-condensed);
    font-weight: 700;
    letter-spacing: .04em;
    text-transform: uppercase;
}

.admin-alert__body {
    max-width: 78ch;
}

.admin-alert__body > :last-child {
    margin-bottom: 0;
}

.admin-alert__body > * + * {
    margin-top: var(--s-2);
}

.admin-alert__detail {
    color: var(--ink-muted);
    font-size: .875rem;
}

@media only screen and (max-width: 575.98px) {
    .admin-alert {
        grid-template-columns: minmax(0, 1fr);
    }

    /* The dark edge still identifies the banner. Spending another column on
       the icon makes the longer operating notes needlessly tall on a phone. */
    .admin-alert__icon {
        display: none;
    }
}

/* Below lg the rail is a band above the content: the groups sit side by side
   rather than stacking five deep and pushing the table off the first screen. */
.dash-rail__groups {
    display: flex;
    flex-wrap: wrap;
    gap: var(--s-4) var(--s-6);
}

@media only screen and (min-width: 992px) {
    .dash-rail__groups {
        display: block;
    }

    .dash-rail__group + .dash-rail__group {
        margin-top: var(--s-5);
    }
}

.dash-rail__mobile-toggle {
    display: grid;
    grid-template-columns: minmax(0, 1fr) auto auto;
    align-items: center;
    width: 100%;
    min-height: 52px;
    padding: var(--s-2) var(--s-3);
    border: 1px solid var(--rule-strong);
    background: var(--surface);
    color: var(--ink);
    text-align: left;
}

.dash-rail__mobile-current {
    font-family: var(--f-condensed);
    font-weight: 700;
    text-transform: uppercase;
}

.dash-rail__mobile-unread {
    grid-column: 1;
    color: var(--accent);
    font-size: .75rem;
}

.dash-rail__mobile-action {
    grid-column: 2;
    grid-row: 1 / span 2;
    margin-inline-end: var(--s-2);
    color: var(--ink-muted);
    font-family: var(--f-condensed);
    font-size: .75rem;
    font-weight: 700;
    text-transform: uppercase;
}

.dash-rail__mobile-toggle svg {
    grid-column: 3;
    grid-row: 1 / span 2;
    transition: transform 160ms ease-out;
}

.dash-rail__mobile-toggle[aria-expanded="true"] svg {
    transform: rotate(180deg);
}

@media only screen and (min-width: 992px) {
    .dash-rail__groups.collapse {
        display: block !important;
    }
}

.dash-rail__group {
    flex: 1 1 10rem;
}

/* On a phone the three groups would sit in two columns of about 160px, which
   wraps "Brands & categories" onto two lines and puts its count under it. One
   group per row instead; there are five links in total, so nothing is pushed far. */
@media only screen and (max-width: 575.98px) {
    .dash-rail__group {
        flex-basis: 100%;
    }
}

/* The mono register, at .filter-group__head's values.

   05-storefront.css says of that rule that the admin rail and the catalog rail
   "are the same object doing the same job, and there was no reason for the two
   to name their groups in two different voices" - and then the two were in two
   voices anyway: the catalog's group heads are mono 600 at .12em, these were
   Archivo 700 at .1em. Stating the intent is not the same as delivering it, and
   nothing since had put them together to notice.

   It shows up worst on the page head this rail sits beside, where the screen's
   group is printed as a .marker: ADMINISTRATION in mono over the panel and
   ADMINISTRATION in Archivo in the rail, forty pixels apart and the same word.

   Muted stays. .filter-group__head is at full ink because it names a group of
   checkboxes that are themselves muted; these name a list of links that are
   already at ink, so the label is the thing that has to stay subordinate. */
.dash-rail__heading {
    margin-bottom: var(--s-2);
    padding-bottom: var(--s-2);
    border-bottom: 1px solid var(--rule);
    color: var(--ink-muted);
    font-family: var(--f-mono);
    font-size: .6875rem;
    font-weight: 600;
    letter-spacing: .12em;
    text-transform: uppercase;
}

.dash-rail__list {
    margin: 0;
    padding: 0;
    list-style: none;
}

.dash-rail__link {
    display: flex;
    align-items: center;
    gap: var(--s-3);
    min-height: 44px;
    padding: var(--s-2) var(--s-3);
    color: var(--ink-muted);
    font-family: var(--f-condensed);
    font-weight: 700;
    letter-spacing: .02em;
    text-decoration: none;
    transition: color 200ms linear, background-color 200ms linear;
}

/* --surface, not --page. body is #F6F6F6, which is exactly what --page holds, so
   both of these were painting the ground in the colour of the ground: the hover
   did nothing at all and the current item was carried by its underline alone.
   On this ground a state lifts to white - the same move .plane makes. */
.dash-rail__link:hover {
    background-color: var(--surface);
    color: var(--ink);
}

/* The current item is marked the way the masthead marks the current page - an
   accent underline - scaled down to the label rather than the whole row, so the
   colour lands on the words and the row keeps its shape. */
.dash-rail__link.is-current {
    background-color: var(--surface);
    color: var(--ink);
}

.dash-rail__link.is-current .dash-rail__name {
    box-shadow: inset 0 -3px 0 var(--accent);
}

/* Log out is a POST, so it is a <button> where every other row is an <a>. It
   has to sit in the list as though it were one: a bare button brings its own
   background, border, centred text and browser font, none of which the rail
   uses. Everything visual stays on .dash-rail__link; this only undoes what the
   user agent adds. */
.dash-rail__link--button {
    width: 100%;
    border: 0;
    background: none;
    font-size: inherit;
    text-align: left;
    cursor: pointer;
}

.dash-rail__name {
    margin-right: auto;
    padding-bottom: 2px;
}

.dash-rail__number {
    display: inline-flex;
    align-items: center;
    justify-content: center;
    flex: 0 0 2rem;
    min-width: 2rem;
}

.dash-rail__count {
    min-width: 1.25rem;
    line-height: 1.25rem;
    text-align: center;
    font-size: .75rem;
    font-weight: 400;
    font-variant-numeric: tabular-nums;
    color: var(--ink-muted);
}

/* The one count that is worth the accent: things nobody has dealt with. A total
   in the muted ink takes its place in the same fixed-width slot, so the number
   does not jump sideways when an item is marked read. */

/* ---------------------------------------------------------------------------
   Row actions.

   Every one of these was an <svg onclick> or a <div type="button"> - not
   focusable, not keyboard-operable, and announced as nothing. As real buttons
   they need the chrome stripping back off and a target big enough to hit: 44px
   is the same floor the carousel controls use.
   --------------------------------------------------------------------------- */
.icon-button {
    display: inline-flex;
    align-items: center;
    justify-content: center;
    min-width: 44px;
    min-height: 44px;
    padding: 0;
    border: 0;
    background: none;
    color: var(--ink-muted);
    transition: color 200ms linear;
}

.icon-button:hover {
    color: var(--accent);
}

/* Delete is the one action in a row that cannot be undone, and it used to be the
   third item in a dropdown, drawn exactly like the two safe ones. It sits in the
   open now, so the difference has to be carried by the control: the accent on
   hover is the same as its neighbours, and the tinted ground is what says this
   one is not View. */
.icon-button--danger,
.icon-button--danger:hover,
.icon-button--danger:focus-visible {
    color: var(--feedback-error);
    background-color: var(--page);
}

/* Three actions on one row, kept off the row's own click target. 44px each, so
   the group needs the width the Actions column now reserves. */
.row-actions {
    display: flex;
    align-items: center;
    justify-content: flex-end;
    gap: var(--s-1);
}

.row-action__label {
    display: none;
}

.batch-toolbar {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    gap: var(--s-2);
    margin-bottom: var(--s-3);
    padding: var(--s-3);
    background-color: var(--surface);
    border: 1px solid var(--rule);
}

.batch-toolbar__summary {
    margin-inline-end: auto;
}

.batch-toolbar__scope {
    display: flex;
    flex: 1 0 100%;
    flex-wrap: wrap;
    align-items: center;
    gap: var(--s-2) var(--s-3);
    padding: var(--s-2) var(--s-3);
    background-color: var(--page);
    border-block: 1px solid var(--rule);
}

.batch-toolbar .btn {
    min-height: 40px;
}

.admin-product-table__select {
    width: 3rem;
    text-align: center;
}

.admin-product-select-target {
    display: inline-grid;
    place-items: center;
    width: 44px;
    height: 44px;
    margin: -10px;
    cursor: pointer;
}

.admin-product-select-target .form-check-input {
    margin: 0;
}

@media (max-width: 767.98px) {
    .batch-toolbar {
        align-items: stretch;
    }

    .batch-toolbar__summary {
        flex-basis: 100%;
        margin-inline-end: 0;
    }

    .batch-toolbar .btn {
        flex: 1 1 auto;
    }
}

/* Disabled catalog records stay legible and editable in Admin, but they must not
   look live. The neutral page fill and desaturated image carry the state without
   lowering text contrast; the explicit label means colour is never the only cue. */
.dash-row.is-disabled > td,
.taxonomy-row.is-disabled > td {
    background-color: var(--page);
}

.dash-row.is-disabled .table-image,
.dash-row.is-disabled .admin-product-thumbnail {
    filter: grayscale(1);
    opacity: .58;
}

.catalog-status {
    display: inline-block;
    margin-inline-start: var(--s-2);
    padding: .125rem .375rem;
    border: 1px solid var(--rule-strong);
    color: var(--ink-muted);
    font-family: var(--f-condensed);
    font-size: .6875rem;
    font-weight: 700;
    letter-spacing: .06em;
    line-height: 1.35;
    text-transform: uppercase;
    vertical-align: middle;
}

/* Catalog transfer is one guarded workflow: import owns the working surface,
   export sits in the page header as a secondary action, and the preview
   becomes the page's evidence before anything can be written. */
.catalog-transfer-import {
    border: 1px solid var(--rule);
}

.catalog-import-preview__footer {
    display: flex;
    align-items: flex-end;
    justify-content: space-between;
    gap: var(--s-4);
}

.catalog-transfer-import__head,
.catalog-import-preview__footer > div {
    min-width: 0;
    max-width: 72ch;
}

.catalog-transfer-upload__row {
    display: flex;
    align-items: stretch;
    gap: var(--s-3);
}

.catalog-transfer-dropzone {
    position: relative;
    display: flex;
    flex: 1 1 auto;
    min-width: 0;
    align-items: center;
    padding: var(--s-4) var(--s-5);
    border: 1px dashed var(--rule-strong);
    border-radius: 2px;
    background-color: var(--page);
    transition: border-color .15s ease, background-color .15s ease;
}

.catalog-transfer-dropzone:hover,
.catalog-transfer-dropzone:focus-within,
.catalog-transfer-dropzone.is-dragover {
    border-color: var(--ink);
    background-color: var(--surface);
}

.catalog-transfer-dropzone.has-file {
    border-style: solid;
    border-color: var(--ink);
    background-color: var(--surface);
}

.catalog-transfer-dropzone.is-invalid {
    border-color: var(--accent);
}

.catalog-transfer-dropzone__label {
    display: flex;
    flex-direction: column;
    gap: .25rem;
    min-width: 0;
    margin: 0;
    cursor: pointer;
}

.catalog-transfer-dropzone__title {
    color: var(--ink);
    font-weight: 600;
    overflow-wrap: anywhere;
}

.catalog-transfer-dropzone__hint {
    color: var(--ink-muted);
    font-size: .75rem;
}

/* Visually covers the dropzone so native click, keyboard focus, and
   drag-and-drop all hit the real <input type="file"> directly. */
.catalog-transfer-dropzone__input {
    position: absolute;
    inset: 0;
    width: 100%;
    height: 100%;
    opacity: 0;
    cursor: pointer;
}

.catalog-transfer-upload__submit {
    flex: 0 0 auto;
    padding-inline: var(--s-5);
}

.catalog-transfer-import__rule {
    padding: var(--s-2) var(--s-3);
    border-inline-start: 2px solid var(--rule-strong);
    color: var(--ink-muted);
    font-size: .875rem;
}

.catalog-transfer-notice,
.catalog-import-errors {
    padding: var(--s-3) var(--s-4);
    border: 1px solid var(--rule);
    border-inline-start: 3px solid var(--ink);
    background: var(--surface);
}

.catalog-import-errors {
    border-inline-start-color: var(--accent);
    color: var(--ink);
}

/* The headings the reader accepts. A disclosure, so it costs one line until a
   refused file sends the owner looking for it; the headings themselves are set
   in the data face because they are what he has to type. */
.catalog-transfer-headings {
    max-width: 70ch;
    border-top: 1px solid var(--rule);
}

.catalog-transfer-headings > summary {
    padding: var(--s-2) 0;
    color: var(--ink);
    font-weight: 600;
    cursor: pointer;
}

.catalog-transfer-headings__body {
    padding-bottom: var(--s-2);
}

.catalog-transfer-headings__group {
    margin: var(--s-3) 0 var(--s-1);
    color: var(--ink-muted);
    font-family: var(--f-condensed);
    font-size: .6875rem;
    font-weight: 700;
    letter-spacing: .08em;
    text-transform: uppercase;
}

.catalog-transfer-headings__list {
    margin: 0;
}

.catalog-transfer-headings__list > div {
    display: grid;
    grid-template-columns: minmax(10rem, 16rem) minmax(0, 1fr);
    gap: var(--s-3);
    padding: var(--s-1) 0;
    border-bottom: 1px solid var(--rule);
}

.catalog-transfer-headings__list dt {
    font-weight: 600;
}

.catalog-transfer-headings__list dd {
    margin: 0;
    font-size: .8125rem;
    overflow-wrap: anywhere;
}

/* The summary is also the filter: each tile is a link to its own rows. A
   count of nothing stays a plain tile - a link to an empty table is a click
   that tells the owner what the zero already did. */
.catalog-import-summary {
    display: grid;
    grid-template-columns: repeat(6, minmax(0, 1fr));
    border: 1px solid var(--rule);
}

.catalog-import-summary__item {
    display: block;
    min-width: 0;
    padding: var(--s-3);
    border-right: 1px solid var(--rule);
    color: var(--ink);
    text-decoration: none;
}

.catalog-import-summary__item:last-child {
    border-right: 0;
}

/* Scoped through the nav to answer the dashboard's sentence-link rule in
   06-admin.css (0,1,1), which would underline every count and turn it red on
   hover: a tile is marked by its frame, not by an underline. */
.catalog-import-summary a.catalog-import-summary__item {
    color: var(--ink);
    text-decoration: none;
}

.catalog-import-summary a.catalog-import-summary__item:hover,
.catalog-import-summary a.catalog-import-summary__item:focus-visible {
    background-color: var(--page);
    color: var(--ink);
}

/* The selected filter is ruled underneath in ink, like a current tab. Inset,
   so marking it moves nothing. */
.catalog-import-summary__item[aria-current] {
    background-color: var(--page);
    box-shadow: inset 0 -2px 0 var(--ink);
}

.catalog-import-summary__label {
    display: block;
    color: var(--ink-muted);
    font-family: var(--f-condensed);
    font-size: .6875rem;
    font-weight: 700;
    letter-spacing: .08em;
    text-transform: uppercase;
}

.catalog-import-summary__count {
    display: block;
    margin-top: var(--s-1);
    font-size: 1.25rem;
    font-weight: 700;
}

.catalog-import-summary__item.is-empty .catalog-import-summary__count {
    color: var(--ink-muted);
}

.catalog-import-summary__item--error:not(.is-empty) .catalog-import-summary__count,
.catalog-import-row--error .catalog-import-action {
    color: var(--accent);
}

.catalog-import-filter,
.catalog-import-pager {
    display: flex;
    flex-wrap: wrap;
    align-items: baseline;
    justify-content: space-between;
    gap: var(--s-2) var(--s-4);
}

.catalog-import-filter__label {
    margin-inline-end: var(--s-2);
    font-weight: 700;
}

.catalog-import-filter__links {
    display: flex;
    flex-wrap: wrap;
    gap: var(--s-2) var(--s-4);
}

.catalog-import-empty {
    padding: var(--s-4);
    border: 1px solid var(--rule);
}

.catalog-import-table-plane .table-scroll {
    max-height: 38rem;
}

.catalog-import-table th:first-child,
.catalog-import-table td:first-child {
    width: 5rem;
}

.catalog-import-table th:nth-child(2),
.catalog-import-table td:nth-child(2) {
    width: 14rem;
}

.catalog-import-table th:nth-child(4),
.catalog-import-table td:nth-child(4) {
    width: 10rem;
}

.catalog-import-action {
    display: inline-block;
    padding: .125rem .375rem;
    border: 1px solid var(--rule-strong);
    color: var(--ink-muted);
    font-family: var(--f-condensed);
    font-size: .6875rem;
    font-weight: 700;
    letter-spacing: .06em;
    line-height: 1.35;
    text-transform: uppercase;
    /* "Sem alteração" broken over two lines reads as two labels. */
    white-space: nowrap;
}

.catalog-import-action--create,
.catalog-import-action--restore {
    border-color: var(--ink);
    color: var(--ink);
}

.catalog-import-row--error .catalog-import-action {
    border-color: var(--accent);
    background-color: var(--accent);
    color: var(--surface);
}

.catalog-import-row--error > td:first-child {
    box-shadow: inset 3px 0 0 var(--accent);
}

.catalog-import-row__issues {
    padding-left: 1.1rem;
    color: var(--ink);
}

.catalog-import-row__issues li + li {
    margin-top: var(--s-1);
}

.catalog-import-stage-note {
    color: var(--ink);
}

.catalog-import-confirm__list {
    margin: 0 0 var(--s-3);
    padding-left: 1.1rem;
}

.catalog-import-confirm__list li + li {
    margin-top: var(--s-1);
}

.catalog-import-pager > :nth-child(3) {
    text-align: right;
}

@media (max-width: 991.98px) {
    .catalog-transfer-upload__row,
    .catalog-import-preview__footer {
        align-items: stretch;
        flex-direction: column;
    }

    .catalog-transfer-upload__submit,
    .catalog-import-preview__footer form,
    .catalog-import-preview__footer .btn {
        width: 100%;
    }

    .catalog-transfer-import__rule {
        max-width: none;
    }

    .catalog-import-summary {
        grid-template-columns: repeat(3, minmax(0, 1fr));
    }

    .catalog-import-summary__item:nth-child(3) {
        border-right: 0;
    }

    .catalog-import-summary__item:nth-child(-n + 3) {
        border-bottom: 1px solid var(--rule);
    }
}

/* Phone: each row becomes a card - row number, reference and result on the
   first line, the name under them, then what to do. The column labels the
   card pattern prints above every value (06-admin.css) are dropped here for
   the three that read for themselves; a reference in the data face is
   recognisably a reference, and a result is a labelled chip already. The
   thead stays for assistive technology either way. Selectors carry both
   table classes because the generic card rules load later. */
@media only screen and (max-width: 767.98px) {
    .catalog-import-table-plane .table-scroll {
        max-height: none;
    }

    .catalog-import-table.admin-card-table > tbody > tr {
        display: grid;
        grid-template-columns: auto minmax(0, 1fr) auto;
        grid-template-areas:
            "number reference result"
            "name name name"
            "details details details";
        column-gap: var(--s-3);
        padding: var(--s-3);
    }

    .catalog-import-table.admin-card-table > tbody > tr > td {
        display: block;
        width: auto;
        padding: 0;
        background-color: transparent;
    }

    .catalog-import-table.admin-card-table > tbody > tr.catalog-import-row--error {
        border-color: var(--accent);
        background-color: color-mix(in srgb, var(--accent) 5%, var(--surface));
    }

    .catalog-import-table.admin-card-table .catalog-import-row__number {
        grid-area: number;
        color: var(--ink-muted);
    }

    .catalog-import-table.admin-card-table .catalog-import-row__reference {
        grid-area: reference;
        font-weight: 700;
    }

    .catalog-import-table.admin-card-table .catalog-import-row__result {
        grid-area: result;
    }

    .catalog-import-table.admin-card-table .catalog-import-row__name {
        grid-area: name;
        margin-top: var(--s-1);
    }

    .catalog-import-table.admin-card-table .catalog-import-row__details {
        grid-area: details;
        margin-top: var(--s-2);
    }

    .catalog-import-table.admin-card-table .catalog-import-row__reference::before,
    .catalog-import-table.admin-card-table .catalog-import-row__name::before,
    .catalog-import-table.admin-card-table .catalog-import-row__result::before,
    .catalog-import-table.admin-card-table .catalog-import-row__details::before {
        content: none;
    }

    .catalog-import-table.admin-card-table .catalog-import-row__number::before {
        display: inline;
        margin: 0 var(--s-1) 0 0;
    }

    .catalog-transfer-headings__list > div {
        grid-template-columns: minmax(0, 1fr);
        gap: 0;
    }

    .catalog-import-filter__links {
        flex-direction: column;
    }
}

@media (max-width: 575.98px) {
    .catalog-import-summary {
        grid-template-columns: repeat(2, minmax(0, 1fr));
    }

    .catalog-import-summary__item:nth-child(3) {
        border-right: 1px solid var(--rule);
    }

    .catalog-import-summary__item:nth-child(even) {
        border-right: 0;
    }

    .catalog-import-summary__item:nth-child(-n + 4) {
        border-bottom: 1px solid var(--rule);
    }
}

/* The whole row opens the editor. Editing a product was two clicks behind a menu
   that had to be opened before it would say what was in it - on the table whose
   entire job is finding a product and changing it. */
.dash-row {
    cursor: pointer;
}

/* The product title is the route-backed editor link, not a storefront link. It
   is deliberately drawn like the row label rather than like navigation. */
.row-title {
    display: inline;
    padding: 0;
    border: 0;
    background: none;
    color: var(--ink);
    font: inherit;
    text-align: left;
    text-decoration: none;
}

.row-title:hover {
    color: var(--accent);
    text-decoration: underline;
    text-underline-offset: .2em;
}

/* ---------------------------------------------------------------------------
   Product editor.

   One form, two presentations: a full-height sheet beside the desktop table,
   and a route-backed page when the viewport is too narrow or the URL is opened
   directly. The fields keep the same order and semantics in both.
   --------------------------------------------------------------------------- */
.product-editor-sheet {
    width: min(48rem, 100vw);
    border-left: 1px solid var(--rule);
    background-color: var(--surface);
}

.product-editor-form {
    display: flex;
    flex-direction: column;
    min-height: 100%;
}

.product-editor__header {
    flex: 0 0 auto;
    padding: var(--s-5);
    border-bottom: 1px solid var(--rule);
}

.product-editor__body {
    flex: 1 1 auto;
    padding: var(--s-5);
    overscroll-behavior: contain;
}

.product-editor__grid {
    display: grid;
    gap: var(--s-6);
    min-width: 0;
}

@media only screen and (min-width: 768px) {
    .product-editor__grid {
        grid-template-columns: minmax(0, 1fr) 15rem;
        align-items: start;
    }
}

.product-editor__fields,
.product-editor__group {
    min-width: 0;
}

.product-editor__group {
    float: none;
    width: auto;
    margin: 0;
    padding: 0;
    border: 0;
}

.product-editor__group + .product-editor__group {
    margin-top: var(--s-6);
    padding-top: var(--s-5);
    border-top: 1px solid var(--rule);
}

.product-editor__group > legend {
    float: none;
    width: auto;
    margin-bottom: var(--s-3);
    padding: 0;
    color: var(--ink-muted);
    font-family: var(--f-condensed);
    font-size: .75rem;
    font-weight: 700;
    letter-spacing: .1em;
    text-transform: uppercase;
}

.product-editor__preview {
    display: flex;
    align-items: center;
    justify-content: center;
    width: 100%;
    min-height: 12rem;
    padding: var(--s-3);
    border: 1px solid var(--rule);
    background-color: var(--page);
    overflow: hidden;
}

.product-editor__preview.is-empty {
    color: var(--ink-muted);
    font-size: .875rem;
    text-align: center;
}

.product-editor__preview-canvas {
    position: relative;
    display: inline-grid;
    width: fit-content;
    max-width: 100%;
    place-items: center;
}

.product-editor__preview-canvas > #uploadedImage {
    grid-area: 1 / 1;
    display: block;
    width: auto;
    max-width: 100%;
    max-height: 15rem;
}

.product-editor__preview-marks {
    --preview-centre-width: 28%;
    position: absolute;
    inset: 0;
    pointer-events: none;
}

.product-editor__preview-marks > img {
    position: absolute;
    display: block;
    height: auto;
}

.product-editor__preview-corner {
    top: 0;
    left: 0;
    width: 30%;
}

.product-editor__preview-centre {
    top: 50%;
    left: 50%;
    width: var(--preview-centre-width);
    opacity: .18;
    transform: translate(-50%, -50%);
}

.product-editor__preview-note {
    margin-top: var(--s-2);
    color: var(--ink);
}

.product-editor__footer {
    z-index: 2;
    display: flex;
    flex: 0 0 auto;
    align-items: center;
    justify-content: flex-end;
    gap: var(--s-2);
    padding: var(--s-3) var(--s-5) max(var(--s-3), env(safe-area-inset-bottom));
    border-top: 1px solid var(--rule);
    background-color: var(--surface);
}

.product-editor-page {
    max-width: 70rem;
    margin: 0 auto;
}

.product-editor-page__back {
    display: inline-block;
    min-height: 44px;
    padding: .625rem 0;
    color: var(--ink-muted);
    font-family: var(--f-condensed);
    font-weight: 700;
    text-decoration: none;
    text-transform: uppercase;
}

.product-editor-page__back:hover {
    color: var(--ink);
    text-decoration: underline;
    text-underline-offset: .2em;
}

.product-editor-page__intro,
.product-editor-page__body {
    padding: var(--s-5);
}

.product-editor-page__intro {
    padding-bottom: 0;
}

.product-editor-page .product-editor__footer {
    position: sticky;
    bottom: 0;
}

.product-save-status {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    gap: var(--s-2) var(--s-4);
    margin-bottom: var(--s-4);
    padding: var(--s-3) var(--s-4);
    border-top: 1px solid var(--rule);
    border-bottom: 1px solid var(--rule);
    background-color: var(--surface);
}

.product-save-status__message {
    flex: 1 1 22rem;
}

/* The way back from a one-click hide. Sticky to the bottom of the products
   area rather than fixed to the window: it stays in view while the table
   scrolls under it, wherever the hidden row was, and it leaves with the table
   rather than floating over the pagination and the footer. The accent is the
   mark on its edge, not its ground - it is a notice, not an alarm. */
.product-undo {
    position: sticky;
    bottom: 0;
    z-index: 3;
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    gap: var(--s-2) var(--s-3);
    margin-top: var(--s-3);
    padding: var(--s-2) var(--s-2) var(--s-2) var(--s-4);
    border: 1px solid var(--rule-strong);
    border-inline-start: 2px solid var(--accent);
    background-color: var(--surface);
}

.product-undo__message {
    flex: 1 1 18rem;
    font-size: .875rem;
}

.product-undo .btn {
    min-height: 44px;
}

.product-undo .btn-close {
    width: 44px;
    height: 44px;
    padding: 0;
}

/* Set apart from the fields above it: it is about the product, not about any
   one field. */
.product-editor__delete-hint {
    margin-top: var(--s-6);
    padding-top: var(--s-4);
    border-top: 1px solid var(--rule);
}

.dash-row.is-saved > * {
    background-color: #FDF3F3;
    transition: background-color 600ms ease-out;
}

@media only screen and (max-width: 575.98px) {
    .product-editor-page__body,
    .product-editor-page__intro,
    .product-editor__header,
    .product-editor__body {
        padding-right: var(--s-3);
        padding-left: var(--s-3);
    }

    .product-editor__footer {
        justify-content: stretch;
        padding-right: var(--s-3);
        padding-left: var(--s-3);
    }

    .product-editor__footer > * {
        flex: 1 1 0;
    }
}

@media (prefers-reduced-motion: reduce) {
    .dash-row.is-saved > * {
        transition: none;
    }
}

/* ---------------------------------------------------------------------------
   Admin settings.

   A short operating form, not a field dump: each section explains the public
   consequence on the left and keeps its controls together on the right.
   --------------------------------------------------------------------------- */
.admin-settings__head {
    margin-bottom: var(--s-4);
}

.admin-settings__notice {
    margin-bottom: var(--s-4);
    padding: var(--s-3) 0;
    border-top: 1px solid var(--rule-strong);
    border-bottom: 1px solid var(--rule-strong);
    color: var(--ink);
}

/* A failed test email: the same ruled band, its rules in the accent, because
   it carries the mail server's own error for the owner to act on. */
.admin-settings__notice--error {
    border-color: var(--accent);
    overflow-wrap: anywhere;
}

.admin-settings-form {
    display: grid;
    gap: var(--s-4);
}

.admin-settings__section {
    display: grid;
    gap: var(--s-5);
    padding: var(--s-5);
}

.admin-settings__fields {
    display: grid;
    gap: var(--s-4);
}

.admin-settings__field--wide {
    min-width: 0;
}

.whatsapp-setting {
    display: grid;
    gap: var(--s-3);
    padding-top: var(--s-4);
    border-top: 1px solid var(--rule);
}

.whatsapp-setting__inherit {
    display: flex;
    align-items: center;
    gap: var(--s-2);
    min-height: 44px;
    margin: 0;
    padding-left: 0;
}

.whatsapp-setting__inherit .form-check-input {
    flex: 0 0 auto;
    width: 1.25rem;
    height: 1.25rem;
    margin: 0;
    cursor: pointer;
}

.whatsapp-setting__inherit .form-check-label {
    cursor: pointer;
}

.whatsapp-setting__number {
    min-width: 0;
}

.whatsapp-setting__number.is-inherited .form-label,
.whatsapp-setting__number.is-inherited .form-control {
    color: var(--ink-muted);
}

/* While WhatsApp uses the primary phone, the separate number is a read-only
   box nobody can use, so its label and box go. The hint under them stays: it is
   what says which number WhatsApp is on. CSS rather than settings.js, so it
   holds before the script runs, and a rejected number stays in view so its
   error can be seen. The value still submits; the controller ignores it while
   the box is ticked. */
.whatsapp-setting:has([data-whatsapp-inherit]:checked) .whatsapp-setting__number:not(:has(.is-invalid)) > :is(.form-label, .form-control) {
    display: none;
}

.whatsapp-setting__number .form-control[readonly] {
    border-color: var(--rule);
    background-color: var(--page);
    cursor: default;
}

/* The on/off switch on the Settings screen, used by the email notifications.
   The status word follows the box rather than an id, so another switch can
   share it. */
.setting-switch {
    display: flex;
    align-items: flex-start;
    gap: var(--s-3);
    min-height: 44px;
    padding-bottom: var(--s-4);
}

.setting-switch.form-switch {
    padding-left: 0;
}

.setting-switch .form-check-input {
    flex: 0 0 auto;
    width: 2.75rem;
    height: 1.5rem;
    margin: .125rem 0 0;
    cursor: pointer;
}

.setting-switch label {
    display: grid;
    gap: var(--s-1);
    cursor: pointer;
}

.setting-switch__status {
    color: var(--ink-muted);
    font-family: var(--f-condensed);
    font-size: .8125rem;
    font-weight: 700;
    text-transform: uppercase;
}

.setting-switch__status--off {
    display: none;
}

.setting-switch .form-check-input:not(:checked) ~ label .setting-switch__status--on {
    display: none;
}

.setting-switch .form-check-input:not(:checked) ~ label .setting-switch__status--off {
    display: inline;
}

@media only screen and (min-width: 992px) {
    .admin-settings__section {
        grid-template-columns: minmax(12rem, 16rem) minmax(0, 1fr);
    }
}

@media only screen and (min-width: 768px) {
    .admin-settings__fields--contact {
        grid-template-columns: repeat(2, minmax(0, 1fr));
    }

    .admin-settings__fields--location {
        grid-template-columns: minmax(8rem, .7fr) repeat(2, minmax(0, 1fr));
    }

    .admin-settings__field--wide {
        grid-column: 1 / -1;
    }
}

@media only screen and (max-width: 575.98px) {
    .admin-settings__section {
        padding: var(--s-4) var(--s-3);
    }
}

/* ---------------------------------------------------------------------------
   Admin table type.

   /admin/dashboard rendered 291 of its 292 elements at --t-6: the column
   labels, the cell text, the muted brand and category lines and the product
   title were all one size, against nine sizes on /catalog over the same data.
   Tokens were never the problem - every colour, face and size on the admin
   already existed on the storefront - the scale simply went unused, so a
   twelve-row, six-column table gave the eye no entry point.

   Nothing new is introduced here. A catalog card carries these same three
   facts and already ranks them, so the row borrows the card's roles: the
   taxonomy reads as a caption, and the column label takes the same voice the
   catalog's own filter-group heads use. The title and the mono reference keep
   --t-6 and become the largest things in the row by leaving them alone.
   --------------------------------------------------------------------------- */
/* The head itself is specified in 06-admin.css, not here.

   A `.dash-table thead th` rule used to sit at this point painting the head
   --bar with 13px labels, written when the admin's table heads were dark. They
   are not any more: `.admin-dashboard .table > thead > tr > th` paints them on
   --page in the muted ink, and every .dash-table on the site is inside
   .admin-dashboard, so that rule is more specific and won on all three of them.
   Both of its declarations were being overridden, which made this the file that
   explained the decision and 06-admin.css the file that made it - and the size
   the screen actually used was not the size argued for here.

   One rule now, where the ground it needs is also stated. What stays in this
   section is the ranking above, which is about the cells. */

/* The sort button inherits `font: inherit` from .table-sort below, which picks
   up the head's size from that rule; the letter-spacing has to be asked for
   explicitly. */
.dash-table thead .table-sort {
    letter-spacing: inherit;
}

/* The sort control in a table head. It sits on .table-dark, so it inherits the
   head's colour rather than the body ink. */
.table-sort {
    display: inline-flex;
    align-items: center;
    gap: var(--s-2);
    min-height: 44px;
    padding: 0;
    border: 0;
    background: none;
    color: inherit;
    font: inherit;
    text-transform: inherit;
}

.table-sort:hover {
    color: var(--accent-on-dark);
}

/* .font-primary sets the same colour for a link and its :hover, so any link
   carrying it has no hover state of its own. The dashboard's remaining ones - the
   storefront link in a row's action group and the product names on the statistics
   tab - get one here. */
#table-products-dashboard a.font-primary:hover,
.chart-table__link:hover {
    color: var(--accent);
}

/* Bootstrap's .btn-link is #0d6efd, a blue that appears nowhere in this
   palette; it was reaching the page on the dialogs' Cancel. The reset-filter
   links carry .text-danger, which is !important and still wins over this. */
.btn-link {
    color: var(--ink-muted);
}

.btn-link:hover {
    color: var(--ink);
}

.page-item.active .page-link {
    background-color: var(--ink);
    border-color: var(--ink);
    color: var(--page);
}

/* The framework's own paginator, which the dashboard's three server-rendered
   tables use, against the hand-written partial the catalog uses. The partial
   carries .rounded-0.border-0.bg-gray on every link; the framework's view carries
   none of them, so the same control was drawn twice in two shapes on one site.
   The shape belongs here rather than in a utility class on each anchor. */
/* The items sat flush against each other, so the filled current-page block ran
   straight into the number beside it and the strip read as one continuous band
   rather than as separate pages. Bootstrap's own spacing comes from a border
   this design removes, which is why nothing was left holding them apart. */
.pagination {
    gap: var(--s-1);
    /* The list carried Bootstrap's bottom margin and no top one, so it sat
       flush against whatever it paged - measured 1px under the products table.
       Symmetrical, so the control reads as separate from the thing above it
       rather than as the table's last row. */
    margin-top: var(--s-4);
}

.pagination .page-link {
    /* Every cell carries its rule, not just the current one. Unbordered, the
       pager read as a row of loose numerals with a single black square in it;
       the design draws the whole set as cells, so the current page is the one
       that is filled rather than the only one that exists. */
    border: 1px solid var(--rule-strong);
    border-radius: 0;
    background-color: var(--page);
    color: var(--ink);
    font-family: var(--f-mono);
    font-size: .8125rem;
}

.pagination .page-link:hover {
    color: var(--accent);
}

.pagination .disabled > .page-link,
.pagination .page-item.disabled .page-link {
    color: var(--ink-muted);
    background-color: var(--page);
    /* Bootstrap gives the disabled cell its own border-color at this same
       specificity, so the rule above it does not reach: a greyed-out arrow drew
       #dee2e6 while every cell beside it drew --rule-strong. It is the one
       pagination cell nobody clicks, which is why it went unnoticed. */
    border-color: var(--rule-strong);
}

/* Bootstrap rounds the two end caps through .page-item:first-child .page-link -
   three classes, which outranks the .pagination .page-link above and is why the
   pager kept 4px corners on the ends while every cell between them was square.
   The custom pager hides it with a rounded-0 in the markup; the three admin
   screens on Laravel's default paginator have no such class, so the same
   component was round-ended on Statistics and square everywhere else. */
.pagination .page-item:first-child .page-link,
.pagination .page-item:last-child .page-link {
    border-radius: 0;
}

.rotate {
    -moz-transition: all .1s linear;
    -webkit-transition: all .1s linear;
    transition: all .1s linear;
}
.rotate.down {
    -moz-transform:rotate(180deg);
    -webkit-transform:rotate(180deg);
    transform:rotate(180deg);
}

/* The caret belongs to the column that is sorting, and only to it. Both
   sortable heads drew one unconditionally, so the strip looked identical
   whichever column was active - and on first load, where the order is 'latest'
   and neither column sorts, both still pointed somewhere.

   visibility rather than display, so the head does not reflow by 20px each time
   the sort moves between columns. */
th[aria-sort="none"] .table-sort .rotate {
    visibility: hidden;
}

/* The affordance survives: hovering or tabbing to an inactive head shows the
   caret it would set, muted. */
th[aria-sort="none"] .table-sort:hover .rotate,
th[aria-sort="none"] .table-sort:focus-visible .rotate {
    visibility: visible;
    opacity: .45;
}

/* Below Bootstrap's xxl (1400). */
@media only screen and (max-width: 1399.98px) {
    .css-hide {
        display: none;
    }

    .product-image {
        object-fit: contain;
        width: 220px;
        height: 220px;
    }

    .product-image-placeholder.product-image {
        width: 220px;
        height: 220px;
    }

}

/* Below Bootstrap's sm (576), matching every d-sm-* utility in the views. */
@media only screen and (max-width: 575.98px) {
    .product-image {
        object-fit: contain;
        width: 220px;
        height: 220px;
    }

    .product-image-placeholder.product-image {
        width: 220px;
        height: 220px;
    }

    .css-hide {
        display: block;
    }

    .logo {
        max-width: 104px;
        height: auto;
        cursor: pointer;
    }

    .bi-telephone-fill {
        height: 16px;
        width: 16px;
        display: none;
    }

    /* .header-text-phone was pinned to 18px here, which is the same hard
       phone-size override the type scale replaced everywhere else: .fs-3 already
       clamps to 20px at 390px. */

    .landing-page-image-big {
        min-height: 0;
        width: 100%;
        clear: both;
    }
}

.page-link, li.page-item.disabled {
    border-style: none;
    color: var(--ink);
    border-radius: 0;
}

/* Pagination measured 30px tall on a phone. */
.page-link {
    min-width: 44px;
    min-height: 44px;
    display: flex;
    align-items: center;
    justify-content: center;
}

/* Nothing on the site cleared 44x44 on a phone - not one of the 94 controls
   measured. These are the ones a visitor actually drives the funnel with. */
.js-add-product,
.js-remove-product,
.sort-direction,
.navbar-toggler,
#sortProducts,
.filter-chip,
.js-filter-toggle {
    min-height: 44px;
}

.sort-direction,
.navbar-toggler {
    min-width: 44px;
}

/* Buttons only ever grow to the floor here; btn-sm is excluded because the card
   CTA above already sets its own. */
.btn:not(.btn-sm) {
    min-height: 44px;
}

/* Inline text links in the masthead: padding rather than a min-height, so they
   gain a target without breaking the line box around them.

   `footer a` was here too, and it was doing two things it should not. It was an
   element selector on every footer on the site, so the dashboard's product
   editor - which closes its panel with a <footer> - inherited 24px of vertical
   padding on its buttons for no reason. And in the site footer it applied at
   every width, which is what put ~55px between two words in a desktop column
   that the design sets 10px apart. The site footer's own .footer-link carries
   the thumb-sized target where a thumb is doing the pointing (04-structure.css)
   and nothing above it. */
.header-text-phone a,
.logo-link {
    display: inline-block;
    padding-top: .75rem;
    padding-bottom: .75rem;
}

/* The masthead number and its call-cost notice are one unit, and the rule above
   was pushing them apart: 12px of anchor padding plus the notice's own 8px put
   20px between a number and its own footnote.

   Only the bottom padding gives way, and only here - the top still carries the
   separation from the search row, and the footer keeps the full pair. The target
   stays over the 44px floor with room to spare: .fs-3 clamps to 20px at 390px,
   so the anchor's line box alone is ~30px, and 12px + 6px takes it to ~48px. On
   a desktop it is ~60px. */
.header-text-phone a {
    padding-bottom: .375rem;
    white-space: nowrap;
}

/* The phone number remains the primary call action. Messaging is offered as a
   compact secondary action beside the regulatory call-cost note, so the same
   telephone icon never has two possible outcomes. */
.header-contact-meta {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    justify-content: flex-end;
    gap: 0 var(--s-2);
    color: var(--ink-muted);
    font-size: .75rem;
    line-height: 1.25;
}

@media (max-width: 575.98px) {
    .home-page .header-text-phone {
        font-size: 1.125rem !important;
    }

    .home-page .header-contact-meta {
        max-width: 15rem;
        margin-left: auto;
    }
}

.header-contact-meta a {
    padding: .375rem 0;
    color: var(--ink);
    font-family: var(--f-condensed);
    font-weight: 700;
    letter-spacing: .06em;
    text-underline-offset: .2em;
}

/* Bootstrap ships the box at 1em, which lands at 14px on a phone - below the
   24px AA target floor.

   Bootstrap positions the box by floating it into a padding gutter sized for 1em.
   Growing the box makes that gutter too small, and the label either butts against
   the checkbox or drops to the next line. Laying the row out with flex sizes the
   gap explicitly instead of inferring it from the box, so the two stay aligned at
   any box size. */
.form-check {
    display: flex;
    align-items: flex-start;
    /* So a validation message under a checkbox goes under it. This row is a flex
       container, which makes .invalid-feedback a third item beside the box and the
       label - and the consent error appeared to the right of the label rather than
       below it. */
    flex-wrap: wrap;
    gap: .6rem;
    padding-left: 0;
}

.form-check .invalid-feedback {
    flex: 0 0 100%;
    /* The gap above already spaces it; Bootstrap's own top margin doubles it. */
    margin-top: 0;
}

/* Scoped to .form-check so it outranks Bootstrap's own `.form-check
   .form-check-input { float: left; margin-left: -1.5em }` - a two-class selector
   that a single-class rule here loses to, which left the box hanging a gutter
   out to the left of its own row. */
.form-check .form-check-input {
    flex: 0 0 auto;
    float: none;
    width: 1.5rem;
    height: 1.5rem;
    margin-left: 0;
    margin-top: .1rem;
}

/* Bootstrap's #6c757d is 4.34:1 on the #F6F6F6 page background, just under AA.
   This is the same visual step down, one shade darker. */
.text-muted {
    color: #5f6266 !important;
}

/* ...but the same token also runs on the dark footer and cookie banner, where it
   has to go lighter rather than darker to clear the same bar. */
.bg-dark .text-muted,
.cookie-consent-banner .text-muted {
    color: #b6b9bd !important;
}

/* Same step, same grounds, for copy that is not a Bootstrap utility. */
.bg-dark,
.cookie-consent-banner {
    --note-ink: #b6b9bd;
}

/* The brand logos used to be held together by grayscale + 50% opacity; that job
   now belongs to .brand-rail's cell geometry, which unifies them without
   spending their contrast to do it. */

/* The bottom edge belongs to the cookie banner and back-to-top control. Keep
   notifications at the top right, but below the sticky navigation rather than
   over its quote, account and menu controls. The bar is 56px on desktop and
   60px on compact layouts. */
.toast-region {
    position: fixed;
    top: calc(56px + var(--s-4));
    right: 0;
    padding: 1rem;
    z-index: 2147483647;
}

/* A toast is transient, so its state has to be understood before it disappears.
   Strong semantic surfaces, a written label and a distinct mark carry the same
   message three ways. Legacy selectors remain during the asset-cache window so
   an hour-old toast.js still receives the new treatment. */
.toast-region .toast {
    width: min(26rem, calc(100vw - 2rem));
    max-width: none;
    color: var(--feedback-on-color);
    box-shadow: var(--shadow-2);
}

.toast-region .toast.toast-success,
.toast-region .toast.toast-ok {
    background-color: var(--feedback-success);
}

.toast-region .toast.toast-error,
.toast-region .toast.toast-err {
    background-color: var(--feedback-error);
}

.toast-notice {
    display: grid;
    grid-template-columns: 2.25rem minmax(0, 1fr) auto;
    align-items: center;
    gap: var(--s-3);
    padding: var(--s-3) var(--s-4);
}

.toast-state-mark {
    display: none;
    width: 2.25rem;
    height: 2.25rem;
    align-items: center;
    justify-content: center;
    background-color: rgba(255, 255, 255, .16);
    color: var(--feedback-on-color);
}

.toast-success .toast-state-mark--success,
.toast-ok .toast-state-mark--success,
.toast-error .toast-state-mark--error,
.toast-err .toast-state-mark--error,
.toast-success .toast-state-label--success,
.toast-ok .toast-state-label--success,
.toast-error .toast-state-label--error,
.toast-err .toast-state-label--error {
    display: flex;
}

.toast-copy {
    min-width: 0;
}

.toast-state-label {
    display: none;
    margin-bottom: var(--s-1);
    font-family: var(--f-condensed);
    font-size: .75rem;
    font-weight: 700;
    line-height: 1;
    letter-spacing: .1em;
    text-transform: uppercase;
}

.toast-region .toast-body {
    padding: 0;
    font-size: .9375rem;
    line-height: 1.4;
    overflow-wrap: break-word;
}

.toast-dismiss {
    flex: 0 0 auto;
    margin: 0;
    opacity: 1;
}

@media (max-width: 575.98px) {
    .toast-region {
        top: calc(60px + var(--s-3));
        left: 0;
        padding: var(--s-3);
    }

    .toast-region .toast {
        width: 100%;
    }
}

.page-link:hover {
    background-color: #d9d9d9;
    border-style: none;
    color: black;
}

.force-bg-gray {
    background-color: #F6F6F6 !important;
}

/* Kept focusable instead of `disabled`, which drops the send button out of the
   tab order and announces nothing about why. It still reads as unavailable, and
   activating it gets the message that says what to do. */
.btn[aria-disabled="true"] {
    opacity: .65;
}

/* Moved out of a <style> block inside includes/generic/cookie.blade.php. What
   is left is layout only - the two CTAs are the shared .btn now, which is what
   removed the site's single border-radius: 2px. */
.cookie-consent-banner {
    box-sizing: border-box;
    width: 100%;
    background: var(--bar-raised);
}

.cookie-consent-banner__inner {
    display: grid;
    grid-template-columns: minmax(0, 1fr) auto;
    align-items: center;
    gap: var(--s-4) var(--s-6);
}

.cookie-consent-banner__copy {
    margin-bottom: 0;
}

.cookie-consent-banner__header {
    margin-bottom: var(--s-1);
    color: white;
    font-family: var(--f-condensed);
    font-weight: 700;
    font-size: 1.125rem;
    line-height: 1.2;
}

.cookie-consent-banner__description {
    font-weight: normal;
    color: var(--page);
    line-height: 1.45;
    max-width: 75ch;
}

.has-consent-banner .back-to-top {
    display: none !important;
}

/* The bespoke CTA was 164x44; the shared .btn is smaller, and this is the one
   place on the site where both buttons are the whole interaction. */
.cookie-consent-banner .btn {
    min-width: 9rem;
    min-height: 44px;
}

@media (max-width: 767.98px) {
    .cookie-consent-banner__inner {
        grid-template-columns: 1fr;
        gap: var(--s-2);
    }

    .cookie-consent-banner__header {
        margin-bottom: 0;
        font-size: 1rem;
    }

    .cookie-consent-banner__description {
        font-size: .875rem;
        line-height: 1.35;
    }

    .cookie-consent-banner__actions {
        display: grid !important;
        grid-template-columns: 1fr 1fr;
    }

    .cookie-consent-banner .btn {
        min-width: 0;
        min-height: 44px;
        padding-top: var(--s-2);
        padding-bottom: var(--s-2);
    }
}

/* ---------------------------------------------------------------------------
   Applied-filter chips.

   Above the grid rather than in the rail, because on a phone the rail is a
   closed drawer and the question they answer - why am I looking at 40 products
   and not 9,650 - is asked while looking at the grid.
   --------------------------------------------------------------------------- */
/* A bare <button>, not a .btn, so the user agent's font, radius and cursor all
   have to be answered here - square like every other edge on the site. */
.filter-chip {
    display: inline-flex;
    align-items: center;
    gap: var(--s-2);
    padding: .25rem .5rem .25rem .625rem;
    border: 1px solid var(--rule-strong);
    border-radius: 0;
    background-color: var(--surface);
    color: var(--ink);
    font: inherit;
    font-size: .8125rem;
    line-height: 1.4;
    cursor: pointer;
    transition: border-color .15s ease, color .15s ease;
}
.filter-chip:hover,
.filter-chip:focus-visible {
    border-color: var(--accent);
    color: var(--accent);
}
/* 1.5x the glyph and no larger: the x is the target, but the whole chip is
   clickable, so it does not need to carry the hit area on its own. */
.filter-chip__x {
    font-size: 1.125rem;
    line-height: 1;
    color: var(--ink-muted);
}
.filter-chip:hover .filter-chip__x,
.filter-chip:focus-visible .filter-chip__x {
    color: var(--accent);
}
