/**
 * OTA News Block widget styles.
 *
 * The "Latest news & resources" section: an eyebrow, a heading, a View all
 * button, one large featured card and a column of small article rows.
 *
 * Every colour is a colour theme role, mapped once in the token block below and
 * referenced by name after that, which is what lets the block follow whatever
 * theme is in force above it: its own, else the container's, else the page's,
 * else the site's. The one exception is the section's own background, which the
 * widget offers as a colour control and which overrides the surface role for the
 * section band alone: see `--onb-section-bg` below. The roles come from the
 * "News Block" component in the OTA design file, binding for binding:
 *
 *   section surface   bar/background     --ota-background
 *   eyebrow           bar/Ochre Button   --ota-ochre-button
 *   heading           bar/text           --ota-text
 *   View all button   .ota-btn--outline, which reads cta-bg / cta-text itself
 *   card surface      bar/background     --ota-background
 *   category badge    bar/Ochre Button   --ota-ochre-button
 *   badge label       bar/background     --ota-background
 *   card title        bar/text           --ota-text
 *   card rule         bar/Divider        --ota-divider
 *   card date         bar/White Text     --ota-white-text
 *   Read more         bar/text           --ota-text
 *   row eyebrow       bar/text-muted     --ota-text-muted
 *   row title         bar/text           --ota-text
 *   row date          bar/text-muted     --ota-text-muted
 *
 * Three of those are a departure, and all three are the same departure: the
 * Figma layer holds a raw hex rather than a bound variable. "Read more" and both
 * row titles are #003038, which is what bar/text resolves to in the frame's own
 * mode, and the row date is #5A6B6E, a grey that is in no theme and in no
 * palette. Binding them to the role the neighbouring bound layers use is the
 * only reading that survives a theme change; left as hexes they would go
 * invisible on Navy and Teal.
 *
 * `white-text` is not literally white. It is the role for text that reads on
 * this theme's background, so it resolves navy on the light themes and white on
 * the dark ones.
 *
 * THE FEATURED CARD IS A SECOND THEME, ON PURPOSE
 *
 * The design frame is two variable modes, not one. Its outer section and its
 * small rows resolve bar/background to white, and the featured card resolves the
 * same variable to #F0E7D8: a White section with an Ash card inside it. That is
 * exactly what a nested theme class does here, so the widget offers a "Featured
 * card theme" of its own and the token block below is declared on both `.ota-news`
 * and `.ota-news__feature`.
 *
 * The duplication is load bearing rather than untidy. A custom property whose
 * value contains `var()` is resolved on the element that declares it, so tokens
 * declared once on `.ota-news` would inherit into the card already resolved
 * against the section's theme and the card's own class would do nothing. Naming
 * the card in the same rule makes it resolve them again, against its own theme.
 *
 * Typography comes from the Elementor global fonts, each as a `var()` with the
 * Figma number as its fallback, so the block still renders to spec on a site
 * whose kit has not had the type scale imported. Label/Eyebrow for the eyebrow,
 * Heading/H2 for the heading, Heading/H3 for the featured title, Body/Default
 * for the featured date, Body/Caption for both small eyebrows and Body/Small for
 * the row date.
 *
 * Four weights are stated rather than read from a global, because the scale has
 * no cut for them: the two category eyebrows and both card titles are Bold at
 * sizes the scale only publishes Light or Regular. The sizes still come from the
 * globals; only `font-weight` is local. Same for the row date, where Figma draws
 * 14px and Body/Small is 15px: the global wins where the kit has one and 0.875rem
 * is the fallback, since a 1px difference is not worth a tenth style.
 *
 * The badge and row eyebrow tracking is in `em` rather than the design's px, so
 * it tracks the size through the responsive steps. 0.6912/11.52 and 0.96/12 are
 * the design's own ratios.
 */

/*
 * The roles. Ash values as fallbacks, so the block is never unstyled on a site
 * with no colour theme configured. Declared for the card as well as the section:
 * see the note on the featured card above.
 */
