/*
 * Plugin chrome stylesheet — loaded on theme-rendered pages alongside front.css.
 * The injected header/footer use the new fourka.dev markup (.nav / .footer), which
 * front.css already styles. This file handles theme integration: hide the active
 * theme's own header/footer so the plugin chrome takes over, and keep the sticky
 * nav above any theme stacking context. The plugin chrome uses
 * `header.nav.aytin-chrome-header` and `footer.footer`, so the selectors below are
 * scoped to theme markup and never touch the plugin's own chrome.
 */

/* Twenty Twenty-Five (and other block themes): hide the header/footer template
   parts. The plugin nav/footer are injected via wp_body_open / wp_footer, so they
   sit OUTSIDE .wp-site-blocks and carry no .wp-block-template-part class. */
body.aytin-chrome-active .wp-site-blocks > header,
body.aytin-chrome-active .wp-site-blocks > footer,
body.aytin-chrome-active header.wp-block-template-part,
body.aytin-chrome-active footer.wp-block-template-part {
    display: none !important;
}

/* Jannah (classic theme) chrome — harmless no-ops when Jannah is inactive. */
body.aytin-chrome-active #theme-header,
body.aytin-chrome-active #mobile-header,
body.aytin-chrome-active .side-aside,
body.aytin-chrome-active .rainbow-line,
body.aytin-chrome-active #footer {
    display: none !important;
}

body.aytin-chrome-active #tie-wrapper,
body.aytin-chrome-active #tie-container {
    margin-top: 0 !important;
    padding-top: 0 !important;
}

/* Lift the sticky plugin nav above any theme-created stacking context. */
body.aytin-chrome-active .nav {
    z-index: 999;
}