/* Global search overlay */

body.search-overlay-open {
	overflow: hidden;
}

.search-overlay[hidden] {
	display: none;
}

.search-overlay {
	position: fixed;
	inset: 0;
	z-index: var( --z-overlay-backdrop );
	font-family: var( --font-ui );
}

/*
 * The backdrop is a real <button> so the overlay can be dismissed by click and
 * exposes an accessible name. That makes it inherit base.css's generic control
 * skin — including `button:hover { background-color: accent-dark }`, whose
 * (0,1,1) specificity beats a lone `.search-overlay__backdrop` (0,1,0) and
 * flashed the whole backdrop solid burgundy on hover/active. Stating every
 * interactive state on the class raises specificity to (0,2,0) and wins
 * without `!important`; the backdrop must stay a neutral scrim in all states.
 */
.search-overlay__backdrop,
.search-overlay__backdrop:hover,
.search-overlay__backdrop:focus,
.search-overlay__backdrop:focus-visible,
.search-overlay__backdrop:active {
	position: absolute;
	inset: 0;
	width: 100%;
	height: 100%;
	border: 0;
	border-radius: 0;
	background: rgba( 23, 23, 23, 0.42 );
	color: inherit;
	padding: 0;
	cursor: pointer;
}

/*
 * `type="search"` makes Chrome paint its own cancel button once the field has
 * a value, so a filled field showed TWO clear controls side by side: the blue
 * native glyph and our own `.search-overlay__clear`. The input keeps
 * type="search" (correct semantics, and it gives mobile keyboards a search
 * key) — only the platform decoration is suppressed. Same treatment for the
 * search-results page field, which has the same pairing.
 */
.search-overlay__input::-webkit-search-cancel-button,
.search-overlay__input::-webkit-search-decoration,
.search-overlay__input::-webkit-search-results-button,
.search-overlay__input::-webkit-search-results-decoration,
.search-page-form__input::-webkit-search-cancel-button,
.search-page-form__input::-webkit-search-decoration,
.search-page-form__input::-webkit-search-results-button,
.search-page-form__input::-webkit-search-results-decoration {
	-webkit-appearance: none;
	appearance: none;
	display: none;
}

.search-overlay__panel {
	position: relative;
	z-index: var( --z-overlay );
	max-height: 88vh;
	overflow-y: auto;
	background: var( --color-ivory );
	border-bottom: 1px solid var( --color-border );
	box-shadow: var( --shadow-dropdown );
	animation: aa-search-slide var( --t-slow ) var( --ease-out ) both;
}

.search-overlay__inner {
	width: min( 100%, 1120px );
	margin-inline: auto;
	padding: 26px 40px 34px;
}

.search-overlay__header,
.search-overlay__section-heading {
	display: flex;
	align-items: center;
	justify-content: space-between;
	gap: var( --sp-4 );
}

/* Back affordance is mobile-only; the desktop header keeps the labelled
   "Tutup ×" button. See the note in the overlay template. */
.search-overlay__back {
	display: none;
}

/* The submit button ships both glyphs. Desktop shows the labelled "Cari →";
   the compact magnifier is hidden here and swapped in by the mobile block.
   Without this the button rendered label + arrow + magnifier together. */
.search-overlay__submit-glyph--compact {
	display: none;
}

/* Section titles carry a small leading glyph (trending / history). */
.search-overlay__content-title {
	display: flex;
	align-items: center;
	gap: 7px;
}

.search-overlay__title-icon {
	color: var( --color-burgundy );
}

.search-overlay__header {
	margin-bottom: 18px;
}

.search-overlay__eyebrow,
.search-overlay__section-heading p {
	margin: 0;
	color: var( --color-warm-gray );
	font-size: var( --fs-xs );
	font-weight: var( --fw-bold );
	letter-spacing: 0.16em;
	text-transform: uppercase;
}

.search-overlay__close {
	display: inline-flex;
	align-items: center;
	gap: var( --sp-2 );
	min-height: 40px;
	padding: 0 12px 0 14px;
	border: 1px solid var( --color-border );
	border-radius: var( --radius-md );
	background: var( --color-paper );
	color: var( --color-warm-gray );
}

.search-overlay__close:hover {
	border-color: var( --color-burgundy );
	background: var( --color-paper );
	color: var( --color-burgundy );
}

