/**
 * The published-alerts register.
 *
 * Loaded only for `template-alerts.php` — the arrangement `home.css` and
 * `warning-signs.css` both have, and for the same reason: three bands' worth of
 * rules that exactly one URL can reach do not belong in a stylesheet every
 * visitor downloads.
 *
 * **It loads after `lc-components.css`**, declared in `functions.php` as a
 * dependency on `lieferantencheck-components` rather than on
 * `lieferantencheck-theme`. That used to be load-bearing here: the four rules
 * re-laying the plugin's lookup for a 22.5rem rail tie on specificity with the
 * component sheet's own at (0,2,0), and source order was the whole margin. They
 * moved *into* that sheet at 1.12.0, when `/domains/` became the second page
 * with a lookup in its rail. Nothing in this file ties today, so the dependency
 * is now the precaution every page sheet declares — one order for all five, so
 * the first rule here that does need it works instead of silently not.
 *
 * **Everything below the hero is paper in both colour schemes, and not one
 * declaration in this file says so.** The template carries `.lc-onpaper` on its
 * `<main>` and `.lc-onimage` on the hero inside it; both are token re-points in
 * `style.css`, and a custom property declared on a nearer ancestor wins for its
 * own subtree. Every rule here names a semantic token, so the page comes out
 * navy-then-paper in either scheme with no `@media (prefers-color-scheme)`
 * anywhere — which is the point, because a media query is a branch the light
 * side silently depends on being written correctly. Section 17 of
 * `tools/test-theme-contrast.php` measures every pair through the pin and fails
 * if a scheme branch appears here.
 *
 * @package LieferantenCheck
 */

/* ==========================================================================
   1. The root
   ========================================================================== */

/*
 * The page grid, not the reading grid.
 *
 * `style.css` narrows `.lc-page`, `.lc-single`, `.lc-archive` and `.lc-404` to
 * `--lc-shell-read`. This page is bands — a hero, a full-bleed strip, a register
 * beside a rail — and it wants the full shell for the same reason `.lc-home` and
 * `.lc-guide` do. There is deliberately no rule here narrowing it; `.lc-shell`
 * already defaults to `--lc-shell`.
 *
 * Section 7 of the contrast harness derives its list of template roots from the
 * theme's own PHP so a *new* `<main>` cannot open at the old left-heavy grid
 * unremarked, and it has to be told about this one by name.
 */
.lc-register-page {
	display: block;
}

/* ==========================================================================
   2. Hero
   ========================================================================== */

/*
 * Two numbers, declared on `.lc-reghero` rather than on the `--image` modifier,
 * so the grid rule below can never resolve `--lc-reg-split` to nothing: an
 * unresolved `var()` is invalid at computed-value time and would drop the whole
 * `grid-template-columns` declaration rather than fall back to the one-column
 * rule above it.
 *
 * The same derivation `.lc-hero` and `.lc-guide-hero` use, restated because
 * neither of those sheets is loaded here and a custom property cannot be
 * inherited from a stylesheet that is not present. Section 17 pins this copy to
 * the same *shape*, which is what stops it drifting into the bug 1.4.6 fixed.
 */
.lc-reghero {
	--lc-reg-gap: 2.5rem;
	--lc-reg-split: calc(4 / 7);

	padding-block: clamp(2.75rem, 6vw, 4.25rem);
	background: var(--lc-ink);
}

/*
 * **Nothing is ever read on top of the photograph**, at any width. Below 62rem
 * the plate is not rendered at all, so the headline sits on flat `--lc-ink` and
 * the contrast argument is arithmetic that no photograph can move: white
 * 17.0:1, the soft token 12.8:1, the gold eyebrow 6.6:1.
 */
.lc-reghero__bg {
	position: absolute;
	inset: 0;
	display: none;
	overflow: hidden;
}

/*
 * `brightness(0.72)`, between the homepage plate's 0.58 and the checklist's
 * 0.86, and read off this photograph rather than copied from either.
 *
 * `Containerhafen` is a lit dockside at dusk: brighter overall than `Betonwand`
 * and without the specular metal that made `Industrieanlage` need clamping.
 * Nothing is read on top of it at any width, so this is not a contrast argument
 * in either direction — it is that a backdrop nobody can see is not a backdrop,
 * and one with a blown highlight competes with the headline beside it.
 */
