/*
    Only what MudBlazor does not already provide: the pre-Blazor loading shell, the framework's
    error strip, and a layout helper. 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 screenshot thumbnail, pending or stored. Bounded both ways so a tall phone screenshot and a
   wide monitor one take similar room. */
.image-thumb {
    display: block;
    max-height: 96px;
    max-width: 180px;
    border: 1px solid var(--mud-palette-lines-default);
    border-radius: 4px;
}

/* A pending image with its remove button in the corner. */
.pending-image {
    position: relative;
}

.pending-image-remove {
    position: absolute;
    top: -8px;
    right: -8px;
    background-color: var(--mud-palette-surface);
}

/* Post text is shown exactly as typed: line breaks kept, long unbroken strings (URLs, stack
   traces) wrapped rather than widening the page. */
.post-body {
    white-space: pre-wrap;
    overflow-wrap: anywhere;
}

/* Internal notes must never be mistaken for replies the customer can see. Warning-tinted, using
   the theme's own shade so it follows the palette. */
.internal-note {
    background-color: var(--mud-palette-warning-hover);
}