.search-overlay__form {
	position: relative;
}

.search-overlay__field-icon {
	position: absolute;
	top: 50%;
	left: 20px;
	color: var( --color-warm-gray );
	transform: translateY( -50% );
	pointer-events: none;
}

.search-overlay__input {
	width: 100%;
	height: 70px;
	padding: 0 180px 0 54px;
	border: 1px solid var( --color-border );
	border-radius: var( --radius-field-lg );
	background: var( --color-paper );
	color: var( --color-ink );
	font-size: 21px;
}

.search-overlay__input:focus {
	border-color: var( --color-burgundy );
	outline: 0;
	box-shadow: 0 0 0 4px var( --focus-ring );
}

.search-overlay__clear {
	position: absolute;
	top: 50%;
	right: 112px;
	display: inline-flex;
	align-items: center;
	justify-content: center;
	width: 32px;
	height: 32px;
	padding: 0;
	border: 0;
	border-radius: 50%;
	background: var( --color-section-warm );
	color: var( --color-warm-gray );
	transform: translateY( -50% );
}

.search-overlay__clear:hover {
	background: var( --color-soft-burgundy );
	color: var( --color-burgundy );
}

.search-overlay__submit {
	position: absolute;
	top: 10px;
	right: 10px;
	display: inline-flex;
	align-items: center;
	justify-content: center;
	gap: 7px;
	min-width: 94px;
	height: 50px;
	padding: 0 18px;
	border: 0;
	border-radius: var( --radius-md );
	background: var( --color-burgundy );
	color: var( --color-paper );
	font-size: var( --fs-md );
	font-weight: var( --fw-semibold );
}

.search-overlay__filters {
	margin-top: 20px;
}

.search-overlay__chips,
.search-overlay__popular {
	display: flex;
	flex-wrap: wrap;
	gap: var( --sp-2 );
}

.search-overlay__chips {
	margin-top: 10px;
}

.search-chip,
.search-topic {
	display: inline-flex;
	align-items: center;
	gap: 6px;
	min-height: 36px;
	padding: 6px 12px;
	border: 1px solid var( --color-border );
	border-radius: 7px;
	background: var( --color-paper );
	color: var( --color-ink );
	font-size: var( --fs-sm );
	font-weight: var( --fw-semibold );
}

/*
 * Hover and selected were one shared declaration block, so a hovered chip was
 * pixel-identical to the selected one and you could not tell which filter was
 * actually applied. They are separate states now: hover is a border-only
 * emphasis that leaves the pill's own taxonomy tint intact, selection is the
 * filled treatment.
 */
.search-chip:hover {
	border-color: var( --color-burgundy );
}

/*
 * Unified selected treatment for every filter chip — "Semua" and every
 * taxonomy category alike: dark fill, white label, white check mark. Every
 * interactive state is stated on the rule so base.css's generic
 * `button:hover/:active` (0,1,1) cannot repaint it, and pressing a chip cannot
 * change its geometry — padding, border width and radius are untouched here.
 *
 * Qualified with the element type (`button.search-chip.is-active`, specificity
 * (0,2,1)) rather than left as a plain two-class rule (0,2,0): the per-category
 * taxonomy tint in visual-parity.css (`.search-chip.category-nasional {
 * background: cat-bg }`, also (0,2,0)) would otherwise tie with this rule, and
 * a tie is won by whichever file loads later — which is exactly why a selected
 * "Nasional" chip kept showing its pale unselected tint instead of the
 * selected treatment. The extra type selector wins regardless of file order.
 */
button.search-chip.is-active,
button.search-chip.is-active:hover,
button.search-chip.is-active:focus,
button.search-chip.is-active:focus-visible,
button.search-chip.is-active:active {
	border-color: var( --color-ink );
	background: var( --color-ink );
	color: var( --color-paper );
}

/*
 * There is exactly one `.search-chip__check` element in the whole document —
 * navigation.js moves it into whichever chip is active rather than templating
 * one per chip and toggling visibility, so it needs no visibility rule here,
 * only a fixed size so it can never inherit a different SVG scale from
 * wherever it lands.
 */
.search-chip__check {
	width: 14px;
	height: 14px;
	flex: 0 0 auto;
}

/* Unselected "Semua" must not inherit the taxonomy-tint hover either — it has
   no category colour of its own. */
