/*
    Only what MudBlazor does not already provide: the pre-Blazor loading shell, the framework's
    error strip, and a couple of layout helpers. Everything else is left to the component library,
    so the application has one source of styling rather than two that drift.
*/

html, body {
    margin: 0;
    font-family: "Segoe UI", Roboto, "Helvetica Neue", Arial, sans-serif;
}

.loading-shell {
    display: flex;
    align-items: center;
    justify-content: center;
    height: 100vh;
    color: #5c6a67;
    font-size: 0.95rem;
}

#blazor-error-ui {
    display: none;
    position: fixed;
    bottom: 0;
    left: 0;
    right: 0;
    z-index: 1000;
    padding: 0.7rem 1.2rem;
    background: #fdf3d8;
    border-top: 1px solid #e0cf9a;
    color: #4a3c12;
    box-shadow: 0 -1px 3px rgba(0, 0, 0, 0.12);
}

#blazor-error-ui .dismiss {
    position: absolute;
    top: 0.5rem;
    right: 0.9rem;
    cursor: pointer;
}

/* Page bodies breathe a little; MudBlazor's containers are deliberately tight by default. */
.page-section {
    margin-bottom: 1.5rem;
}

/*
    A settings row with changes that have not been saved yet. Warning-tinted rather than primary so it
    reads as "needs attention", not as "selected". Uses the theme's own hover shade, so it follows the
    palette instead of hard-coding a colour that would clash with a future dark theme.
*/
.row-unsaved {
    background-color: var(--mud-palette-warning-hover);
}