/* Copyright (C) 2026 Intel Corporation */ /* SPDX-License-Identifier: MIT */ /* Sample/example code blocks only (parsed-literal -> pre.literal-block; code-block / Doxygen @code -> div.highlight pre). Scoped to article content, so this never affects the left nav, right TOC, API signatures (.sig), or inline . On wide monitors the fluid content column would otherwise let sample lines sprawl the full width; cap them at a readable column and wrap long lines there instead of forcing a horizontal scrollbar. `100ch` is the one knob to tune. */ /* Cap the whole code box (the outer `.highlight` container for code-block/@code, or the standalone pre for parsed-literal) so the grey background sizes WITH the code -- capping only the inner 
 left the container's background sprawling past it. */
.bd-article div.highlight,
.bd-article pre.literal-block {
    max-width: 120ch;
}
/* Wrap long lines within that width, on the text element. */
.bd-article div.highlight pre,
.bd-article pre.literal-block {
    white-space: pre-wrap;
    overflow-wrap: break-word;
}

/* "Added in version X" note under each API/enum/struct name (emitted by
   api_spec.mako via `.. rst-class:: api-version`). Small and muted so it reads as
   metadata, not body text. */
.api-version {
    font-size: 0.8em;
    color: var(--pst-color-text-muted, #666);
    margin-top: 0.15rem;
    margin-bottom: 0.6rem;
}

/* "Introduced in Level Zero version X.Y" note under an extension doc page's title
   (emitted by generate_docs for EXT_*/EXT_Exp_* pages via `.. rst-class:: ext-version`). */
.ext-version {
    font-size: 0.85em;
    color: var(--pst-color-text-muted, #666);
    margin-top: 0.15rem;
    margin-bottom: 0.9rem;
}

/* "(since vX)" note appended to enum values added after their enum (injected into
   the final HTML by generate_docs._inject_etor_versions_html). Small + muted. */
.since-note {
    font-size: 0.85em;
    color: var(--pst-color-text-muted, #666);
    font-style: italic;
}

/* Make better use of wide displays -- responsively.
 *
 * The theme (pydata/sphinx_book_theme) traps the ENTIRE layout band
 * (left nav + content + right TOC) inside `.bd-page-width{max-width:88rem}`
 * (~1408px), centered with dead margins on either side. So raising only the
 * content column's cap does nothing on a wide screen -- the content is already
 * clipped by that outer band. The three rules below work together instead of
 * fighting that cap:
 *
 * All of this is gated by the theme's own min-width media queries: below
 * ~960px both sidebars collapse to overlay drawers, so none of this affects
 * phones/narrow windows. It only relaxes the desktop ceiling.
 */

/* 1. Let the layout band fill the window instead of stopping at 88rem. It
 *    already has width:100%, so uncapping makes it auto-track the viewport. */
.bd-page-width {
    max-width: 100%;
}

/* 2. Pin the left nav to a fixed width (theme default is 25%, which would just
 *    inflate the nav on wide screens). A fixed basis routes the extra window
 *    space to the CONTENT. Wide enough for the nested
 *    "API Docs -> 
 -> {APIs, Extensions, Experimental}" tree. */
.bd-sidebar-primary {
    flex-basis: 22rem;
}

/* 3. Content grows with the window up to a readable ceiling. Combined with the
 *    above, content width = viewport - nav - TOC - padding, capped here so long
 *    prose pages (PROG) don't stretch to unreadable line lengths on 4K. */
.bd-article-container {
    max-width: 120em;
}

/* Bottom paginator on paginated class pages ("< Prev  1 2 3  Next >").
   Emitted as a raw-HTML