/* ============================================================================
   Daybreak-specific overrides for the 2026 login engine (PR 8 Phase A.3).
   login-2026.css already lays the form to the LEFT (`.lg-shell {
   justify-content: flex-start; padding-left: max(24px, 5vw); }`). Daybreak's
   theme template wraps the login view in `.public-content-area` which
   centers its child via flex, undoing the engine's left-align and pushing
   the glass card to the middle of the viewport on top of the scene.

   Strip that wrapper's centering whenever the body has `.lg-host` so the
   engine's own positioning wins. Mobile (`@media (max-width: 880px)`) in
   login-2026.css will still re-center the card at narrow widths.
   ============================================================================ */
body.lg-host .public-content-area {
    display: block !important;
    align-items: stretch !important;
    justify-content: flex-start !important;
    padding: 0 !important;
    background: transparent !important;
    min-height: 100vh;
}

/* Daybreak's #content padding shrinks the visible scene area; zero it on
   login pages so the scene + glass form get the whole viewport. */
body.lg-host #content,
body.lg-host #wrapper,
body.lg-host .main-container {
    padding: 0 !important;
    margin: 0 !important;
    max-width: none !important;
    min-height: 100vh;
}

/* Daybreak's index.php base body rule sets `display: flex; flex-direction:
   column` which is fine for normal pages but on login we want the scene to
   own absolute positioning under the form. The .lg-shell handles its own
   layout, so resetting body to block-flow keeps the engine in charge. */
body.lg-host {
    display: block !important;
}

/* PR 8 Phase F.1 - the admin chrome bundle (_layout.css) pushes body
   down by header-height + 10px to clear its fixed header. Login pages
   don't render the header, so the padding would leave a gap above the
   scene + form. Zero it out for lg-host. Same for the wrapper margin
   from _layout.css (no sidebar on login either). */
body.lg-host,
body.theme-new.lg-host {
    padding-top: 0 !important;
}

body.theme-new.lg-host #wrapper,
body.theme-new.lg-host .content-wrapper {
    margin-left: 0 !important;
    min-height: 100vh !important;
}

/* Information notice inside the sign-in card (flash "info"). It takes the
   card's own text colour, so it reads on the light card and on the dark one,
   and it never floats over the scene. */
body.lg-host .lg-card .lg-note {
    margin: 0 0 16px;
    padding: 10px 14px;
    border-radius: 12px;
    border: 1px solid rgba(var(--lg-green-rgb), 0.45);
    border-left-width: 4px;
    background: rgba(var(--lg-green-rgb), 0.10);
    color: var(--lg-text);
    font-size: 13px;
    font-weight: 500;
    line-height: 1.45;
    text-align: left;
    overflow-wrap: anywhere;
}

/* The same notice is not repeated as a floating toast on the sign-in page. */
body.lg-host .float-alert.alert-info {
    display: none !important;
}

/* Floating toasts on the sign-in page (wrong password, account messages...):
   solid surface and readable text over the dark scene, for every type. */
body.lg-host .float-alert {
    background: #ffffff !important;
    color: #14181d !important;
    border: 1px solid rgba(20, 24, 29, 0.12) !important;
    border-left: 4px solid #5b6472 !important;
    -webkit-box-shadow: 0 16px 40px -12px rgba(0, 0, 0, 0.55);
            box-shadow: 0 16px 40px -12px rgba(0, 0, 0, 0.55);
    z-index: 100000;
}
body.lg-host .float-alert .alert-title,
body.lg-host .float-alert .close,
body.lg-host .float-alert [data-notify="icon"] {
    color: #14181d !important;
    opacity: 1;
    text-shadow: none;
}
body.lg-host .float-alert.alert-danger  { border-left-color: #d92d20 !important; }
body.lg-host .float-alert.alert-warning { border-left-color: #dc6803 !important; }
body.lg-host .float-alert.alert-success { border-left-color: #079455 !important; }