.lc-reghero__img {
	width: 100%;
	height: 100%;
	object-fit: cover;
	object-position: center 48%;
	filter: grayscale(1) brightness(0.72) contrast(1.05);
}

/* The content sits above the absolutely positioned plate. No `z-index`
   anywhere: the plate is a positioned element earlier in tree order, so paint
   order alone puts the shell over it. */
.lc-reghero--image {
	position: relative;
}

.lc-reghero--image > .lc-shell {
	position: relative;
}

.lc-reghero__grid {
	display: grid;
	gap: var(--lc-reg-gap);
	grid-template-columns: minmax(0, 1fr);
	align-items: center;
}

/*
 * `--lc-t-2xl`, not the `--lc-t-3xl` the other two heroes take.
 *
 * This is a register rather than a landing page: the reference sets its title
 * about two thirds the size of the homepage's, and a 64px headline over a list
 * of two alerts is a page shouting about how little it holds. It also has to
 * carry "Published supplier alerts" on one line at desktop widths, which 42px
 * does in a 780px column and 64px does not.
 */
.lc-reghero__title {
	max-width: 20ch;
	margin: 0;
	font-size: var(--lc-t-2xl);
	font-weight: 700;
	letter-spacing: -0.026em;
	line-height: 1.08;
	text-wrap: balance;
}

.lc-reghero__lede {
	max-width: 52ch;
	margin: 1rem 0 0;
	color: var(--lc-fg-soft);
	font-size: var(--lc-t-md);
	line-height: 1.6;
}

.lc-reghero__actions {
	display: flex;
	flex-wrap: wrap;
	gap: 0.75rem;
	margin: 1.5rem 0 0;
}

/*
 * The split, at the same 62rem the other two heroes use.
 *
 * The plate's left edge is **derived from the grid rather than checked against
 * it**. As a percentage of the viewport it would be a different distance from
 * the text at every window width — 46px of flat ink at 992 and 843px at 3440 —
 * because the text column's right edge is a fraction of a shell that is capped
 * and centred and the viewport is not. That bug shipped on the homepage and
 * survived being "checked at 992, 1200, 1440, 1920 and 2560".
 *
 * The terms are the shell's left rail, its gutter, column one and the join:
 *
 *   (100% - shell) / 2  +  gutter  +  col1  +  gap
 *
 * `100%` is this section's padding box — `.lc-reghero` sets no inline padding,
 * so that is the viewport — while the grid's own `100%` is its content box,
 * which is why column one is spelled out again instead of shared as a length.
 * `--lc-reg-split` is the one number both expressions read, so the join is one
 * grid gap at every width by construction.
 */
@media (min-width: 62rem) {
	.lc-reghero__bg {
		display: block;
		inset: 0 0 0 calc(
			(100% - min(100%, var(--lc-shell))) / 2
			+ var(--lc-gutter)
			+ (min(100%, var(--lc-shell)) - var(--lc-gutter) * 2 - var(--lc-reg-gap))
				* var(--lc-reg-split)
			+ var(--lc-reg-gap)
		);
	}

	/*
	 * The left edge, dissolved into the ink the text sits on. The stops are
	 * **lengths and not percentages**: a fade sized at 20% of the plate grows
	 * with the monitor, so the photograph starts further from the text the more
	 * room there is for it and the extra reads as dead space. The job is an
	 * edge, and an edge is a fixed distance.
	 */
	.lc-reghero__bg::after {
		position: absolute;
		inset: 0;
		background: linear-gradient(
			90deg,
			var(--lc-ink) 0%,
			rgba(17, 29, 42, 0.62) 3rem,
			rgba(17, 29, 42, 0.34) 18rem
		);
		content: "";
	}

	/*
	 * Column two is deliberately empty. It reserves the plate's width inside the
	 * grid, so the headline can never run under the photograph however long a
	 * translation turns out to be — and the plate places itself from the same
	 * `--lc-reg-split`, so the reservation cannot fall out of step with the
	 * thing it reserves.
	 */
	.lc-reghero__grid {
		grid-template-columns:
			calc((100% - var(--lc-reg-gap)) * var(--lc-reg-split))
			minmax(0, 1fr);
	}

	.lc-reghero__main {
		grid-column: 1;
	}
}

/* ==========================================================================
   3. The commitment strip
   ========================================================================== */

