/*
 * Rules that no bundler is allowed to parse.
 *
 * `details::details-content` is a real pseudo-element (Chrome 131+) and this
 * animation worked in the browser. But the Turbopack CSS parser in Next 15.0.5
 * does not recognise it and treats it as a PARSE ERROR, which fails the whole
 * stylesheet — so with these two rules in app/globals.css, `next dev --turbo`
 * answered 500 on every route. Production (webpack) was lenient, so the live
 * site never showed it and the breakage looked like "the dev server is down".
 *
 * Served from public/ and linked directly, this file reaches the browser
 * verbatim. Browsers ignore selectors they do not understand, which is the
 * behaviour that was wanted all along.
 *
 * Move these back into globals.css once Next is new enough to parse them, and
 * delete this file with its <link> in app/layout.tsx.
 */
@supports (interpolate-size: allow-keywords) {
  details::details-content {
    height: 0;
    overflow: clip;
    transition: height 0.3s var(--cd-ease), content-visibility 0.3s allow-discrete;
  }
  details[open]::details-content {
    height: auto;
  }
}