.ota-news,
.ota-news__feature {
	--onb-surface: var(--ota-background, #f0e7d8);
	--onb-text: var(--ota-text, #003038);
	--onb-muted: var(--ota-text-muted, #005361);
	/*
	 * The ochre pill, and the one binding worth flagging. On the Ochre theme
	 * `ochre-button` and `background` resolve to the same colour, so the badge
	 * would be an ochre pill with ochre text on an ochre card and disappear
	 * entirely. The design binds both, so both are kept, and this is the one
	 * line to change if that combination ever ships: `--ota-accent` and
	 * `--ota-logo` are the two roles that flip away from the background on
	 * every theme.
	 */
	--onb-accent: var(--ota-ochre-button, #f04c3a);
	--onb-badge-text: var(--ota-background, #f0e7d8);
	--onb-divider: var(--ota-divider, rgba(0, 48, 56, 0.2));
	--onb-date: var(--ota-white-text, #003038);
}

.ota-news {
	/*
	 * The design's own container: 1280px of content inside a 1440px artboard.
	 * Narrower than the header's 1440, which is deliberate and is what the
	 * frame draws.
	 */
	--onb-max: 1280px;
	--onb-pad: 2rem;
	/*
	 * No --onb-gap here, deliberately. The two layouts have different design
	 * gaps (12px featured, 39/24px cards), and a value declared at this shared
	 * scope would defeat every per-layout `var(--onb-gap, <default>)` fallback
	 * below: a var() fallback only applies when the property is UNSET, not when
	 * it is set to another value. So the token exists only when the Gap slider
	 * writes it, and each consumer carries its own layout's default. Raised in
	 * review on PR #8, third round.
	 */
	--onb-radius: 14px;
	--onb-media-h: 390px;
	--onb-thumb: 118px;
	--onb-ring: 2px;

	padding-block: 96px;
	/*
	 * The section band only. Unset, which is how it ships, this is the surface
	 * role and the block is entirely theme driven as before. The widget's
	 * Background control writes `--onb-section-bg` here, and it is deliberately
	 * a separate token rather than an override of `--onb-surface`: the cards
	 * read the surface role, so overriding it would repaint them to match the
	 * band and flatten the design's card-on-section reading. An editor who wants
	 * the cards to move too has the Colour Theme control for that.
	 */
	background-color: var(--onb-section-bg, var(--onb-surface));
	color: var(--onb-text);
}

.ota-news__inner {
	box-sizing: border-box;
	display: flex;
	flex-direction: column;
	gap: 48px;
	width: 100%;
	max-width: var(--onb-max);
	margin-inline: auto;
	padding-inline: var(--onb-pad);
}

/* --- Header -------------------------------------------------------------- */

.ota-news__head {
	display: flex;
	flex-wrap: wrap;
	align-items: center;
	justify-content: space-between;
	gap: 24px;
}

.ota-news__intro {
	display: flex;
	flex-direction: column;
	gap: 8px;
}

/*
 * Only when there is a subheading: the intro takes the room left after the
 * button, so the copy spans to it. The basis is 0, not auto: with auto the
 * intro's basis is its own content width, a long subheading fills the line and
 * the wrapping header drops the button underneath. From 0 it grows into
 * whatever the button leaves.
 *
 * Scoped by the template's modifier rather than set on every intro, because a
 * basis of 0 also means the intro can never push the button to a second line,
 * and a block with no subheading relies on exactly that between 600px and
 * about 1024px, where a long heading beside the button would otherwise be
 * squeezed to a word a line. Those blocks keep the wrap they shipped with.
 */
.ota-news__head--has-subheading .ota-news__intro {
	flex: 1 1 0;
	min-width: 0;
}

.ota-news__eyebrow {
	margin: 0;
	color: var(--onb-accent);
	font-size: var(--e-global-typography-eyebrow-font-size, 1.0625rem);
	font-weight: var(--e-global-typography-eyebrow-font-weight, 700);
	line-height: var(--e-global-typography-eyebrow-line-height, 1.46em);
	letter-spacing: var(--e-global-typography-eyebrow-letter-spacing, 1px);
}

.ota-news__title {
	margin: 0;
	color: var(--onb-text);
	font-size: var(--e-global-typography-h2-font-size, 2.75rem);
	font-weight: var(--e-global-typography-h2-font-weight, 400);
	line-height: var(--e-global-typography-h2-line-height, 1.08em);
	letter-spacing: var(--e-global-typography-h2-letter-spacing, -0.44px);
}

/*
 * The optional line under the heading (Teamwork 49523897): Body, in the
 * block's text role. It runs the width of the header up to the button, which
 * is what the intro's flex: 1 below is for; Bryce asked for the span rather
 * than a fixed reading measure (17 Sep). The 8px the intro already puts
 * between its children is too tight after a 44px heading, so it takes a
 * little more above.
 */
.ota-news__subheading {
	margin: 4px 0 0;
	color: var(--onb-text);
	font-size: var(--e-global-typography-body-font-size, 1.0625rem);
	font-weight: var(--e-global-typography-body-font-weight, 400);
	line-height: var(--e-global-typography-body-line-height, 1.5em);
}

/* Air before the button beyond the header's 24px gap, so the copy does not
   read as running into it (Bryce's eye, 17 Sep). Keyed to the button being
   there (the template's modifier), not to the width alone: a block with a
   subheading and no View all link would otherwise carry 64px of dead space.
   Taken off again inside the 600px stack below, where the button is under the
   copy and the width is all the copy's; the same query as the stack, so no
   fractional width between two breakpoints matches neither. */
.ota-news__head--has-button .ota-news__subheading {
	padding-inline-end: 64px;
}

/* --- Grid ---------------------------------------------------------------- */

/*
 * Two equal columns. The design draws 633 + 12 + 633 against a 1280 container,
 * which is `1fr 1fr` with the gap taken out of the middle.
 *
 * Left to stretch rather than aligned to the start, so the two columns end on
 * the same line whichever is taller: the rows distribute into a taller featured
 * card, and a taller stack of rows is absorbed by the card's body instead.
 */
.ota-news__grid {
	display: grid;
	grid-template-columns: 1fr 1fr;
	gap: var(--onb-gap, 12px);
}

/* Only one of the two sides has anything in it: the featured card is switched
   off, or the query returned just enough for the card and nothing for the rows.
   See the note in templates/widgets/news-block.php. */
.ota-news__grid--single {
	grid-template-columns: 1fr;
}

/* --- Featured card ------------------------------------------------------- */

.ota-news__feature {
	position: relative;
	display: flex;
	flex-direction: column;
	overflow: hidden;
	border-radius: var(--onb-radius);
	background-color: var(--onb-surface);
	color: var(--onb-text);
	text-decoration: none;
}

.ota-news__feature:hover,
.ota-news__feature:focus {
	text-decoration: none;
}

/*
 * The hover ring, drawn by the card-large component's Hover variant: a 2px
 * bar/text border inside the card's own radius, over the photograph rather than
 * around it.
 *
 * A pseudo-element rather than a real border, for three reasons that all point
 * the same way. A border on the card itself would resize it on hover and shift
 * the row beside it; an `outline` with a negative offset draws square corners on
 * a Safari older than 16.4, against a 14px radius that is the whole shape of the
 * card; and an inset `box-shadow` paints on the card's own background layer,
 * which puts it under the featured image and erases the top half of the ring.
 * A positioned pseudo-element paints above the image, costs no layout, and
 * inherits the radius whatever the Corner Radius control is set to.
 *
 * Always present and transparent, so only the colour changes on hover and there
 * is something for the transition to run against.
 */
.ota-news__feature::after {
	content: "";
	position: absolute;
	z-index: 1;
	inset: 0;
	border: var(--onb-ring) solid transparent;
	border-radius: inherit;
	pointer-events: none;
	transition: border-color 150ms ease;
}

.ota-news__feature:hover::after {
	border-color: var(--onb-text);
}

.ota-news__feature:hover .ota-news__feature-title {
	text-decoration: underline;
}

/*
 * A fixed height rather than an aspect ratio: the design pins 390px and the card
 * beside a column of rows wants a predictable top edge more than it wants to
 * track its column's width. The divider tint stands in when a post has no
 * featured image, so the badge always has something to sit on.
 */
.ota-news__feature-media {
	position: relative;
	display: block;
	height: var(--onb-media-h);
	background-color: var(--onb-divider);
}

/*
 * Two classes, not for style but for specificity. Elementor ships
 * `.elementor img { height: auto; max-width: 100% }` at (0,1,1), which beats a
 * lone class: `height: auto` would collapse the box to the image's intrinsic
 * size. Same trap as the one fixed on the category feature and the hero.
 */
.ota-news .ota-news__feature-image {
	display: block;
	width: 100%;
	max-width: none;
	height: 100%;
	object-fit: cover;
}

.ota-news__badge {
	position: absolute;
	top: 28px;
	left: 34px;
	display: inline-flex;
	align-items: center;
	padding: 4px 12px;
	border-radius: 999px;
	background-color: var(--onb-accent);
	color: var(--onb-badge-text);
	font-size: var(--e-global-typography-caption-font-size, 0.75rem);
	font-weight: 700;
	line-height: 1.65em;
	letter-spacing: 0.06em;
	text-transform: uppercase;
}

.ota-news__feature-body {
	display: flex;
	flex: 1 1 auto;
	flex-direction: column;
	gap: 27px;
	padding: 32px;
}

.ota-news__feature-title {
	margin: 0;
	color: var(--onb-text);
	font-size: var(--e-global-typography-h3-font-size, 2rem);
	font-weight: var(--e-global-typography-h3-font-weight, 400);
	line-height: var(--e-global-typography-h3-line-height, 1.08125em);
	letter-spacing: var(--e-global-typography-h3-letter-spacing, -0.32px);
}

/*
 * Pushed to the bottom of the body rather than following the title, so the rule
 * and the date land on the card's lower edge whatever the headline runs to. The
 * design's fixed 581px card has the same effect without having to say so.
 */
.ota-news__feature-meta {
	display: flex;
	align-items: center;
	justify-content: space-between;
	gap: 10px;
	margin-block-start: auto;
	padding-block: 8px;
	border-block-start: 1px solid var(--onb-divider);
}

.ota-news__feature-date {
	color: var(--onb-date);
	font-size: var(--e-global-typography-body-font-size, 1.0625rem);
	font-weight: var(--e-global-typography-body-font-weight, 300);
	line-height: var(--e-global-typography-body-line-height, 1.65em);
}

/*
 * Not a link. The whole card is the anchor, so a second one here would be a
 * nested link, and a screen reader would announce two destinations for one
 * card. It is an affordance, which is why it underlines on the card's hover
 * rather than on its own.
 */
.ota-news__more {
	display: inline-flex;
	align-items: center;
	gap: 10px;
	color: var(--onb-text);
	font-size: var(--e-global-typography-body-font-size, 1.0625rem);
	font-weight: 700;
	line-height: 1;
}

.ota-news__more svg {
	flex: none;
	display: block;
	width: 13px;
	height: 13px;
}

.ota-news__feature:hover .ota-news__more {
	text-decoration: underline;
}

/* --- Article rows -------------------------------------------------------- */

/*
 * Spread rather than stacked, so the column ends level with the featured card
 * beside it. With four rows against the design's 581px card that is the 27px of
 * slack the frame distributes by hand.
 */
.ota-news__list {
	display: flex;
	flex-direction: column;
	justify-content: space-between;
}

.ota-news__item {
	display: flex;
	align-items: center;
	gap: 16px;
	padding: 16px;
	border-radius: var(--onb-radius);
	background-color: var(--onb-surface);
	color: var(--onb-text);
	text-decoration: none;
}

.ota-news__item:hover,
.ota-news__item:focus {
	text-decoration: none;
}

.ota-news__item-media {
	flex: 0 0 auto;
	overflow: hidden;
	width: var(--onb-thumb);
	height: var(--onb-thumb);
	border-radius: var(--onb-radius);
	background-color: var(--onb-divider);
}

.ota-news .ota-news__item-image {
	display: block;
	width: 100%;
	max-width: none;
	height: 100%;
	object-fit: cover;
}

/* `min-width: 0` so a long unbroken headline wraps instead of pushing the row
   wider than its column. */
.ota-news__item-body {
	display: flex;
	flex-direction: column;
	gap: 9px;
	min-width: 0;
}

.ota-news__item-eyebrow {
	color: var(--onb-muted);
	font-size: var(--e-global-typography-caption-font-size, 0.75rem);
	font-weight: 700;
	line-height: 1.65em;
	letter-spacing: 0.08em;
	text-transform: uppercase;
}

.ota-news__item-title {
	margin: 0;
	color: var(--onb-text);
	font-size: var(--e-global-typography-body-font-size, 1.0625rem);
	font-weight: 700;
	line-height: 1.2;
}

.ota-news__item:hover .ota-news__item-title {
	text-decoration: underline;
}

.ota-news__item-meta {
	display: inline-flex;
	align-items: center;
	gap: 10px;
	color: var(--onb-muted);
	font-size: var(--e-global-typography-small-font-size, 0.875rem);
	font-weight: var(--e-global-typography-small-font-weight, 300);
	line-height: 1.65em;
}

.ota-news__item-meta svg {
	flex: none;
	display: block;
	width: 15px;
	height: 15px;
}

/* --- Focus --------------------------------------------------------------- */

/*
 * On the card, not on anything inside it. The whole card is the anchor, so the
 * ring has to describe the whole card or it points at the wrong target.
 */
.ota-news__feature:focus-visible,
.ota-news__item:focus-visible {
	outline: 2px solid var(--onb-text);
	outline-offset: 3px;
}

/* --- Narrow -------------------------------------------------------------- */

/*
 * No mobile frame was drawn for this block, so everything below is an
 * extrapolation from the desktop one and from the breakpoints the hero and the
 * mega menu already use. Worth designing properly before client sign-off.
 *
 * One column, and the featured card's media loses height with it: at half the
 * width it no longer needs 390px to hold its shape, and a full-width 390px
 * photograph pushes the rows a screen down.
 */
@media (max-width: 1024px) {
	.ota-news {
		--onb-pad: 1.1875rem;
		--onb-media-h: 260px;

		padding-block: 64px;
	}

	.ota-news__inner {
		gap: 32px;
	}

	.ota-news__grid {
		grid-template-columns: 1fr;
	}

	/* Nothing left to spread against, so the rows sit together and the padding
	   inside each one is the only gap they need. */
	.ota-news__list {
		justify-content: flex-start;
	}
}

@media (max-width: 600px) {
	.ota-news {
		--onb-thumb: 88px;
	}

	/* The button goes under the heading rather than beside it: at this width
	   the two share a line only by squeezing the heading to a word a line. */
	.ota-news__head {
		flex-direction: column;
		align-items: flex-start;
	}

	.ota-news__head--has-button .ota-news__subheading {
		padding-inline-end: 0;
	}

	.ota-news__badge {
		top: 16px;
		left: 16px;
	}

	.ota-news__feature-body {
		gap: 20px;
		padding: 24px;
	}

	.ota-news__item {
		gap: 12px;
		padding: 12px;
	}
}

/*
 * THE CARDS ROW, the homepage design: Layout/News 359:13589. Equal cards side
 * by side, no featured slot and no article rows. Same section head above it.
 *
 * The token redeclaration on `.ota-news__card` is the featured card's trick for
 * the featured card's reason: the design draws white cards on a sand section,
 * a nested theme, and custom properties resolve where they are declared. The
 * pill is bound to cta-bg/cta-text where the featured card's is ochre-button:
 * that is the design's own binding on this frame, not a restyle.
 *
 * The design's fixed 372px card is expressed as a pinned footer instead: the
 * body is a column whose footer takes margin-top auto, so every footer in a row
 * lands on the same lower edge whatever the headlines run to, which is all the
 * fixed height was doing.
 */
/* Gap through the Layout section's slider like every other measurement in this
   file, with the design's 39px as the fallback. It was hardcoded, so the slider
   an editor could see and move did nothing on this layout. */
.ota-news__cards {
	display: grid;
	grid-template-columns: repeat(3, 1fr);
	gap: var(--onb-gap, 39px);
}

.ota-news__card {
	--onb-surface: var(--ota-background, #ffffff);
	--onb-text: var(--ota-text, #003038);
	--onb-title: var(--ota-white-text, #003038);
	--onb-rule: var(--ota-divider, rgba(0, 48, 56, 0.2));
	--onb-pill: var(--ota-cta-bg, #003038);
	--onb-on-pill: var(--ota-cta-text, #ffffff);

	/*
	 * The hover ring, from the card's own hover variant (Component/News
	 * 359:13125): a 2px stroke that the frame binds to text-muted, unlike the
	 * events card's ring, which the design leaves as a raw hex.
	 *
	 * `--onb-card-ring` and not `--onb-ring`, which is the ring's WIDTH up on
	 * `.ota-news` (line 113) and is consumed as one in `border: var(--onb-ring)
	 * solid transparent`. The two scopes never met, so nothing broke, but one
	 * property name meaning a length in one part of this file and a colour in
	 * another is a trap for whoever next hoists a declaration or copies the
	 * featured card's border shorthand onto a card. Raised in review on PR #8,
	 * second round.
	 */
	--onb-card-ring: var(--ota-text-muted, #005361);

	position: relative;
	display: flex;
	flex-direction: column;
	overflow: hidden;
	border-radius: var(--onb-radius);
	background: var(--onb-surface);
	color: var(--onb-title);
	text-decoration: none;
}

/*
 * The ring is a transparent pseudo-element rather than a real border, for the
 * events card's three reasons: a real border resizes the card and shifts the
 * row, an inset shadow paints under the image, and a pseudo-element can follow
 * the card's own radius with `inherit`.
 */
.ota-news__card::after {
	content: '';
	position: absolute;
	inset: 0;
	border: 2px solid transparent;
	border-radius: inherit;
	pointer-events: none;
	transition: border-color 150ms ease;
}

.ota-news__card:hover::after,
.ota-news__card:focus-visible::after {
	border-color: var(--onb-card-ring);
}

.ota-news__card:hover .ota-news__card-title,
.ota-news__card:focus-visible .ota-news__card-title {
	text-decoration: underline;
}

/*
 * A fixed height rather than an aspect ratio, for the featured card's reason: a
 * row of cards wants one shared top edge for its titles. The design pins 170px.
 * The divider tint stands in when a post has no featured image, so the pill
 * always has something to sit on.
 */
.ota-news__card-media {
	position: relative;
	display: block;
	height: var(--onb-card-media-h, 170px);
	flex-shrink: 0;
	background: var(--onb-rule);
}

/* The class is named as well as the element so the card image carries its own
   rule rather than borrowing the article row's, which is what it did before it
   had a class of its own. `max-width: none` for the same reason the row image
   sets it: the theme caps every img at 100% of its box, and the fill here is
   the absolutely positioned box. */
.ota-news__card-media img,
.ota-news .ota-news__card-image {
	position: absolute;
	inset: 0;
	width: 100%;
	max-width: none;
	height: 100%;
	object-fit: cover;
}

.ota-news__card-tag {
	position: absolute;
	top: 24px;
	right: 24px;
	padding: 6px 16px;
	border-radius: 999px;
	background: var(--onb-pill);
	color: var(--onb-on-pill);
	font-size: 11.5px;
	font-weight: 700;
	line-height: 1.65;
	letter-spacing: 0.69px;
	text-transform: capitalize;
}

.ota-news__card-body {
	display: flex;
	flex-direction: column;
	flex-grow: 1;

	/*
	 * The design's 372px card minus its 170px media: the space between the
	 * title and the footer rule is the leftover, and without this a row of
	 * one-line titles collapses that space to nothing, because the footer's
	 * margin-top auto has nothing to push against. The min rather than a
	 * height, so a long headline still grows the card instead of overflowing.
	 */
	min-height: 202px;
	padding: 24px 24px 8px;
}

.ota-news__card-title {
	/*
	 * The floor under the title-to-rule gap for headlines long enough to eat
	 * the body's spare height.
	 */
	margin: 0 0 24px;
	color: var(--onb-title);
	font-size: var(--e-global-typography-h4-font-size, 22px);
	font-weight: var(--e-global-typography-h4-font-weight, 400);
	line-height: var(--e-global-typography-h4-line-height, 1.4);
	letter-spacing: var(--e-global-typography-h4-letter-spacing, 0);
}

/*
 * Pushed to the bottom of the body rather than following the title, so the rule
 * and the date land on the card's lower edge whatever the headline runs to.
 */
.ota-news__card-footer {
	display: flex;
	align-items: center;
	justify-content: space-between;
	gap: 10px;
	margin-top: auto;
	padding: 8px 0;
	border-top: 1px solid var(--onb-rule);
}

.ota-news__card-date {
	color: var(--onb-title);
	font-size: var(--e-global-typography-small-font-size, 15px);
	font-weight: var(--e-global-typography-small-font-weight, 300);
	line-height: var(--e-global-typography-small-line-height, 1.65);
}

.ota-news__card-more {
	display: inline-flex;
	align-items: center;
	gap: 10px;
	padding: 15.5px 0;
	color: var(--onb-text);
	font-size: 17px;
	font-weight: 700;
	line-height: 1;
	white-space: nowrap;
}

/*
 * The arrow's dot, copied from the events card at Bryce's ask (the frame draws
 * a bare arrow; the site draws one Read More affordance everywhere). Card
 * coloured at rest, which is the design's way of saying invisible, and it
 * fills with the CTA colours on hover. Sized and centred at rest as well as on
 * hover so the fill does not move the arrow.
 */
.ota-news__card-dot {
	display: inline-flex;
	flex: none;
	align-items: center;
	justify-content: center;
	width: 30px;
	height: 30px;
	border-radius: 999px;
	background-color: var(--onb-surface);
	color: var(--onb-text);
	transition:
		background-color 150ms ease,
		color 150ms ease;
}

.ota-news__card:hover .ota-news__card-dot,
.ota-news__card:focus-visible .ota-news__card-dot {
	background-color: var(--onb-pill);
	color: var(--onb-on-pill);
}

.ota-news__card-dot svg {
	flex: none;
	display: block;
	width: 13px;
	height: 13px;
}

@media (max-width: 1024px) {
	.ota-news__cards {
		grid-template-columns: repeat(2, 1fr);
		gap: var(--onb-gap, 24px);
	}
}

@media (max-width: 600px) {
	.ota-news__cards {
		grid-template-columns: 1fr;
	}
}

/*
 * The rule that hides an empty block's section is in ota-block-empty.css, one
 * copy shared with the events block. This widget declares that handle in
 * `get_style_depends()` alongside this file.
 */