/*
 * **`.lc-trustbar` moved to `style.css` at 1.9.0 and is not declared here.**
 *
 * It was written for this page and was the only caller until the part-number
 * index grew one too. A component with callers on more than one template belongs
 * with the component and not with the first page that needed it — the call 1.5.6
 * made when `.lc-icon__knockout` shipped in `home.css` and was therefore styled
 * on exactly one template. See section 15b of `style.css`.
 */

/* ==========================================================================
   4. The register
   ========================================================================== */

/*
 * The field the entries sit on, which is `--lc-band` and not paper.
 *
 * The reference draws white cards on a light-gray field, and that relationship
 * is what makes a column of entries read as a column of objects: at 1.081:1 the
 * step is a mood rather than a boundary, so each card also declares a `--lc-rule`
 * edge and the two together do the job. Painting the field white instead would
 * leave the cards distinguishable by their hairline alone — the same argument
 * `.lc-signs` makes on the homepage.
 */
.lc-registry {
	padding-block: clamp(2.25rem, 5vw, 3.5rem);
	background: var(--lc-band);
}

/*
 * 76rem is the split the homepage's warning-signs band and the checklist page
 * both take, and for the same kind of reason: below it the rail would leave an
 * entry about 300px of description column. Above it the rail is 22.5rem — 360px,
 * the width the homepage's report card was measured to and the width the design
 * reference draws these cards at.
 *
 * `align-items: start` is what lets the rail sit level with the heading while
 * being *after* the list in the DOM, which is the order a phone wants: the
 * alerts first, then how they were verified.
 */
.lc-registry__grid {
	display: grid;
	gap: clamp(1.75rem, 3.5vw, 2.5rem);
	grid-template-columns: minmax(0, 1fr);
	align-items: start;
}

@media (min-width: 76rem) {
	.lc-registry__grid {
		grid-template-columns: minmax(0, 1fr) 22.5rem;
	}
}

.lc-registry__main {
	min-width: 0;
}

/*
 * The heading, its sentence and the count, with the count pushed to the far end
 * and dropping under the heading below 34rem rather than squashing beside it.
 * `align-items: baseline` so the count sits on the heading's baseline and not on
 * the middle of a two-line block.
 */
.lc-registry__head {
	display: flex;
	flex-wrap: wrap;
	align-items: baseline;
	justify-content: space-between;
	gap: 0.5rem 1.5rem;
	margin-bottom: 1.1rem;
}

.lc-registry__heading {
	margin: 0;
	font-size: var(--lc-t-xl);
	letter-spacing: -0.016em;
}

.lc-registry__intro {
	margin: 0.3rem 0 0;
	color: var(--lc-fg-soft);
	font-size: var(--lc-t-ui);
}

.lc-registry__count {
	margin: 0;
	color: var(--lc-fg-quiet);
	font-size: var(--lc-t-ui);
	white-space: nowrap;
}

/* ---- The filter form --------------------------------------------------- */

.lc-regfilters {
	margin: 0 0 1.1rem;
}

/*
 * Four cells: the search box takes the free space and the three controls beside
 * it are sized to their content. `auto-fit` was declined here — the submit
 * button and the two selects have genuinely different natural widths, and a
 * uniform track makes the button either wider than its label or narrower than
 * its target.
 *
 * Below 46rem every cell goes full width, which keeps the 44px target the
 * button already has and stops a two-word select truncating.
 */
.lc-regfilters__grid {
	display: grid;
	gap: 0.6rem;
	grid-template-columns: minmax(0, 1fr);
	align-items: stretch;
}

@media (min-width: 46rem) {
	.lc-regfilters__grid {
		grid-template-columns: minmax(0, 1fr) auto auto auto;
	}
}

.lc-regfilters__field {
	display: flex;
	margin: 0;
	min-width: 0;
}

/*
 * The glyph sits *inside* the field, so the box is what draws the border and
 * the input inside it declares none. `position: relative` on the box and
 * padding on the input would work too and is worse: the glyph would then have to
 * know the input's padding, and the two would drift the first time either moved.
 */
.lc-regfilters__box {
	display: flex;
	flex: 1 1 auto;
	align-items: center;
	gap: 0.55rem;
	min-width: 0;
	padding-inline: 0.85rem;
	border: 1px solid var(--lc-rule-firm);
	border-radius: var(--lc-radius);
	background: var(--lc-field-bg);
}

