/* * Dokka theme overrides aligning the API reference with the project's Zensical site * (Material Design 3 chrome: indigo primary, slate dark, Inter + JetBrains Mono). * * Companion to dokka-zensical-chrome.js, which rewrites the page DOM at load time to * produce real .md-* scaffolding. This stylesheet (a) loads the Material fonts, (b) * hides Dokka's native chrome so it doesn't flash, (c) overrides Dokka's CSS variables * for both light and dark schemes, (d) keeps Dokka content tables visible inside the * Material content area. * * Loaded via Dokka 2.x `pluginsConfiguration.html.customStyleSheets` in * compose-highlight/build.gradle.kts. See compose-highlight/dokka-theme/README.md. */ @import url("https://fonts.googleapis.com/css?family=Inter:300,400,500,700&family=JetBrains+Mono:400,500,700&display=fallback"); /* ── Hide Dokka's native chrome ───────────────────────────────────────────── * The chrome script wraps Dokka's #content inside Material scaffolding. Hide Dokka's * old top header and sidebar source-of-truth so they don't flash or render twice. * * The Dokka `#leftColumn` sidebar source is also hidden — our chrome script reads * `navigation.html` directly, so the in-DOM sidebar is redundant. * * Critical: we do NOT hide #filter-section or #searchBar with display:none. Dokka's * platform-content-handler.js initializes filter buttons in #filter-section on * window.load and walks .main-content for member visibility. If #filter-section's * children are display:none Dokka's init aborts and the Members section never shows. * Same kind of trap with #searchBar — it must remain interactive so we can delegate * Material's search icon clicks to it. Hide them off-screen instead. */ #navigation-wrapper, #leftColumn, .library-name, .navigation-controls--break, /* Dokka's stock footer (.footer with go-to-top + copyright) — replaced by our * Material .md-footer-meta block injected inside .md-container. */ #main > .footer, .footer--container { display: none !important; } /* #filter-section: kept addressable but visually pushed off-screen so * platform-content-handler.js can populate it without it appearing on-page. * Children stay un-pointer-event-disabled so its filter-button init walks. */ #filter-section { position: absolute !important; left: -10000px !important; top: 0 !important; pointer-events: none; } /* #searchBar: kept addressable via off-screen positioning. The Material icon * at [data-search-trigger] is the visible click target; the chrome script * delegates to the inner #pages-search programmatically. */ #searchBar { position: absolute !important; left: -10000px !important; top: 0 !important; pointer-events: none !important; } /* Ring UI's search popup is rendered via a React portal into a target div * appended to , with the popup positioned via inline `top: 0; left: 0` * but offset upward by a JS-applied `margin-top: -px`. The trigger * (#searchBar) is off-screen at left:-10000, so the popup ends up at * viewport y = - with the input row clipped above * viewport. * * Override the inline positioning so the popup pins to the top-right of the * viewport, just below the Material header. The popup-wrapper class targets * Ring UI's popup container; the rule only matches when the popup is mounted * (which is on demand, not at page load). */ [data-test="ring-popup"][data-test-direction="bottom-right"] { position: fixed !important; top: 3.5rem !important; /* below the Material header (~3rem) */ right: 1rem !important; left: auto !important; bottom: auto !important; margin: 0 !important; max-width: min(640px, calc(100vw - 2rem)) !important; max-height: calc(100vh - 5rem) !important; z-index: 1000 !important; } /* The chrome script removes Dokka's