.search-chip--all:not( .is-active ),
.search-chip--all:not( .is-active ):hover,
.search-chip--all:not( .is-active ):active {
	border-color: var( --color-border );
	background: var( --color-paper );
	color: var( --color-ink );
}

.search-chip--all:not( .is-active ):hover {
	border-color: var( --color-ink );
}

.search-topic {
	padding: 9px 14px;
	border-color: transparent;
	background: var( --color-section-warm );
	font-size: var( --fs-base );
}

.search-topic span {
	width: 6px;
	height: 6px;
	border-radius: 50%;
	background: currentColor;
}

/*
 * Both are real <button>s, so base.css's generic control skin applies to
 * them too — `button:hover { background-color: accent-dark }` at (0,1,1)
 * outranks the plain `.search-overlay__reset-filter` / `.search-overlay__
 * clear-history` class rule at (0,1,0), and because `:hover` also matches
 * while the pointer is held down, that generic rule painted a solid
 * burgundy rectangle behind these text-only actions on press. Same failure
 * family as `.search-overlay__backdrop` and `.search-overlay__recent-pick`
 * above — stating every interactive state on the class raises specificity
 * to (0,2,0) so it wins without `!important`. These stay compact text
 * actions: only the label colour shifts on hover/active, never a fill.
 */
.search-overlay__reset-filter,
.search-overlay__reset-filter:hover,
.search-overlay__reset-filter:focus,
.search-overlay__reset-filter:focus-visible,
.search-overlay__reset-filter:active,
.search-overlay__clear-history,
.search-overlay__clear-history:hover,
.search-overlay__clear-history:focus,
.search-overlay__clear-history:focus-visible,
.search-overlay__clear-history:active {
	padding: 4px;
	border: 0;
	background: transparent;
	color: var( --color-burgundy );
	font-size: var( --fs-sm );
}

.search-overlay__reset-filter:hover,
.search-overlay__reset-filter:active,
.search-overlay__clear-history:hover,
.search-overlay__clear-history:active {
	color: var( --color-burgundy-dark );
}

.search-overlay__content {
	margin-top: 28px;
}

.search-overlay__initial,
.search-overlay__suggestions {
	display: grid;
	grid-template-columns: minmax( 0, 1.25fr ) minmax( 280px, 1fr );
	gap: 44px;
}

/* The hidden attribute must actually hide these panels: the display:grid
   above otherwise overrides the [hidden] UA rule, so the initial popular
   panel bled through behind the loading / error / results views. Skeleton
   and error carry the same display:flex issue (see below) — same fix,
   same reason, listed here so the whole panel set stays together. */
.search-overlay__initial[hidden],
.search-overlay__suggestions[hidden],
.search-overlay__skeleton[hidden],
.search-overlay__error[hidden] {
	display: none;
}

.search-overlay__content-title {
	margin: 0 0 12px;
	color: var( --color-ink );
	font-family: var( --font-ui );
	font-size: var( --fs-sm );
	font-weight: var( --fw-bold );
	letter-spacing: 0.1em;
	text-transform: uppercase;
}

.search-overlay__recent-list,
.search-overlay__term-list,
.search-overlay__post-list {
	list-style: none;
	margin: 0;
	padding: 0;
}

.search-overlay__recent-item {
	display: grid;
	grid-template-columns: minmax( 0, 1fr ) 32px;
	gap: var( --sp-2 );
	align-items: center;
	border-bottom: 1px solid var( --color-border );
}

/*
 * Both controls are real <button>s, so base.css's generic control skin applies
 * to them — and `button:hover { background-color: accent-dark }` at (0,1,1)
 * outranks a lone `.search-overlay__recent-pick` at (0,1,0). Because the pick
 * is the full 1fr grid column, hovering anywhere on the row (403px at 1440)
 * flooded it solid burgundy while the label stayed ink — burgundy on ink,
 * unreadable, and it read as the whole recent-search column changing colour.
 *
 * Stating every interactive state on the class raises specificity to (0,2,0)
 * and wins without `!important`. The row itself never takes a fill; only the
 * compact 32px delete control does. Same failure family as the overlay
 * backdrop — see the note on .search-overlay__backdrop above.
 */