.lc-regfilters__box:focus-within {
	border-color: var(--lc-fg);
}

.lc-regfilters__glyph {
	flex: 0 0 auto;
	color: var(--lc-fg-quiet);
}

/*
 * `background: none` and `border: 0`, because the box around it is the control.
 * `min-width: 0` beside them for the flex reason: a field's default
 * `min-width: auto` refuses to shrink below its intrinsic size, which on a
 * `type="search"` is wide enough to push the row past its track.
 */
.lc-regfilters__input {
	flex: 1 1 auto;
	min-width: 0;
	padding-block: 0.75rem;
	border: 0;
	background: none;
	color: var(--lc-fg);
	font-family: inherit;
	font-size: var(--lc-t-ui);
}

.lc-regfilters__input:focus {
	outline: none;
}

.lc-regfilters__input::placeholder {
	color: var(--lc-fg-quiet);
	opacity: 1;
}

/*
 * The selects keep the UA's own arrow. Replacing it means `appearance: none`
 * plus a background image, and a background image cannot follow `currentColor` —
 * which is the whole reason the icon pack is inlined. `color-scheme: light` from
 * the pin is what makes the UA draw a light control here rather than a dark one.
 */
.lc-regfilters__select {
	min-width: 0;
	max-width: 100%;
	padding: 0.75rem 0.85rem;
	border: 1px solid var(--lc-rule-firm);
	border-radius: var(--lc-radius);
	background: var(--lc-field-bg);
	color: var(--lc-fg);
	font-family: inherit;
	font-size: var(--lc-t-ui);
}

/* The button is `.lc-button--primary`; this only stops it demanding the 3.25rem
   the hero's buttons take, so the row's four cells line up on one height. */
.lc-regfilters__submit {
	width: 100%;
	min-height: 0;
	padding-block: 0.75rem;
}

.lc-regfilters__clear {
	margin: 0.7rem 0 0;
	font-size: var(--lc-t-ui);
}

/* ---- An entry ---------------------------------------------------------- */

.lc-entries {
	display: grid;
	gap: 0.85rem;
	margin: 0;
	padding: 0;
	list-style: none;
}

/*
 * `--lc-bg` on `--lc-band` with a `--lc-rule` edge — the pairing `.lc-sign` and
 * `.lc-check` already use, and the one the reference draws.
 *
 * The left rule is the status, and it is the one place on this page where colour
 * carries meaning. It is not the *only* place that meaning is carried: the badge
 * beside it states the status in words, so `border-left-color` could be dropped
 * entirely and nothing would be lost — the test every colour on this site has to
 * pass. 3px rather than 1: an edge this short has to be seen from the far side
 * of a 900px card.
 */
.lc-entry {
	display: grid;
	gap: 0.75rem 1.25rem;
	margin: 0;
	padding: 1.15rem 1.35rem;
	border: 1px solid var(--lc-rule);
	border-left: 3px solid var(--lc-rule-firm);
	border-radius: var(--lc-radius);
	background: var(--lc-bg);
	grid-template-columns: minmax(0, 1fr);
}

/*
 * One rule per status, and each names the *ink* of its own badge rather than a
 * new colour. Four values that must stay related to four badges are one edit
 * away from not being, which is the argument `--lc-st-review-fg` already makes
 * for pointing at `--lc-caution-text` instead of restating #7f6220.
 */
.lc-entry--reported {
	border-left-color: var(--lc-st-reported-fg);
}

.lc-entry--review {
	border-left-color: var(--lc-st-review-fg);
}

.lc-entry--evidenced {
	border-left-color: var(--lc-st-evidenced-fg);
}

.lc-entry--corrected {
	border-left-color: var(--lc-st-corrected-fg);
}

.lc-entry__status {
	min-width: 0;
}

.lc-entry__body {
	min-width: 0;
}

.lc-badge__glyph {
	flex: 0 0 auto;
}

.lc-entry__date {
	margin: 0 0 0.3rem;
	color: var(--lc-fg-quiet);
	font-size: var(--lc-t-xs);
	font-weight: 600;
	letter-spacing: 0.09em;
	text-transform: uppercase;
}

.lc-entry__title {
	margin: 0;
	font-size: var(--lc-t-md);
	letter-spacing: -0.01em;
	line-height: 1.4;
}

