/* The alpha/testnet notice — `common_wasm::alpha_banner::AlphaBanner`.
 *
 * Its own file rather than a block in common.css because only three of the eight panes link
 * common.css at all: membership, leaderboard and admin link no stylesheet whatsoever, and adding
 * 172 lines of shared styling to them to deliver two rules would restyle three panes as a side
 * effect of a one-sentence notice. One file per concern is already this directory's convention
 * (landing.css, scoring.css, flashcard.css); this is one more.
 *
 * FIXED, not in flow. One pane (game_3d) is a 100vw x 100vh canvas under `overflow: hidden`, so an
 * in-flow banner would push its canvas off-screen. The offsets below give the seven in-flow panes
 * their space back, keyed on the four container shapes the panes actually use.
 */
.alpha-banner {
    position: fixed;
    top: 0;
    left: 0;
    right: 0;
    z-index: 9999;
    display: flex;
    gap: 0.75rem;
    align-items: center;
    justify-content: center;
    padding: 0.4rem 0.75rem;
    background: #7a3b00;
    color: #fff;
    font-family: sans-serif;
    font-size: 0.85rem;
    line-height: 1.3;
    box-sizing: border-box;
}

.alpha-banner-link {
    color: #ffd9a0;
    text-decoration: underline;
    white-space: nowrap;
}

/* `:has()` so a pane that adds a new container shape still gets its offset without editing this
 * file. Chrome/Edge/Safari 18+ all support it, which is the browser floor the guide already states
 * (docs/user-stories.md). A browser without it renders the banner over ~2rem of the page rather
 * than above it — degraded, not broken. */
body:has(.alpha-banner) .production-app,
body:has(.alpha-banner) .landing-app,
body:has(.alpha-banner) .in-game-app,
body:has(.alpha-banner) main {
    padding-top: 2rem;
}