/* ========== Navbar Styles ========== */
nav {
    background: #333;
    color: #fff;
    height: 85px;
}
/* Phase 5 A11Y-003: nav title is no longer a <h1> (the global <h1>
 * on every page broke the heading hierarchy and reduced individual
 * page titles to <h2>). Replaced by a <span class="lmt-logo">. */
nav .lmt-logo {
    display: inline-block;
    font-size: 2.5rem;
    letter-spacing: -1px;
}

/* ========== Burger Menu ========== */
/* .burger-menu { display: none; } removed Phase 4 CP2 fix #2.
 * The desktop "hidden" rule was historical dead code: the inline
 * style="display:block" on the <li> always overrode it, so the
 * burger has actually been visible at every breakpoint forever.
 * In C9 the inline was migrated to tw:block (in @layer utilities),
 * which lost the cascade against this unlayered rule on desktop —
 * making the burger genuinely disappear above 768px for the first
 * time. Removing the rule lets the natural <li> default (list-item)
 * + tw:block work, which means burger visible everywhere. */
@media (max-width: 768px) {
    .burger-menu { display: block !important; }
    .navbar .list-inline-item.d-md-inline { display: none !important; }
}

/* ========== Mobile Menu Overlay ========== */
/* Note: jQuery $.fadeIn() forces inline display:block on show, so the
 * overlay is rendered as a block container (not flex). The previous
 * flex-direction/align-items/justify-content rules were inert and
 * were removed in R.A.bis F-9 polish. The 100px 20px padding was
 * also reduced to padding-bottom only because the new structural
 * <div class="...h-[85px]"> wrapper at the top of the overlay (header.php)
 * now provides the close-button row aligned pixel-perfectly with the
 * <nav> burger geometry, so the original 100px top padding would
 * have offset the close 100px below the burger. */
#mobile-menu-overlay {
    display: none;
    position: fixed;
    top: 0; left: 0;
    width: 100vw; height: 100vh;
    z-index: 9999;
    background-attachment: local;
    background-image: linear-gradient(-170deg, #2376ae, #c16ecf);
    color: #fff;
    padding-bottom: 100px;
}
#mobile-menu-overlay ul {
    list-style: none;
    padding: 0;
    margin: 0;
    text-align: center;
    flex: 1;
    display: flex;
    flex-direction: column;
    justify-content: space-evenly;
}
#mobile-menu-overlay li {
    margin: 0;
    padding-bottom: 2rem;

    letter-spacing: 1px;
    font-size: 2rem;
}

/* R.A.bis: extend selector to .lmt-link-button so Contact us /
 * Support us entries (rendered as <button data-lmt-dialog>, not <a>)
 * share the same visual treatment as the <a> menu links. */
#mobile-menu-overlay :is(a, .lmt-link-button) {
    color: #fff;
    text-decoration: none;
    -webkit-font-smoothing: antialiased;
    text-shadow: 2px 2px 0 #1c5e8b;
}

#close-mobile-menu {
    background: none;
    border: none;
    color: #fff;
    font-size: 2rem;
    z-index: 10000;
    cursor: pointer;
}
#mobile-menu-overlay[style*="display: none"] {
  pointer-events: none !important;
  opacity: 0 !important;
}

/* ========== Contact Form 7 ========== */
.wpcf7 form.sent .wpcf7-response-output {
    width: 100%;
    border: solid 2px #fff;
}

/* ========== Menu Overlay Entrance Animations ========== */
.menu-fade-in {
    opacity: 0;
    transform: translateY(20px);
    transition: opacity 0.6s cubic-bezier(0.4,0,0.2,1), transform 0.6s cubic-bezier(0.4,0,0.2,1);
}
.menu-fade-in.visible {
    opacity: 1;
    transform: none;
}
.menu-delay-1 { transition-delay: 0.1s; }
.menu-delay-2 { transition-delay: 0.2s; }
.menu-delay-3 { transition-delay: 0.3s; }
.menu-delay-4 { transition-delay: 0.4s; }
.menu-delay-5 { transition-delay: 0.5s; }

/* ========== [END navbar.css] ========== */