.lc-entry__title a {
	color: var(--lc-fg);
	text-decoration: none;
}

.lc-entry__title a:hover,
.lc-entry__title a:focus-visible {
	text-decoration: underline;
	text-decoration-color: var(--lc-accent);
	text-decoration-thickness: 2px;
	text-underline-offset: 0.18em;
}

/*
 * `overflow-wrap` on the heading because an alert's title opens with its domain
 * — one unbroken token that would otherwise set the width of the card and push
 * the whole register past its track.
 */
.lc-entry__title a {
	overflow-wrap: anywhere;
}

.lc-entry__parts {
	display: flex;
	flex-wrap: wrap;
	gap: 0.4rem;
	margin: 0.5rem 0 0;
	padding: 0;
	list-style: none;
}

/*
 * The part numbers are `--lc-accent-text`, which is 5.72:1 on paper — a *word*,
 * and the reference draws them as the loudest thing in the card after the
 * title. The mark token would be 3.29:1 and would fail as text, which is the
 * distinction the three golds exist for.
 */
.lc-entry__part {
	color: var(--lc-accent-text);
	font-family: var(--lc-mono);
	font-size: var(--lc-t-ui);
	font-weight: 700;
	letter-spacing: 0.02em;
	overflow-wrap: anywhere;
}

.lc-entry__excerpt {
	margin: 0.55rem 0 0;
	max-width: var(--lc-measure);
	color: var(--lc-fg-soft);
	font-size: var(--lc-t-ui);
	line-height: 1.55;
}

/*
 * The tactics, as outlined chips.
 *
 * `--lc-danger` for both the ink and the edge — #a12e32 on paper is 7.11:1 as
 * text and clears 1.4.11 as a boundary from the same value. They are red because
 * each one names a documented fraud tactic, which is a finding; they are
 * *outlined* rather than filled because a row of solid red blocks under a red
 * badge reads as four more badges.
 */
.lc-entry__tactics {
	display: flex;
	flex-wrap: wrap;
	gap: 0.4rem;
	margin: 0.7rem 0 0;
	padding: 0;
	list-style: none;
}

.lc-entry__tactic {
	padding: 0.12rem 0.5rem;
	border: 1px solid var(--lc-danger);
	border-radius: var(--lc-radius);
	color: var(--lc-danger);
	font-size: var(--lc-t-xs);
	line-height: 1.6;
}

.lc-entry__foot {
	display: flex;
	flex-wrap: wrap;
	align-items: baseline;
	justify-content: space-between;
	gap: 0.4rem 1rem;
	margin: 0.8rem 0 0;
}

.lc-entry__checked {
	color: var(--lc-fg-quiet);
	font-size: var(--lc-t-sm);
}

/*
 * `margin-left: auto` so the link stays at the far end when the re-check date is
 * absent — `justify-content: space-between` puts a lone child at the *start*,
 * which would move the one control on the card to the left on exactly the
 * entries that have the least in them.
 */
.lc-entry__more {
	display: inline-flex;
	align-items: center;
	gap: 0.35rem;
	margin-left: auto;
	font-size: var(--lc-t-ui);
	font-weight: 600;
}

.lc-entry__chevron {
	flex: 0 0 auto;
}

.lc-entry__more:hover .lc-entry__chevron,
.lc-entry__more:focus-visible .lc-entry__chevron {
	transform: translateX(3px);
}

/*
 * The badge moves into a column of its own once there is room for one, which is
 * what the reference draws. 9rem is measured rather than picked: "Under review"
 * is the longest label the register can print, and at `--lc-t-xs` with the
 * badge's own 0.6rem padding and its 13px glyph it is 138px — so the track is
 * sized to the widest thing that can land in it rather than to today's data.
 */
@media (min-width: 40rem) {
	.lc-entry {
		grid-template-columns: 9rem minmax(0, 1fr);
	}
}

/* ---- Empty, and the pagination ----------------------------------------- */

.lc-registry__main .lc-empty {
	margin: 0;
	padding: 1.5rem;
	border: 1px solid var(--lc-rule);
	border-radius: var(--lc-radius);
	background: var(--lc-bg);
}

/*
 * `.lc-pagination` is styled in `style.css` and reused whole. It is written for
 * `the_posts_pagination()`'s markup, which wraps the links in
 * `nav.navigation.pagination > .nav-links`; `paginate_links()` returns the bare
 * links, so this puts back the one property that wrapper supplied.
 */
