/* /Components/Layout/MainLayout.razor.rz.scp.css */
/*
    Only the error bar is left here.

    Everything else in this file was the Blazor template's Bootstrap layout — .page, .sidebar,
    .top-row, article — and none of those class names has existed in MainLayout.razor since the
    design system replaced Bootstrap. Scoped CSS is bundled into Multimon.Web.styles.css whether or
    not anything matches it, so dead rules ship on every page.

    These two blocks are not dead, and they outrank the Tailwind classes on the same element:
    scoped CSS rewrites the selector to #blazor-error-ui[b-xxxxxxxxxx], which beats a utility class
    on specificity. The position and z-index of the error bar are decided here, not by the markup.

    Its colours are deliberately *not*, and that is the whole point of this note. This block carried
    the template's "color-scheme: light only; background: lightyellow" while the markup asked for
    bg-surface and text-ink — and because of the specificity above, the light background won while
    the near-white text did not, so the bar read as white on pale yellow. Nothing in the source
    looked wrong: MainLayout.razor names the right colours, this file names the wrong ones, and only
    the rendered page shows which of the two the browser took. Leave the colours to the markup;
    anything set here silently overrules it.
*/

#blazor-error-ui[b-anh0h0np8d] {
    bottom: 0;
    box-shadow: 0 -1px 2px rgba(0, 0, 0, 0.2);
    box-sizing: border-box;
    display: none;
    left: 0;
    padding: 0.6rem 1.25rem 0.7rem 1.25rem;
    position: fixed;
    width: 100%;
    z-index: 1000;
}

    #blazor-error-ui .dismiss[b-anh0h0np8d] {
        cursor: pointer;
        position: absolute;
        right: 0.75rem;
        top: 0.5rem;
    }