.search-overlay__recent-pick,
.search-overlay__recent-pick:hover,
.search-overlay__recent-pick:focus,
.search-overlay__recent-pick:focus-visible,
.search-overlay__recent-pick:active,
.search-overlay__recent-remove,
.search-overlay__recent-remove:focus {
	border: 0;
	background: transparent;
	color: var( --color-ink );
}

.search-overlay__recent-pick {
	display: flex;
	align-items: center;
	gap: 10px;
	min-height: 44px;
	padding: 10px 0;
	text-align: left;
	cursor: pointer;
	transition: color var( --t-fast, 140ms ) var( --ease-out, ease );
}

.search-overlay__recent-icon {
	color: var( --color-muted );
	flex: 0 0 auto;
}

.search-overlay__recent-label {
	min-width: 0;
	overflow: hidden;
	text-overflow: ellipsis;
	white-space: nowrap;
}

/* Affordance without a fill: the label itself takes the accent colour. */
.search-overlay__recent-pick:hover,
.search-overlay__recent-pick:focus-visible {
	color: var( --color-burgundy );
}

.search-overlay__recent-remove,
.search-overlay__recent-remove:focus {
	display: inline-flex;
	align-items: center;
	justify-content: center;
	width: 32px;
	height: 32px;
	padding: 0;
	border-radius: var( --radius-sm );
	color: var( --color-muted );
	cursor: pointer;
	transition:
		background-color var( --t-fast, 140ms ) var( --ease-out, ease ),
		color var( --t-fast, 140ms ) var( --ease-out, ease );
}

/* The one element allowed to fill — a compact square, never the row. Paper
   glyph on burgundy; the inherited muted grey would not have contrasted. */
.search-overlay__recent-remove:hover,
.search-overlay__recent-remove:focus-visible,
.search-overlay__recent-remove:active {
	background: var( --color-burgundy );
	color: var( --color-paper );
}

.search-overlay__status {
	padding: 4px 0 8px;
}

.search-overlay__status-message {
	margin: 0;
	padding: 26px 16px;
	text-align: center;
	color: var( --color-warm-gray );
	font-size: var( --fs-sm );
}

/* Loading: the shimmer skeleton is the visual; the localized status text
   stays in the role=status live region but visually hidden, so screen
   readers still hear "Mencari artikel..." without echoing the skeleton. */
.search-overlay__status.is-loading .search-overlay__status-message {
	position: absolute;
	width: 1px;
	height: 1px;
	padding: 0;
	overflow: hidden;
	clip: rect( 0 0 0 0 );
	white-space: nowrap;
	border: 0;
}

/* Loading skeleton -- mirrors the prototype "Cari - Loading" shimmer rows
   (Aspirasi Aktual.dc.html lines 168-178): three article placeholders, an
   88px 4:3 thumb and three text bars, with a moving highlight. */
.search-overlay__skeleton {
	display: flex;
	flex-direction: column;
	gap: 4px;
	margin-top: 26px;
}

.search-overlay__skeleton-row {
	display: grid;
	grid-template-columns: 88px 1fr;
	gap: 14px;
	padding: 10px 12px;
}

.search-overlay__skeleton-thumb {
	aspect-ratio: 4 / 3;
	border-radius: 4px;
}

.search-overlay__skeleton-lines {
	display: flex;
	flex-direction: column;
	gap: 10px;
	padding-top: 4px;
}

