/* Confirmation modal shared by the session-conflict popups on the login page, the
   password-reset page, and the account-setup page. Kept in one file so the three
   do not drift; setup-account.html is a standalone page and links this directly. */

/* Bold face for the modal buttons. login.css only registers the regular weight of
   AvenirNextLTProReg, so without this a bold button has no real face to render and
   the browser either synthesises it or ignores the weight entirely. */
@font-face {
    font-family: AvenirNextModalBold;
    src: url(../js/lib/login/fonts/AvenirNext-Bold.ttf);
    font-weight: 700;
}

.session-conflict-overlay {
    position: fixed;
    top: 0; left: 0; right: 0; bottom: 0;
    background: rgba(0, 0, 0, 0.5);
    display: flex;
    align-items: center;
    justify-content: center;
    z-index: 1050;
}

/* Fonts are pinned throughout because the two pages resolve them differently:
   main.css sets AvenirNextLTPro on `button, html, input...` while login.css sets
   AvenirNextLTProReg on `html, body`, so which face wins depends on stylesheet
   order. Stating it here keeps the popup identical on both. */
.session-conflict-modal,
.session-conflict-modal h4,
.session-conflict-modal p {
    font-family: AvenirNextLTProReg, AvenirNextLTPro, sans-serif;
}

/* Buttons deliberately omitted above: AvenirNextLTProReg is registered with a
   single regular TTF and no bold variant, so pinning it here would leave
   font-weight with nothing to render. */

.session-conflict-modal {
    background: #fff;
    border-radius: 8px;
    padding: 36px;
    max-width: 560px;
    width: 92%;
    box-shadow: 0 4px 20px rgba(0, 0, 0, 0.3);
    text-align: center;
}

.session-conflict-modal h4 {
    color: #2c5aa0;
    margin-top: 0;
    margin-bottom: 18px;
    font-weight: 600;
    font-size: 26px;
}

.session-conflict-modal p {
    color: #333;
    margin-bottom: 28px;
    font-size: 18px;
}

.session-conflict-actions {
    display: flex;
    gap: 14px;
    justify-content: center;
}

/* Weight is set explicitly rather than inherited: the SPA and the standalone
   setup page load different Bootstrap builds, so the same markup renders with
   different button weights unless pinned here. */
.session-conflict-actions .btn {
    min-width: 160px;
    font-size: 16px;
    padding: 10px 18px;
    font-family: AvenirNextModalBold, AvenirNextLTPro, sans-serif;
    font-weight: 700;
}

/* Matches login.css .btn-primary, which the SPA pages pick up but the standalone
   setup page does not. */
.session-conflict-actions .btn-primary {
    background-color: #306db6;
    border-color: #306db6;
    color: #fff;
}

.session-conflict-actions .btn-default {
    background-color: #fff;
    border-color: #ccc;
    color: #333;
}