/*
 * Responsive oEmbed video — new path on purpose (2026-08-24).
 *
 * WordPress stores a YouTube oEmbed as raw <iframe width="1200" height="675">
 * in the post body, so on a game page the walkthrough video was 1200px wide
 * inside an 890px column — and 1200px inside a 336px column on a phone, where
 * it covered the text to its right and ran 860px past the edge of the screen.
 * The theme's own `.ra-video-embed` wrapper is only used by the template that
 * renders a video field; an oEmbed pasted into the description never gets it.
 *
 * This lives in its own file rather than at the end of frontend.css because
 * LiteSpeed derives a minified sheet's hashed URL from the source *path* and
 * serves it max-age=1yr: an edit inside frontend.css can take a year to reach a
 * returning visitor, while a new path is fetched by everyone at once. Same
 * reasoning as tokens.css / play-cover.css above it.
 */
.entry-content iframe,
.rg-description-content iframe,
.ra-game-description iframe {
    display: block;
    width: 100%;
    max-width: 100%;
    height: auto;
    aspect-ratio: 16 / 9;
    margin-inline: auto;
    border: 0;
}

/* A video is a block, not a word: the paragraph WordPress wraps it in should
   not add its own indent or leave the iframe sitting on the text baseline. */
.entry-content p:has(> iframe),
.rg-description-content p:has(> iframe) {
    margin: 14px 0;
    line-height: 0;
}