.search-overlay__skeleton-thumb,
.search-overlay__skeleton-bar {
	background: linear-gradient( 90deg, #E7E4DC 25%, #F1EEE7 50%, #E7E4DC 75% );
	background-size: 800px 100%;
	animation: aa-search-shimmer 1.2s linear infinite;
}

.search-overlay__skeleton-bar {
	border-radius: 3px;
}

.search-overlay__skeleton-bar--xs { height: 10px; width: 70px; }
.search-overlay__skeleton-bar--lg { height: 16px; width: 92%; }
.search-overlay__skeleton-bar--md { height: 12px; width: 55%; }

@keyframes aa-search-shimmer {
	0% { background-position: -400px 0; }
	100% { background-position: 400px 0; }
}

/* Error alert -- mirrors the prototype "Cari - Error" card
   (Aspirasi Aktual.dc.html lines 180-188): amber alert icon, serif title,
   muted copy, and a solid burgundy retry button. */
.search-overlay__error {
	display: flex;
	flex-direction: column;
	align-items: center;
	gap: 12px;
	padding: 40px 20px 16px;
	text-align: center;
}

/* The alert glyph now strokes with currentColor like the rest of the icon
   family, so its amber comes from the shared warning token rather than a
   hex literal baked into the markup. */
.search-overlay__error-icon {
	line-height: 0;
	color: var( --state-warning );
}

.search-overlay__error-title {
	margin: 0;
	font-family: var( --font-serif );
	font-size: 22px;
	font-weight: 700;
	color: var( --color-ink );
}

.search-overlay__error-text {
	margin: 0;
	font-size: 14px;
	color: var( --color-warm-gray );
}

.search-overlay__retry {
	display: inline-flex;
	align-items: center;
	gap: 8px;
	min-height: 44px;
	margin-top: 6px;
	padding: 11px 22px;
	border: none;
	border-radius: 8px;
	background: var( --color-burgundy );
	color: var( --color-paper );
	font-family: var( --font-ui );
	font-size: 13px;
	font-weight: 600;
	cursor: pointer;
}

.search-overlay__retry:hover {
	background: #741123;
}


.search-overlay__term-link {
	display: flex;
	align-items: center;
	justify-content: space-between;
	gap: var( --sp-3 );
	min-height: 44px;
	padding: 10px 12px;
	border-radius: var( --radius-md );
	text-decoration: none;
}

.search-overlay__term-link:hover,
.search-overlay__post-link:hover {
	background: var( --color-section-warm );
}

.search-overlay__term-kind {
	color: var( --color-burgundy );
	font-size: var( --fs-xs );
	font-weight: var( --fw-bold );
	letter-spacing: 0.08em;
	text-transform: uppercase;
}

.search-overlay__post-link {
	display: grid;
	grid-template-columns: 88px minmax( 0, 1fr );
	gap: 14px;
	align-items: center;
	padding: 10px 12px;
	border-radius: var( --radius-md );
	text-decoration: none;
}

.search-overlay__post-thumb {
	width: 88px;
	aspect-ratio: 4 / 3;
	overflow: hidden;
	background: var( --color-canvas-edge );
}

.search-overlay__post-thumb img {
	width: 100%;
	height: 100%;
	object-fit: cover;
}

.search-overlay__post-placeholder {
	display: grid;
	width: 100%;
	height: 100%;
	place-items: center;
	color: var( --color-muted );
	font-family: var( --font-masthead );
	font-weight: var( --fw-bold );
}

/*
 * inline-flex + align-self: start, not block. The slug-coloured backgrounds in
 * visual-parity.css apply to `.search-overlay__post-category.category-*`, so a
 * block-level label stretched that tint across the entire text column — a
 * 392px colour bar above every result instead of a narrow label. The colour
 * now ends where the word does.
 */
.search-overlay__post-category {
	display: inline-flex;
	align-self: flex-start;
	align-items: center;
	width: auto;
	max-width: 100%;
	margin-bottom: 4px;
	padding: 2px 7px;
	border-radius: var( --radius-sm );
	color: var( --color-burgundy );
	font-size: 10px;
	font-weight: var( --fw-bold );
	letter-spacing: 0.1em;
	text-transform: uppercase;
	white-space: nowrap;
}

.search-overlay__post-title {
	display: block;
	color: var( --color-ink );
	font-family: var( --font-serif );
	font-size: 15px;
	font-weight: var( --fw-bold );
	line-height: 1.3;
}

.search-overlay__post-date {
	display: block;
	margin-top: 3px;
	color: var( --color-warm-gray );
	font-size: var( --fs-xs );
}

.search-overlay__all-results {
	display: inline-flex;
	align-items: center;
	gap: var( --sp-2 );
	margin-top: 10px;
	padding: 6px 0;
	border: 0;
	background: transparent;
	color: var( --color-burgundy );
	font-size: var( --fs-md );
	font-weight: var( --fw-semibold );
}

.search-overlay__all-results:hover {
	background: transparent;
	color: var( --color-burgundy-dark );
}

@keyframes aa-search-slide {
	from {
		opacity: 0;
		transform: translateY( -18px );
	}
	to {
		opacity: 1;
		transform: translateY( 0 );
	}
}

@keyframes aa-search-spin {
	to {
		transform: rotate( 360deg );
	}
}

.search-overlay__keyboard-hint {
	display: flex;
	gap: 18px;
	align-items: center;
	margin-top: 24px;
	padding-top: 14px;
	border-top: 1px solid var(--color-border);
	font-size: 11px;
	color: var(--color-warm-gray);
}

.search-overlay__keyboard-hint strong {
	color: var(--color-ink-light, #6f6b65);
}

@media ( max-width: 767px ) {
	.search-overlay__panel {
		height: 100%;
		max-height: none;
	}

	.search-overlay__inner {
		padding: 18px 16px 28px;
	}

	/*
	 * The keyboard hints stay in the flow. They used to be `display: none`
	 * below 767px, which removed both the hints and the hairline that separates
	 * them from "Lihat semua hasil" — the divider the reference shows under the
	 * CTA. The panel scrolls internally (overflow-y: auto), so on a short screen
	 * they are reached by scrolling rather than deleted from the document.
	 */
	.search-overlay__keyboard-hint {
		flex-wrap: wrap;
		gap: 12px;
		margin-top: 20px;
	}

	/*
	 * Compact back header: arrow, then the section label, then a full-width
	 * rule. Replaces the detached 44px square close button, which read as a
	 * floating card control rather than a screen header. Both controls are the
	 * same dismiss action, so behaviour, focus return and Escape are unchanged.
	 * The rule is drawn on .search-overlay__inner's pseudo-free edge by using
	 * the header's own border, pulled out to the panel edges with negative
	 * margins so it spans the full width like the reference.
	 */
	.search-overlay__header {
		justify-content: flex-start;
		gap: 12px;
		margin: -18px -16px 16px;
		padding: 14px 16px;
		border-bottom: 1px solid var( --color-border );
	}

	.search-overlay__back {
		display: inline-flex;
		align-items: center;
		justify-content: center;
		width: 40px;
		height: 40px;
		margin-left: -8px;
		padding: 0;
		border: 0;
		border-radius: var( --radius-md );
		background: transparent;
		color: var( --color-ink );
		cursor: pointer;
	}

	.search-overlay__back:hover,
	.search-overlay__back:focus,
	.search-overlay__back:active {
		background: transparent;
		color: var( --color-burgundy );
	}

	.search-overlay__close {
		display: none;
	}

	/*
	 * Field: magnifier left, then the query, then a compact burgundy submit
	 * square inside the right edge. The clear control sits clear of the submit
	 * button (previously they abutted at 320/321px and were 18px out of
	 * vertical alignment); the input's right padding reserves room for both so
	 * a long query never runs under either.
	 */
	.search-overlay__input {
		height: 56px;
		padding: 0 96px 0 44px;
		font-size: var( --fs-lg );
	}

	.search-overlay__field-icon {
		left: 14px;
	}

	.search-overlay__submit {
		top: 50%;
		right: 6px;
		width: 44px;
		min-width: 44px;
		height: 44px;
		padding: 0;
		transform: translateY( -50% );
		border-radius: var( --radius-md );
	}

	.search-overlay__submit span,
	.search-overlay__submit-glyph--wide {
		display: none;
	}

	.search-overlay__submit-glyph--compact {
		display: block;
	}

	.search-overlay__clear {
		top: 50%;
		right: 58px;
		width: 32px;
		height: 32px;
		transform: translateY( -50% );
	}

	.search-overlay__filters {
		overflow: hidden;
	}

	/*
	 * The group label is hidden visually, not removed: .search-overlay__filters
	 * is aria-labelledby this element, so `display: none` would strip the
	 * filter group's accessible name. Reset on mobile is expressed by the
	 * "Semua" pill, so the redundant text control is dropped entirely.
	 */
	.search-overlay__filters .search-overlay__section-heading p {
		position: absolute;
		width: 1px;
		height: 1px;
		margin: -1px;
		padding: 0;
		overflow: hidden;
		clip: rect( 1px, 1px, 1px, 1px );
		clip-path: inset( 50% );
		white-space: nowrap;
	}

	.search-overlay__reset-filter {
		display: none;
	}

	.search-overlay__filters .search-overlay__section-heading {
		margin: 0;
	}

	.search-overlay__chips {
		margin-top: 0;
	}

	.search-chip {
		flex: 0 0 auto;
		min-height: 44px;
	}

	.search-overlay__content {
		margin-top: 22px;
	}

	.search-overlay__initial,
	.search-overlay__suggestions {
		grid-template-columns: minmax( 0, 1fr );
		gap: 24px;
	}

}

/*
 * Result list below the desktop shell breakpoint — one flat editorial list,
 * not a stack of rounded cards.
 *
 * Scoped to 1100px rather than 767px on purpose: the canonical mobile
 * reference is captured around 780px, and at 768px the list was still using
 * the desktop card treatment (8px radius, no divider, 88px thumbnail). This
 * band is the same one the rest of the shell switches at.
 *
 * `border-radius` combined with the hover fill was what made each row read as
 * an enclosing card; the divider is the only separator now. Inline gutters are
 * 0 so the thumbnail's left edge lines up with the "Artikel" heading, the
 * chips above it and the "Lihat semua hasil" CTA below. The thumbnail grows
 * while keeping its 4:3 ratio.
 */
@media ( max-width: 1100px ) {
	/* One column, so the result rows span the panel instead of being squeezed
	   into a ~400px half while the sibling column sits empty. Matches the flat
	   list band below; the two-column split stays a desktop composition. */
	.search-overlay__suggestions {
		grid-template-columns: minmax( 0, 1fr );
		gap: 24px;
	}

	/*
	 * Category and trending are single-row horizontal scrollers, not wrapping
	 * rows. Trending previously wrapped to two lines at every width below the
	 * desktop shell breakpoint, and the categories wrapped at 768.
	 *
	 * The scroll affordance is deliberately visible here. An earlier round hid
	 * the track; the newer mobile reference shows a scroll indicator under both
	 * rows, so a slim styled bar is restored — enough to signal "there is more
	 * to the right" without the platform's full-height rail. `scrollbar-width`
	 * covers Firefox; the ::-webkit rules size and colour it elsewhere. Above
	 * 1100px both rows fit, so nothing about the desktop layout changes.
	 */
	.search-overlay__chips,
	.search-overlay__popular {
		flex-wrap: nowrap;
		overflow-x: auto;
		overflow-y: hidden;
		padding-bottom: 8px;
		/* `scrollbar-width: thin` is deliberately NOT set: in Chrome it opts the
		   row into the overlay scrollbar, which takes no layout space and only
		   appears while scrolling — measured 0px, so the affordance the
		   reference shows was effectively invisible at rest. Leaving the
		   standard property at `auto` lets the ::-webkit rules below render a
		   persistent 4px rail. scrollbar-color still styles Firefox. */
		scrollbar-color: var( --color-muted ) var( --color-border );
		-webkit-overflow-scrolling: touch;
		overscroll-behavior-x: contain;
	}

	.search-overlay__chips::-webkit-scrollbar,
	.search-overlay__popular::-webkit-scrollbar {
		height: 4px;
	}

	.search-overlay__chips::-webkit-scrollbar-track,
	.search-overlay__popular::-webkit-scrollbar-track {
		background: var( --color-border );
		border-radius: 999px;
	}

	.search-overlay__chips::-webkit-scrollbar-thumb,
	.search-overlay__popular::-webkit-scrollbar-thumb {
		background: var( --color-muted );
		border-radius: 999px;
	}

	/* Chips must not shrink below their label, or the row stops scrolling and
	   the last category ends up clipped instead of reachable. */
	.search-chip,
	.search-topic {
		flex: 0 0 auto;
		white-space: nowrap;
	}

	.search-overlay__post-link,
	.search-overlay__term-link {
		border-radius: 0;
		padding-inline: 0;
	}

	.search-overlay__post-link {
		grid-template-columns: 96px minmax( 0, 1fr );
		gap: 14px;
		align-items: start;
		padding-block: 14px;
		border-bottom: 1px solid var( --color-border );
	}

	.search-overlay__post-list li:last-child .search-overlay__post-link {
		border-bottom: 0;
	}

	.search-overlay__post-thumb {
		width: 96px;
	}

	.search-overlay__post-title {
		font-size: 16px;
	}

	.search-overlay__all-results {
		margin-top: 14px;
		padding-inline: 0;
	}
}

@media ( prefers-reduced-motion: reduce ) {
	.search-overlay__panel,
	.search-overlay__skeleton-thumb,
	.search-overlay__skeleton-bar {
		animation: none;
	}
}