.lc-registry__main .lc-pagination {
	display: flex;
	flex-wrap: wrap;
	gap: 0.4rem;
	margin-top: 1.5rem;
}

/* ==========================================================================
   5. The rail
   ========================================================================== */

.lc-registry__rail {
	display: grid;
	gap: 1rem;
	min-width: 0;
}

/*
 * **`.lc-railcard`, `.lc-railsteps` and `.lc-railstep` moved to `style.css` at
 * 1.9.0**, for the reason `.lc-trustbar` did: the part-number index carries the
 * same two-card rail, and a second copy of a component is one that drifts.
 * Section 15b of `style.css`.
 *
 * **The rail's lookup rules moved at 1.12.0**, to `lc-components.css` rather
 * than to `style.css`. The comment they left behind said they *could not* move,
 * because they re-lay the plugin's lookup and tie on specificity with the
 * component sheet at (0,2,0) — so a copy in `style.css`, which loads before it,
 * would have sat in plain sight doing nothing. That was right about `style.css`
 * and it named the wrong destination: the sheet a rule has to out-order is the
 * one to put it *in*, after the rules it out-orders. `/domains/` is the second
 * page with a lookup in its rail, and a second copy of a component is a second
 * value the moment either is edited.
 *
 * Nothing about the cards in this rail is declared here now. What follows is the
 * rail itself.
 */

/*
 * Sticky only where there is a column for it to be sticky in, and it clears the
 * masthead by the token three other things already clear it by.
 *
 * The reduced-motion block in `style.css` reaches `animation-*` and
 * `transition-*` and nothing else, so `position` has to be stood down by name —
 * the same override `.lc-toc`, the homepage's method figure and `.lc-beforepay`
 * each carry.
 *
 * On `.lc-registry__rail` and not on `.lc-railcard`: two sticky siblings inside
 * one grid item each stop at the same offset and overlap as the page scrolls.
 * The rail is the box that sticks and the cards ride in it.
 */
@media (min-width: 76rem) {
	.lc-registry__rail {
		position: sticky;
		top: calc(var(--lc-head-h) + 1rem);
	}
}

@media (prefers-reduced-motion: reduce) {
	.lc-registry__rail {
		position: static;
	}
}

/* ==========================================================================
   6. Print
   ========================================================================== */

/*
 * These rules live here rather than in `style.css` section 18, and that is not
 * filing — it is specificity. This sheet loads **after** `style.css`, so a
 * `background` declared here for a band ties with the print reset there on one
 * class and wins on source order. `.lc-signs` is named in that block for exactly
 * this reason and says so.
 */
@media print {
	.lc-reghero,
	.lc-trustbar,
	.lc-registry,
	.lc-entry,
	.lc-railcard,
	.lc-railcard__head {
		padding-block: 0.5rem;
		background: none !important;
	}

	.lc-reghero__bg {
		display: none;
	}

	/*
	 * The hero is `.lc-onimage`, which section 18 already un-inverts — white ink
	 * on a navy that print has dropped is an invisible headline. The rail card's
	 * header is the same fault with the tokens the other way up: it paints
	 * `--lc-invert-fg` on `--lc-invert-bg`, and with the fill gone that is white
	 * text on white paper.
	 */
	.lc-railcard__head {
		color: #000000;
	}

	/* The controls go: a search box and a submit button are things only somebody
	   who can click has any use for. The register itself is the document. */
	.lc-regfilters,
	.lc-reghero__actions,
	.lc-railcard__lookup,
	.lc-pagination {
		display: none;
	}

	.lc-registry__grid,
	.lc-entry {
		display: block;
	}

	.lc-entry {
		margin-bottom: 0.5rem;
		border: 1px solid rgba(0, 0, 0, 0.3);
		break-inside: avoid;
	}

	/* The alert's own URL, because a link that cannot be clicked is a reference
	   that has to be readable. The same treatment the sources on an alert get. */
	.lc-entry__title a[href]::after {
		content: " <" attr(href) ">";
		font-family: var(--lc-mono);
		font-size: 0.85em;
		font-weight: 400;
		word-break: break-all;
	}

	.lc-entry__more,
	.lc-railcard {
		break-inside: avoid;
	}
}