.mud-select .mud-popover-cascading-value {
    z-index: calc(var(--mud-zindex-popover) + 1);
}

.mud-card-header > .mud-grid {
    margin-left: 6px !important;
    
    .mud-grid-item {
        padding-left: 0;
        width: min-content !important;
        max-width: fit-content !important;
    }
}

.fix-pos.mud-grid.mud-grid-spacing-xs-6.justify-start {
    width: calc(100% + 32px) !important;
    margin-left: -15px !important;
    > .mud-grid-item {
        padding-left: 16px;
        padding-right: 16px;
    }
}

@media (max-width: 768px) {
    .fix-pos.mud-grid.mud-grid-spacing-xs-6.justify-start {
        width: calc(100% + 34px) !important;
        margin-left: -16px !important;
    }   
}

.mud-table-foot th {
    display: none !important;
}

.mud-primary-text {
    color: var(--mud-palette-primary-text) !important;
}

.mud-secondary-text {
    color: var(--mud-palette-secondary-text) !important;
}

/*
    REMOVED (2026-08-25): an override that redefined `.mud-secondary-text` to use
    `--mud-palette-secondary-text`.

    Those are three different things and it is worth writing down, because mixing them up is what
    produced the unreadable text this file was patching around:

      .mud-secondary-text  -> color: var(--mud-palette-secondary)        "text in the BRAND color"
      .mud-text-secondary  -> color: var(--mud-palette-text-secondary)   "muted body ink"
      .mud-theme-secondary -> bg secondary + color secondary-text        "an ON-secondary surface"

    `--mud-palette-secondary-text` is the ink meant to sit ON a secondary-colored fill. In the
    Light theme it is white — so making `.mud-secondary-text` use it turned every
    `Color="Color.Secondary"` piece of text white-on-white on an ordinary surface. It appeared to
    help only because it happened to cancel out the real bug, which was in the palette itself:
    several `*ContrastText` slots in Theming/AppThemes.cs were unset and silently defaulting to
    white on mid-tone brand fills (2.59:1 on the orange Wholesale badge). That is fixed at the
    source now, with the measurements recorded there — so this override is not needed, and
    reinstating it would break MudBlazor's own components that legitimately use the class.
*/