/* Haddiction Checkout — phase 9
 *
 * STEP 1 IS DELIBERATELY ALMOST EMPTY.
 *
 * The scaffold renders WooCommerce's own checkout inside our page wrapper, so
 * this file only sets the page up: a centred column, the drawer's type, and
 * room to breathe. The compact styling comes next, once the takeover and all
 * three integrations have been confirmed working on the live site.
 *
 * Styling an unverified takeover first would mean that when something breaks,
 * we would not know whether it was the template or the CSS.
 *
 * !important throughout, same as drawer.css: haddiction.com runs Elementor and
 * Astra, both of which restyle bare elements and form controls inside page
 * content. Exempt, because no theme targets them: transition, animation,
 * overscroll-behavior and ::-webkit-scrollbar*.
 */

/* The checkout's own header: the logo, and nothing else.
 *
 * Aero rendered this page on a bare canvas with no theme header, which is why
 * the site header had never appeared here. It is kept out deliberately - every
 * nav link on a checkout is an exit from a page the shopper is halfway through
 * paying on.
 *
 * `.hadc-checkout-body` is on <body>, so these rules cannot reach any other
 * page even if a theme ships a selector with the same name. */
.hadc-checkout-body {
	background: #ffffff !important;
	margin: 0 !important;
	padding: 0 !important;
}

.hadc-checkout-header {
	background: #ffffff !important;
	/* No divider. `border-bottom` used to be declared here and then wiped by the
	   `border: 0` shorthand on the very next line - a rule that had looked like
	   a hairline for weeks while drawing nothing. The shorthand is the one that
	   was doing the work, so it is now the only one here. */
	border: 0 !important;
	display: block !important;
	margin: 0 !important;
	padding: 0 !important;
	width: 100% !important;
}

.hadc-checkout-header-inner {
	align-items: center !important;
	display: flex !important;
	justify-content: flex-start !important;
	margin: 0 auto !important;
	max-width: 980px !important;
	/* Less underneath than above: the logo needs air over it to clear the phone's
	   status bar, but what sits below is the order summary, and 14px there plus
	   the page's own top padding read as a hole rather than as breathing room. */
	padding: 14px 16px 10px !important;
	width: 100% !important;
}

/* The theme's custom-logo markup, constrained. Astra ships it at whatever size
   the customiser says, which on this site is a full-bleed hero logo - fine in a
   site header, absurd above a payment form. */
.hadc-checkout-header-inner .custom-logo-link,
.hadc-checkout-header-inner a {
	border: 0 !important;
	box-shadow: none !important;
	display: inline-block !important;
	line-height: 0 !important;
	margin: 0 !important;
	padding: 0 !important;
	text-decoration: none !important;
}

.hadc-checkout-header-inner img {
	display: block !important;
	height: auto !important;
	margin: 0 !important;
	max-height: 44px !important;
	max-width: 180px !important;
	padding: 0 !important;
	width: auto !important;
}

.hadc-checkout-wordmark {
	color: #111111 !important;
	font-size: 18px !important;
	font-weight: 800 !important;
	letter-spacing: 0.02em !important;
	line-height: 1.2 !important;
	text-transform: uppercase !important;
}

.hadc-checkout-footer {
	background: #ffffff !important;
	border-top: 1px solid #ececec !important;
	display: block !important;
	margin: 0 !important;
	padding: 0 !important;
	width: 100% !important;
}

.hadc-checkout-footer-inner {
	color: #8a8a8a !important;
	font-size: 12px !important;
	line-height: 1.4 !important;
	margin: 0 auto !important;
	max-width: 980px !important;
	padding: 12px 16px !important;
	text-align: center !important;
	width: 100% !important;
}

.hadc-checkout-page {
	background: #ffffff !important;
	display: block !important;
	margin: 0 !important;
	padding: 14px 16px 24px !important;
	width: 100% !important;
}

/* 980px is the checkout's own measure, not the theme's. Wide enough for the
   two-column address + summary layout that comes in step 3, narrow enough that
   a single field never becomes a 1400px line. */
.hadc-checkout-inner {
	margin: 0 auto !important;
	max-width: 980px !important;
	width: 100% !important;
}

/* The notices wrapper is printed by the template rather than by WooCommerce,
   because our page wrapper sits outside the content area Woo prints into. It
   must never collapse: it is where "Please choose a drop-off location" lands. */
.hadc-checkout-page .woocommerce-notices-wrapper {
	display: block !important;
	margin: 0 !important;
}

/* THE INVISIBLE 16px. The wrapper used to carry `margin-bottom: 16px` itself,
 * which it then applied whether or not it held a notice. Measured on the live
 * page: height 0, margin-bottom 16 - a spacer nobody could see, sitting between
 * the logo and the order summary and making the header look detached.
 *
 * `:empty` below does not catch it: WooCommerce prints whitespace inside the
 * wrapper, and a node with a text child is not empty. So the margin moves onto
 * the notices themselves, which only exist when there is something to say. No
 * `:has()` either - that would be one more selector that silently does nothing
 * in a browser that lacks it, which is exactly the class of bug being fixed.
 *
 * This is the same shape as the Meal Builder's gap: a zero-height child with a
 * margin. Worth remembering as the first thing to look for in a spacing bug. */
.hadc-checkout-page .woocommerce-notices-wrapper > * {
	margin-bottom: 16px !important;
}

.hadc-checkout-page .woocommerce-notices-wrapper:empty {
	display: none !important;
}

/* ---------------------------------------------------------------------------
 * EAS: taxes and duties, calculated silently.
 *
 * EAS's own block is hidden rather than removed. It must stay in the DOM and
 * stay functional, because:
 *
 *   - its hidden nonce field is what our AJAX authenticates with;
 *   - its status element is what we read to know whether the cart is
 *     calculated;
 *   - its button is the fallback the customer needs if the silent path fails
 *     or if EAS asks for a real confirmation, at which point the class comes
 *     off and the block reappears.
 *
 * Removing it would break all three at once, and the failure would look like a
 * pricing bug rather than a markup one.
 * ------------------------------------------------------------------------ */
/* HIDDEN FROM THE FIRST PAINT, not hidden a moment later.
 *
 * Until 0.36.1 the block was visible by default and eas.js hid it on ready.
 * On every load - and most visibly on a reload, when the browser paints before
 * the scripts run - that drew EAS's "Calculate Taxes" button above our
 * Continue, then took it away. Two buttons, for about a frame, on the step
 * where the shopper is deciding whether this checkout is trustworthy.
 *
 * So the default is now hidden and `hadc-eas-shown` is what reveals it: the
 * first paint is right, and the reveal only happens on the paths that need the
 * manual button (a failure, or EAS asking for a real confirmation).
 */
.hadc-checkout-page .eascompliance {
	display: none !important;
}

.hadc-checkout-page .eascompliance.hadc-eas-shown {
	display: block !important;
}

/* Kept for one release. A browser still holding the previous stylesheet from
   Hostinger's edge pairs the OLD css with the NEW script; this is the rule
   that version of the css needs, and writing both classes costs nothing. */
.hadc-checkout-page .eascompliance.hadc-eas-silent {
	display: none !important;
}

/* Our one-line status, where the button used to be. Deliberately quiet: on the
   normal path this is the only thing the customer ever sees of EAS, and a
   reassuring line reads better than a control they must not press. */
.hadc-checkout-page .hadc-eas-line {
	border-radius: 10px !important;
	display: block !important;
	font-size: 13px !important;
	font-weight: 600 !important;
	line-height: 1.4 !important;
	margin: 0 0 12px !important;
	padding: 10px 12px !important;
}

/* [hidden] is a browser-default-stylesheet behaviour, and any
   `display: … !important` above outranks it - the Elementor lesson from the
   other plugins. It has to be restated or an empty status line keeps its
   padding and leaves a floating grey bar. */
.hadc-checkout-page .hadc-eas-line[hidden] {
	display: none !important;
}

.hadc-checkout-page .hadc-eas-line.is-working {
	background: #f3f4f6 !important;
	color: #4b5563 !important;
}

.hadc-checkout-page .hadc-eas-line.is-done {
	background: rgba(22, 163, 74, 0.10) !important;
	color: #15803d !important;
}

/* Amber, not red. Neither of these is an error the customer caused, and both
   have a working way forward directly beneath them. */
.hadc-checkout-page .hadc-eas-line.is-confirm,
.hadc-checkout-page .hadc-eas-line.is-failed {
	background: rgba(245, 158, 11, 0.14) !important;
	color: #92400e !important;
}

/* ===========================================================================
 * THE FORM
 *
 * This styles WooCommerce's OWN markup - #customer_details, #order_review,
 * #place_order, .woocommerce-input-wrapper - and deliberately not a single
 * `wfacp_` class. 0.13 rendered our page wrapper but handed the form back to
 * Aero, so the Next button, the square fields and the red links Yanis saw were
 * all FunnelKit's. Styling those would have made the checkout depend on the
 * plugin this project exists to delete.
 *
 * `HADC_Checkout::core_template()` is what restores Woo's markup. Everything
 * below assumes it.
 * ======================================================================== */

/* One field style, everywhere. Shopify-ish: generous radius, soft border, a
   real focus ring, and enough height to be comfortable on a phone. 16px is not
   a style choice - iOS Safari zooms the whole page when a focused input is
   under 16px, which on a checkout reads as the page jumping about. */
.hadc-checkout-page input[type="text"],
.hadc-checkout-page input[type="email"],
.hadc-checkout-page input[type="tel"],
.hadc-checkout-page input[type="number"],
.hadc-checkout-page input[type="password"],
.hadc-checkout-page textarea,
.hadc-checkout-page select,
.hadc-checkout-page .select2-container .select2-selection--single {
	background: #ffffff !important;
	border: 1px solid #d9dce0 !important;
	border-radius: 12px !important;
	box-shadow: none !important;
	box-sizing: border-box !important;
	color: #111111 !important;
	font-size: 16px !important;
	font-weight: 500 !important;
	line-height: 1.4 !important;
	min-height: 50px !important;
	outline: none !important;
	padding: 13px 14px !important;
	width: 100% !important;
}

/* THE SIDEWAYS DRAG. Leave this rule alone.
 *
 * When select2 enhances the country and state dropdowns it does NOT remove the
 * real <select>. It keeps it, for screen readers and for form submission, and
 * hides it with `.select2-hidden-accessible` - a 1px box, clipped, absolutely
 * positioned. The field rule above names `select` and ends in
 * `width: 100% !important`, which beat select2's own `width: 1px !important`
 * and blew that 1px box out to 100% of the PAGE, because it is absolutely
 * positioned and so measures against the document, not against its wrapper.
 *
 * Measured live: `#billing_country` 1512px wide starting at x=265, so the
 * document scrolled to 1777px against a 1512px viewport. 265px of empty
 * overflow, on every step, because the address fields live in one form that
 * every step shares. On a phone that is the page sliding left and right under
 * your thumb with nothing visible out there.
 *
 * It is invisible precisely BECAUSE select2 clipped it, which is why it read
 * as "something is too wide" rather than as a dropdown being too wide.
 *
 * So: restate select2's own box, after ours, and never style this element as
 * a field. It is not one - it is a hidden mirror of one.
 */
.hadc-checkout-page select.select2-hidden-accessible {
	border: 0 !important;
	clip: rect(0 0 0 0) !important;
	clip-path: inset(50%) !important;
	height: 1px !important;
	margin: -1px !important;
	min-height: 0 !important;
	overflow: hidden !important;
	padding: 0 !important;
	position: absolute !important;
	white-space: nowrap !important;
	width: 1px !important;
}

.hadc-checkout-page textarea {
	min-height: 96px !important;
	resize: vertical !important;
}

.hadc-checkout-page input:focus,
.hadc-checkout-page textarea:focus,
.hadc-checkout-page select:focus {
	border-color: #111111 !important;
	box-shadow: 0 0 0 3px rgba(17, 17, 17, 0.10) !important;
}

/* ---------------------------------------------------------------------------
 * THE COUNTRY DROPDOWN ITSELF.
 *
 * SCOPED ON THE BODY, NOT ON `.hadc-checkout-page`, and that is the whole
 * reason this block looks different from every other one in this file. When
 * select2 opens, it moves the dropdown to the END OF <body> - outside our page
 * wrapper entirely - so `.hadc-checkout-page .select2-dropdown` matches
 * nothing and the panel keeps select2's stock styling no matter what is
 * written there. Checked on the live page: its parent is a
 * `.select2-container` sitting as a direct child of body.
 *
 * `body.hadc-checkout-body` is the class our own template prints, so these
 * rules still cannot reach the select2 dropdowns on any other page of the
 * shop - the shop archive filters, wp-admin, anything a plugin adds.
 *
 * What was wrong with the stock panel: `border-radius: 4px 4px 0 0`, so square
 * at the bottom and barely rounded at the top, flush against the field, with a
 * flat grey `#eee` highlight. Now it is a floating card with the same 14px
 * radius as the summary bar, 6px clear of the field, and a soft blue on the
 * row under the cursor. `overflow: hidden` is what makes the first and last
 * options clip to the radius instead of poking out of the corners.
 * ------------------------------------------------------------------------ */
body.hadc-checkout-body .select2-container--open .select2-dropdown {
	background: #ffffff !important;
	border: 1px solid #e3e5e8 !important;
	border-radius: 14px !important;
	box-shadow: 0 12px 32px rgba(17, 17, 17, 0.12) !important;
	overflow: hidden !important;
}

/* It opens downward most of the time and upward near the bottom of the screen.
   Both need the gap, in opposite directions. */
body.hadc-checkout-body .select2-container--open .select2-dropdown--below {
	margin-top: 6px !important;
}

body.hadc-checkout-body .select2-container--open .select2-dropdown--above {
	margin-top: -6px !important;
}

body.hadc-checkout-body .select2-container--open .select2-search--dropdown {
	padding: 10px !important;
}

/* 16px is not a style choice here either: under 16px iOS Safari zooms the page
   when the search field takes focus, and it takes focus the instant the
   dropdown opens. */
body.hadc-checkout-body .select2-container--open .select2-search__field {
	border: 1px solid #d9dce0 !important;
	border-radius: 10px !important;
	font-size: 16px !important;
	padding: 10px 12px !important;
}

body.hadc-checkout-body .select2-container--open .select2-results__options {
	max-height: 260px !important;
	padding: 6px !important;
}

body.hadc-checkout-body .select2-container--open .select2-results__option {
	border-radius: 10px !important;
	font-size: 15px !important;
	padding: 11px 12px !important;
}

/* The row under the cursor and the country already chosen get the same soft
   blue. Stock select2 uses a solid `#5897fb` with white text, which on a
   checkout full of black and white reads as a different site. */
body.hadc-checkout-body .select2-container--open .select2-results__option--highlighted,
body.hadc-checkout-body .select2-container--open .select2-results__option[aria-selected="true"] {
	background: #eaf1ff !important;
	color: #111111 !important;
}

/* The soft drop. select2 has no animation of its own; the element is inserted
   into the document when it opens, so a plain `animation` runs exactly once,
   at the right moment, with nothing to reset. Not in the !important sweep -
   `animation` is on the exempt list, as no theme targets it. */
@keyframes hadc-select-drop {
	from {
		opacity: 0;
		transform: translateY(-6px);
	}
	to {
		opacity: 1;
		transform: translateY(0);
	}
}

body.hadc-checkout-body .select2-container--open .select2-dropdown {
	animation: hadc-select-drop 160ms cubic-bezier(0.4, 0, 0.2, 1);
}

@media ( prefers-reduced-motion: reduce ) {
	body.hadc-checkout-body .select2-container--open .select2-dropdown {
		animation: none;
	}
}

/* ---------------------------------------------------------------------------
 * THE PHONE FIELD'S COUNTRY-CODE DROPDOWN, matched to the one above.
 *
 * SCOPED ON THE BODY, for the same reason the select2 block is - and getting
 * this wrong is what made 0.21.2 do nothing on a phone while looking correct
 * on a desktop.
 *
 * intl-tel-input (v29.1.2 here) has TWO modes, and they put the panel in
 * different places. Read out of the library itself rather than guessed:
 *
 *   inline     - desktop. The panel stays inside the field's own wrapper, so
 *                it is inside `.hadc-checkout-page` and the old scope worked.
 *   fullscreen - phones. The panel is wrapped in a NEW
 *                `div.iti.iti--detached-country-selector.iti--fullscreen-popup`
 *                and APPENDED TO BODY, outside our page wrapper entirely.
 *
 * So `.hadc-checkout-page .iti__country-selector` matched nothing on mobile,
 * which is the only place the fullscreen mode is ever used. Scoping on
 * `body.hadc-checkout-body` covers both and still keeps these rules off every
 * other page of the shop.
 *
 * The library already HAS its own search box - checked before writing any of
 * this, because adding one would have meant replacing its init rather than
 * restyling it. Nothing here is JavaScript.
 *
 * The element that IS the panel is `.iti__country-selector`, not
 * `.iti__dropdown-content` - that is what older versions called it and it does
 * not exist in v29. It holds the search wrapper and the country list, and sits
 * beside the flag button inside `.iti__country-container`; styling the
 * container would have drawn a card around the button too.
 * ------------------------------------------------------------------------ */
body.hadc-checkout-body .iti__country-selector {
	background: #ffffff !important;
	border: 1px solid #e3e5e8 !important;
	border-radius: 14px !important;
	box-shadow: 0 12px 32px rgba(17, 17, 17, 0.12) !important;
	overflow: hidden !important;
}

/* The 6px gap is an inline-mode idea: it separates the panel from the field it
   dropped out of. In fullscreen there is no field on screen to separate from,
   so it would just be a stray offset. */
body.hadc-checkout-body .iti--inline-country-selector .iti__country-selector {
	margin-top: 6px !important;
}

/* THE SEARCH BOX IS NOT MISSING - IT IS VISUALLY HIDDEN, BY THE LIBRARY.
 *
 * This is the actual answer to "there is no search field", and it was found by
 * reading the live page rather than the markup. intlTelInput.css ships:
 *
 *   .iti .iti__search-input-wrapper {
 *     position: absolute; width: 1px; height: 1px; padding: 0; margin: -1px;
 *     overflow: hidden; clip: rect(0,0,0,0); border: 0;
 *   }
 *
 * - the standard visually-hidden recipe. The input is in the DOM, it is
 * focusable, and its filtering WORKS: typing "latv" into it on the live page
 * cut the list to Latvia alone. Only the box is hidden. So this is nine
 * declarations undoing that, not a search feature being built - and no
 * JavaScript, which is why the library's own filtering keeps working.
 *
 * STICKY, because the panel opens scrolled to the country already selected -
 * the UK, far down an alphabetical list - and a static search box at the top
 * of that scroller would be off screen before the shopper touched anything.
 * The white background is not decoration: without it the country rows scroll
 * visibly underneath the input.
 *
 * The magnifier is `position: absolute` inside the wrapper, so a flex `gap`
 * does nothing for it - the clearance has to come from the input's own
 * padding-left, which is why that number looks oddly specific. */
body.hadc-checkout-body .iti__search-input-wrapper {
	align-items: center !important;
	background: #ffffff !important;
	border: 0 !important;
	clip: auto !important;
	clip-path: none !important;
	display: flex !important;
	height: auto !important;
	margin: 0 !important;
	overflow: visible !important;
	padding: 10px !important;
	position: sticky !important;
	top: 0 !important;
	width: auto !important;
	z-index: 2 !important;
}

/* 22px = the wrapper's own 10px padding plus 12px inside the pill. The icon is
   positioned against the WRAPPER, not the input, so it has to be told about
   the pill's inset by hand. */
body.hadc-checkout-body .iti__search-icon {
	align-items: center !important;
	color: #9aa0a6 !important;
	display: flex !important;
	left: 22px !important;
}

/* A rounded pill, not a flush strip across the top of the panel - a square
   edge-to-edge row inside a 14px-rounded card reads as a rendering fault. */
body.hadc-checkout-body .iti__search-input {
	background: #f4f5f7 !important;
	border: 1px solid #e3e5e8 !important;
	border-radius: 10px !important;
	font-size: 16px !important;
	padding: 10px 12px 10px 38px !important;
	width: 100% !important;
}

/* `input.` and `:focus` are both load-bearing. The focus ring further up this
   file is `.hadc-checkout-page input:focus`, which outranks a plain
   `body.hadc-checkout-body .iti__search-input` - so without the tag and the
   pseudo-class here the ring draws a hard rectangle around a row that is meant
   to sit flush inside the panel. Checked on the live page, not reasoned about:
   the first attempt at this rule lost, and the ring was still there. */
body.hadc-checkout-body input.iti__search-input:focus,
body.hadc-checkout-body input.iti__search-input:focus-visible {
	border-color: #c9ccd1 !important;
	box-shadow: none !important;
	outline: none !important;
}

body.hadc-checkout-body .iti__country-list {
	background: transparent !important;
	border: 0 !important;
	box-shadow: none !important;
	max-height: 260px !important;
	padding: 6px !important;
}

/* THE SIDEWAYS DRAG ON A PHONE, AND WHY IT IS ONLY IN THIS MODE.
 *
 * The panel carries `iti--flexible-dropdown-width`, and the library styles
 * that class with `white-space: nowrap` so the dropdown can grow as wide as
 * its widest row. On a desktop that is the point. On a phone the sheet is
 * pinned to the screen, so the widest row - "United Arab Emirates
 * (<the Arabic name>)" - cannot widen it and overflows instead, which is
 * exactly the left-right pull. Measured rather than guessed: the list's
 * scrollWidth was wider than its clientWidth before this, equal after.
 *
 * `.iti__country-name` is `flex: 0 0 auto` in the library, so it refuses to
 * shrink even once wrapping is allowed - hence the flex and min-width below.
 * `overflow-x: hidden` is the backstop for anything else that ever exceeds
 * the width.
 *
 * Fullscreen also gets the full height of the sheet rather than a 260px window
 * inside it: a scrollbar within a scrollbar was the other half of why the
 * stock version felt wrong on a phone. */
body.hadc-checkout-body .iti--fullscreen-popup .iti__country-list {
	max-height: none !important;
	overflow-x: hidden !important;
	white-space: normal !important;
}

body.hadc-checkout-body .iti--fullscreen-popup .iti__country-selector {
	max-width: 100% !important;
	width: 100% !important;
}

body.hadc-checkout-body .iti--fullscreen-popup .iti__country-name {
	flex: 0 1 auto !important;
	min-width: 0 !important;
	overflow-wrap: anywhere !important;
}

body.hadc-checkout-body .iti__country {
	border-radius: 10px !important;
	font-size: 15px !important;
	padding: 11px 12px !important;
}

body.hadc-checkout-body .iti__country.iti__highlight {
	background: #eaf1ff !important;
}

/* select2 is WooCommerce's country and state dropdown. It builds its own box,
   so the height has to be restated or it sits a few pixels short of every
   input beside it - the kind of 3px misalignment that reads as "cheap". */
.hadc-checkout-page .select2-container .select2-selection--single {
	display: flex !important;
	align-items: center !important;
}

.hadc-checkout-page .select2-container .select2-selection--single
	.select2-selection__rendered {
	color: #111111 !important;
	line-height: 1.4 !important;
	padding: 0 !important;
}

.hadc-checkout-page .select2-container .select2-selection--single
	.select2-selection__arrow {
	height: 100% !important;
	right: 10px !important;
	top: 0 !important;
}

.hadc-checkout-page label {
	color: #4b5563 !important;
	display: block !important;
	font-size: 13px !important;
	font-weight: 600 !important;
	margin: 0 0 6px !important;
}

/* Woo marks required fields with a red abbr. Keep the asterisk, lose the alarm
   colour: nothing is wrong yet, and a form full of red before the shopper has
   typed anything looks like a page of errors. */
.hadc-checkout-page .required,
.hadc-checkout-page abbr.required {
	border: 0 !important;
	color: #9ca3af !important;
	text-decoration: none !important;
}

.hadc-checkout-page .form-row {
	margin: 0 0 14px !important;
	padding: 0 !important;
}

/* NO LOGIN BLOCK ON THE CHECKOUT - THE BELT TO THE PHP BRACES.
 *
 * `HADC_Checkout::drop_login_form()` takes WooCommerce's own callback off
 * `woocommerce_before_checkout_form`, which is the real fix. This hides the
 * same thing in case another plugin prints its own copy of the notice, or
 * attaches WooCommerce's function at a priority ours has already passed.
 *
 * Only a logged-out shopper ever sees it, which is why this needs a belt at
 * all: it is the one part of the page we cannot check while signed in. */
.hadc-checkout-page .woocommerce-form-login-toggle,
.hadc-checkout-page form.woocommerce-form-login,
.hadc-checkout-page form.login {
	display: none !important;
}

/* Links. Grey by default - the discount-code toggle and the login link are
   secondary actions, and a red link on a checkout reads as an error message.
   Underlined so they are still obviously links without colour doing the work. */
.hadc-checkout-page .woocommerce-form-coupon-toggle a,
.hadc-checkout-page .woocommerce-form-login-toggle a,
.hadc-checkout-page .showcoupon,
.hadc-checkout-page .showlogin,
.hadc-checkout-page .woocommerce-info a,
.hadc-checkout-page .woocommerce-message a {
	color: #4b5563 !important;
	font-weight: 600 !important;
	text-decoration: underline !important;
	text-underline-offset: 2px !important;
}

.hadc-checkout-page .woocommerce-form-coupon-toggle a:hover,
.hadc-checkout-page .showcoupon:hover,
.hadc-checkout-page .showlogin:hover {
	color: #111111 !important;
}

/* The notice boxes those links live in: quiet, not a coloured banner. */
.hadc-checkout-page .woocommerce-form-coupon-toggle .woocommerce-info,
.hadc-checkout-page .woocommerce-form-login-toggle .woocommerce-info {
	background: #f8f9fa !important;
	border: 1px solid #ececec !important;
	border-radius: 12px !important;
	color: #4b5563 !important;
	font-size: 14px !important;
	margin: 0 0 14px !important;
	padding: 12px 14px !important;
}

.hadc-checkout-page .woocommerce-form-coupon-toggle .woocommerce-info::before,
.hadc-checkout-page .woocommerce-form-login-toggle .woocommerce-info::before {
	content: none !important;
}

/* ---------------------------------------------------------------------------
 * BUTTONS — one component, shared with the drawer.
 *
 * The drawer's Checkout button is the thing a shopper has just pressed to get
 * here, so the button that finishes the job should be the same object: same
 * height, same radius, same weight. These values are drawer.css's, copied
 * deliberately rather than imported - the two stylesheets load on different
 * pages and an @import would be a second blocking request on the one page
 * where speed is money.
 * ------------------------------------------------------------------------ */
.hadc-checkout-page #place_order,
.hadc-checkout-page .button.alt,
.hadc-checkout-page button.hadc-btn {
	background: #111111 !important;
	border: 0 !important;
	border-radius: 12px !important;
	box-shadow: none !important;
	color: #ffffff !important;
	cursor: pointer !important;
	display: block !important;
	font-size: 15px !important;
	font-weight: 700 !important;
	letter-spacing: 0 !important;
	line-height: 1.2 !important;
	min-height: 52px !important;
	padding: 15px 20px !important;
	text-align: center !important;
	text-transform: none !important;
	width: 100% !important;
}

.hadc-checkout-page #place_order:hover,
.hadc-checkout-page .button.alt:hover {
	background: #000000 !important;
	color: #ffffff !important;
}

/* A disabled button must look disabled AND still look like the same button.
   Aero's Next sat permanently grey, which trains people to ignore it. */
.hadc-checkout-page #place_order:disabled,
.hadc-checkout-page .button.alt:disabled {
	cursor: not-allowed !important;
	opacity: 0.45 !important;
}

/* Secondary buttons - Apply coupon, Login - are outlined, not filled. Two
   filled black buttons on one screen is two primary actions, and the shopper
   has to work out which one finishes the order. */
.hadc-checkout-page .button:not(.alt):not(.hadc-qty-btn) {
	background: #ffffff !important;
	border: 1px solid #d9dce0 !important;
	border-radius: 12px !important;
	box-shadow: none !important;
	color: #111111 !important;
	font-size: 14px !important;
	font-weight: 600 !important;
	min-height: 50px !important;
	padding: 13px 18px !important;
	text-transform: none !important;
}

.hadc-checkout-page .button:not(.alt):hover {
	border-color: #111111 !important;
}

/* ---------------------------------------------------------------------------
 * The three steps.
 *
 * Ours, drawn from our own markup - NOT Aero's `wfacp_three_step`. It is a
 * progress indicator, not navigation: it says where the shopper is in a form
 * they scroll through, which is why the steps are not clickable. A clickable
 * step that jumps past an unfilled address is a validation bug waiting to
 * happen.
 * ------------------------------------------------------------------------ */
.hadc-checkout-steps {
	display: flex !important;
	gap: 8px !important;
	list-style: none !important;
	margin: 0 0 20px !important;
	padding: 0 !important;
	width: 100% !important;
}

.hadc-checkout-steps li {
	align-items: center !important;
	color: #9ca3af !important;
	display: flex !important;
	flex: 1 1 0 !important;
	font-size: 13px !important;
	font-weight: 600 !important;
	gap: 8px !important;
	list-style: none !important;
	margin: 0 !important;
	padding: 0 0 10px !important;
	/* The rule under each step IS the progress bar - no second element to keep
	   in step with the labels. */
	border-bottom: 2px solid #ececec !important;
}

.hadc-checkout-steps li.is-current,
.hadc-checkout-steps li.is-done {
	border-bottom-color: #111111 !important;
	color: #111111 !important;
}

/* A step you can go back to looks like one you can press.
 *
 * Only the steps BEHIND the current one get this - checkout-steps.js adds the
 * class, and only to those - because only they do anything. A step ahead needs
 * Continue and the validation that comes with it, so it is deliberately left
 * looking like plain text: offering a cursor and then refusing the tap is
 * worse than never offering it.
 *
 * `focus-visible` rather than `focus`: these are list items given
 * `role="button"` and a tab stop, so a keyboard user must be able to see where
 * they are, while a mouse user gets no ring after a click. */
.hadc-checkout-steps li.is-clickable {
	cursor: pointer !important;
}

.hadc-checkout-steps li.is-clickable:hover .hadc-step-label {
	text-decoration: underline !important;
}

.hadc-checkout-steps li.is-clickable:focus-visible {
	border-radius: 4px !important;
	outline: 2px solid #111111 !important;
	outline-offset: 2px !important;
}

.hadc-checkout-steps .hadc-step-num {
	align-items: center !important;
	background: #ececec !important;
	border-radius: 999px !important;
	color: #6b7280 !important;
	display: flex !important;
	flex: 0 0 auto !important;
	font-size: 12px !important;
	font-weight: 700 !important;
	height: 22px !important;
	justify-content: center !important;
	width: 22px !important;
}

.hadc-checkout-steps li.is-current .hadc-step-num,
.hadc-checkout-steps li.is-done .hadc-step-num {
	background: #111111 !important;
	color: #ffffff !important;
}

/* Under ~420px the three labels stop fitting on one line. The numbers alone
   still say "1 of 3", which is the whole job of the component. */
@media ( max-width: 420px ) {
	.hadc-checkout-steps .hadc-step-label {
		display: none !important;
	}

	.hadc-checkout-steps li {
		justify-content: center !important;
	}
}

/* ===========================================================================
 * FIXES from the first look at the real form, 16 Nov 2026.
 * ======================================================================== */

/* THE BULLETS. WooCommerce builds the payment methods as a real <ul><li>, and
   our page wrapper sits outside the content area whose reset normally kills
   the markers - so every payment method had a bullet beside it. This is the
   single thing that made the order section look broken. */
.hadc-checkout-page #order_review ul,
.hadc-checkout-page #order_review ol,
.hadc-checkout-page ul.wc_payment_methods,
.hadc-checkout-page ul.woocommerce-shipping-methods,
.hadc-checkout-page .woocommerce-checkout-review-order ul {
	list-style: none !important;
	margin: 0 !important;
	padding: 0 !important;
}

.hadc-checkout-page #order_review li,
.hadc-checkout-page ul.wc_payment_methods > li,
.hadc-checkout-page ul.woocommerce-shipping-methods > li {
	list-style: none !important;
	margin: 0 !important;
}

.hadc-checkout-page #order_review li::marker,
.hadc-checkout-page ul.wc_payment_methods > li::marker {
	content: none !important;
}

/* Hidden labels. WordPress's own visually-hidden class, restated because our
   `display: … !important` rules outrank the theme's copy of it - the same
   browser-default problem as [hidden] above. */
.hadc-checkout-page label.screen-reader-text {
	border: 0 !important;
	clip: rect( 1px, 1px, 1px, 1px ) !important;
	clip-path: inset( 50% ) !important;
	height: 1px !important;
	margin: -1px !important;
	overflow: hidden !important;
	padding: 0 !important;
	position: absolute !important;
	white-space: nowrap !important;
	width: 1px !important;
}

/* With the caption inside the field, rows can sit closer without crowding. */
.hadc-checkout-page .form-row.hadc-labelled {
	margin: 0 0 10px !important;
}

.hadc-checkout-page input::placeholder,
.hadc-checkout-page textarea::placeholder {
	color: #9ca3af !important;
	opacity: 1 !important; /* Firefox dims placeholders by default. */
}

/* Section headings: smaller, so "Billing details" stops competing with the
   step bar directly above it. */
.hadc-checkout-page h3,
.hadc-checkout-page #order_review_heading {
	color: #111111 !important;
	font-size: 18px !important;
	font-weight: 700 !important;
	letter-spacing: 0 !important;
	line-height: 1.3 !important;
	margin: 22px 0 12px !important;
}

/* The order review, as a card rather than loose text on the page. */
/* The order box carries no border of its own.
 *
 * It used to, and with the review table missing it was a large empty card
 * wrapped around a single green "Taxes and duties included" line, which read
 * as a mistake. The card belongs to the TABLE - the thing that is actually a
 * list of what is being bought - so the border moved there. */
.hadc-checkout-page #order_review {
	background: transparent !important;
	border: 0 !important;
	margin: 0 0 16px !important;
	padding: 0 !important;
}

.hadc-checkout-page .woocommerce-checkout-review-order-table {
	background: #ffffff !important;
	border: 1px solid #ececec !important;
	border-radius: 16px !important;
	padding: 6px 16px !important;
}

.hadc-checkout-page .woocommerce-checkout-review-order-table {
	border: 0 !important;
	border-collapse: collapse !important;
	margin: 0 0 14px !important;
	width: 100% !important;
}

.hadc-checkout-page .woocommerce-checkout-review-order-table th,
.hadc-checkout-page .woocommerce-checkout-review-order-table td {
	border: 0 !important;
	border-bottom: 1px solid #f1f2f4 !important;
	font-size: 14px !important;
	padding: 10px 0 !important;
	text-align: left !important;
	vertical-align: top !important;
}

.hadc-checkout-page .woocommerce-checkout-review-order-table td {
	text-align: right !important;
}

.hadc-checkout-page .woocommerce-checkout-review-order-table tr.order-total th,
.hadc-checkout-page .woocommerce-checkout-review-order-table tr.order-total td {
	border-bottom: 0 !important;
	font-size: 17px !important;
	font-weight: 800 !important;
	padding-top: 14px !important;
}

/* Each payment method as a row, with the selected one marked. */
.hadc-checkout-page ul.wc_payment_methods > li {
	border-bottom: 1px solid #f1f2f4 !important;
	padding: 12px 0 !important;
}

.hadc-checkout-page ul.wc_payment_methods > li:last-child {
	border-bottom: 0 !important;
}

/* THE LI IS THE FLEX ROW, NOT THE LABEL.
 *
 * Measured, 16 Nov 2026: WooCommerce's markup is
 * `<li><input type=radio><label>…</label><div class=payment_box>` - the radio
 * is a SIBLING of the label, not inside it. Styling the label as the row left
 * the radio on its own line above everything, which is most of why step 3
 * looked broken.
 *
 * The payment_box must drop to its own full-width line beneath, so the li
 * wraps and the box is forced to 100%. */
.hadc-checkout-page ul.wc_payment_methods > li {
	align-items: center !important;
	display: flex !important;
	flex-wrap: wrap !important;
	gap: 10px !important;
}

.hadc-checkout-page ul.wc_payment_methods > li > label {
	align-items: center !important;
	color: #111111 !important;
	cursor: pointer !important;
	display: flex !important;
	flex: 1 1 auto !important;
	font-size: 15px !important;
	font-weight: 600 !important;
	gap: 10px !important;
	margin: 0 !important;
}

.hadc-checkout-page ul.wc_payment_methods > li > .payment_box {
	flex: 0 0 100% !important;
}

/* THE ROW SITS ON ONE AXIS. Undoing two nudges from a WPCode snippet.
 *
 * Measured on the live page, 16 Nov 2026. Centres of the three things in a
 * payment row, as distance from the top of the row:
 *
 *     radio 20    icon 24    text 14
 *
 * Three different lines, which is exactly what it looked like. Neither was our
 * doing, and neither is visible in a stylesheet read:
 *
 *   - `input.input-radio` carries `position: relative; top: -4px`
 *   - `.hadd-pay-text`    carries `position: relative; top: -10px`
 *
 * `.hadd-pay-*` is not our prefix - ours is `hadc-`. Another WPCode snippet
 * rewrites every payment label into `<span class="hadd-pay-icon">` plus
 * `<span class="hadd-pay-text">` and then nudges both it and the radio with
 * relative offsets, presumably to line them up against Aero's row, where the
 * metrics were different. On our row they are lifts applied to a flex layout
 * that had already centred everything correctly.
 *
 * `align-items: center` cannot win that argument: relative offsets are applied
 * AFTER layout, so the row centres the boxes and then the snippet slides two of
 * them upward. The fix is to take the offsets away - `position: static`, which
 * makes `top` meaningless - and let the centring that was always there stand.
 *
 * Confirmed by simulation before shipping: all three centres move to 24.
 *
 * The li switches to `align-items: flex-start` because it WRAPS - the payment
 * box is a third flex item forced onto its own line - and the radio is then
 * centred explicitly against the label instead. Centring the whole wrapping
 * row would centre the radio against the card form too.
 */
.hadc-checkout-page ul.wc_payment_methods > li {
	align-items: flex-start !important;
}

.hadc-checkout-page ul.wc_payment_methods > li > input.input-radio {
	align-self: center !important;
	flex: 0 0 auto !important;
	margin: 0 !important;
	position: static !important;
	top: auto !important;
}

.hadc-checkout-page ul.wc_payment_methods > li > label {
	min-height: 24px !important;
}

.hadc-checkout-page ul.wc_payment_methods > li > label > * {
	align-self: center !important;
	margin: 0 !important;
	position: static !important;
	top: auto !important;
}

/* The two spans the snippet wraps the label in. Flex, so whatever is inside
   them - an image in one, a text node in the other - centres on the same axis
   rather than sitting on its own baseline. */
.hadc-checkout-page ul.wc_payment_methods > li > label .hadd-pay-icon,
.hadc-checkout-page ul.wc_payment_methods > li > label .hadd-pay-text {
	align-items: center !important;
	display: flex !important;
	line-height: 1.2 !important;
}

/* ONE ICON PER ROW, AND IT IS OURS.
 *
 * `HADC_Checkout::own_icon()` replaces each gateway's icon markup with a
 * single `<img class="hadc-pay-icon">` from `assets/img/pay/`, so there is
 * nothing left to pick between: anything else inside a payment label is a
 * leftover - the gateway's own six card logos, or the WPCode snippet's
 * `.hadd-pay-icon` span - and goes.
 *
 * This replaced a filename match on a `-123` suffix, which depended on what
 * someone had named a media-library upload and broke twice in one evening.
 * See the note on own_icon() for the full reasoning.
 *
 * `order: -1` because WooCommerce prints the gateway icon AFTER the label
 * text, and the icon reads better in front of it. */
.hadc-checkout-page ul.wc_payment_methods > li label img {
	display: none !important;
}

.hadc-checkout-page ul.wc_payment_methods > li label img.hadc-pay-icon {
	display: block !important;
	flex: 0 0 auto !important;
	height: 22px !important;
	margin: 0 !important;
	max-width: none !important;
	object-fit: contain !important;
	order: -1 !important;
	vertical-align: middle !important;
	width: auto !important;
}

.hadc-checkout-page ul.wc_payment_methods > li input[type="radio"] {
	flex: 0 0 auto !important;
	height: 18px !important;
	margin: 0 !important;
	min-height: 0 !important;
	padding: 0 !important;
	width: 18px !important;
}

/* The gateway's own description/fields box. */
.hadc-checkout-page .payment_box {
	background: #f8f9fa !important;
	border: 0 !important;
	border-radius: 12px !important;
	color: #4b5563 !important;
	font-size: 13px !important;
	margin: 10px 0 0 !important;
	padding: 12px !important;
}

.hadc-checkout-page .payment_box::before {
	content: none !important; /* Woo's little pointer triangle. */
}

/* A payment row that ended up reading identically to one above it. Set by
   dedupeRows() in checkout.js - the backstop that makes two rows with the
   same name impossible whatever caused it. */
.hadc-checkout-page #payment ul.wc_payment_methods li.wc_payment_method.hadc-dupe-row {
	display: none !important;
}

/* Place order before a payment method is chosen. Step 3 starts with nothing
   selected on purpose - see the block comment in checkout-steps.js - so the
   button has to say, without words, that it is not ready yet. */
.hadc-checkout-page #place_order.hadc-no-method {
	cursor: not-allowed !important;
	opacity: 0.45 !important;
}

/* Terms. The link was coming out teal from the theme; it is a link like any
   other on this page. The row itself is a real decision, so it keeps a visible
   label and does not get the placeholder treatment (see checkout.js). */
.hadc-checkout-page .woocommerce-terms-and-conditions-wrapper {
	margin: 14px 0 !important;
}

/* No required-star on the terms tick. A checkbox you cannot order without is
   self-explanatory, and the `*` floats away from the sentence it belongs to
   because the label wraps. Hiding WooCommerce's `<abbr class="required">`
   changes appearance only - the tick is still required by the input's own
   `required` attribute and by the server-side check, so an unticked box is
   refused exactly as before. Scoped to the terms wrapper, so required marks
   on the address fields are untouched. */
.hadc-checkout-page .woocommerce-terms-and-conditions-wrapper abbr.required,
.hadc-checkout-page .woocommerce-terms-and-conditions-wrapper .required {
	display: none !important;
}

.hadc-checkout-page .woocommerce-terms-and-conditions-link,
.hadc-checkout-page .woocommerce-privacy-policy-link {
	color: #4b5563 !important;
	text-decoration: underline !important;
	text-underline-offset: 2px !important;
}

.hadc-checkout-page .woocommerce-form__label-for-checkbox,
.hadc-checkout-page .form-row label.checkbox {
	align-items: flex-start !important;
	color: #4b5563 !important;
	display: flex !important;
	font-size: 14px !important;
	font-weight: 500 !important;
	gap: 10px !important;
	line-height: 1.45 !important;
	margin: 0 !important;
}

.hadc-checkout-page input[type="checkbox"] {
	flex: 0 0 auto !important;
	height: 18px !important;
	margin: 2px 0 0 !important;
	min-height: 0 !important;
	padding: 0 !important;
	width: 18px !important;
}

/* The logo was rendering tiny. Give it a real floor as well as a ceiling. */
.hadc-checkout-header-inner img {
	max-height: 40px !important;
	min-height: 28px !important;
}

/* ===========================================================================
 * THE THREE-STEP FLOW
 *
 * Panes are hidden, never removed - see checkout-steps.js for why that is a
 * correctness requirement rather than a preference. The short version: a
 * detached input does not submit, EAS reads twelve field ids on every
 * recalculation, and Packlink's picker holds a reference to the review table.
 * ======================================================================== */
.hadc-checkout-page .hadc-step-hide {
	display: none !important;
}

.hadc-step-nav {
	display: flex !important;
	flex-direction: column !important;
	gap: 10px !important;
	margin: 18px 0 0 !important;
	width: 100% !important;
}

/* Continue is the same object as the drawer's Checkout button and as Place
   order - one primary action, one appearance, wherever it is in the journey.
   `.button.alt` on the markup means it inherits that rule; this only adds the
   order, so the primary action sits first under the thumb. */
.hadc-step-nav .hadc-step-next {
	order: 1 !important;
}

/* ---------------------------------------------------------------------------
 * NO BUSY STATE ON CONTINUE ANY MORE.
 *
 * 0.36.2 removed the in-button spinner. While the totals recalculate the whole
 * page is covered instead - the same cover shown while a payment completes -
 * because two loading states on one screen, handing over to each other, is
 * what read as flicker. The button is still disabled during the refresh; it
 * simply no longer says so on its own.
 *
 * The `.is-busy` rules that used to live here are gone rather than left
 * unused: a dead rule is a thing the next person has to prove is dead.
 * ------------------------------------------------------------------------ */

.hadc-step-nav .hadc-step-back,
.hadc-step-back-last .hadc-step-back {
	background: transparent !important;
	border: 0 !important;
	box-shadow: none !important;
	color: #4b5563 !important;
	cursor: pointer !important;
	display: block !important;
	font-size: 14px !important;
	font-weight: 600 !important;
	margin: 0 auto !important;
	min-height: 0 !important;
	order: 2 !important;
	padding: 10px !important;
	text-decoration: underline !important;
	text-underline-offset: 2px !important;
	width: auto !important;
}

.hadc-step-nav .hadc-step-back:hover,
.hadc-step-back-last .hadc-step-back:hover {
	color: #111111 !important;
}

.hadc-step-back-last {
	display: block !important;
	margin: 0 0 6px !important;
}

/* A field the shopper has been sent back to. Woo sets this class itself on
   submit; we set it too when Continue is blocked, so both routes look the
   same. */
.hadc-checkout-page .form-row.woocommerce-invalid input,
.hadc-checkout-page .form-row.woocommerce-invalid select,
.hadc-checkout-page .form-row.woocommerce-invalid textarea {
	border-color: #dc2626 !important;
}

.hadc-checkout-page .woocommerce-error {
	background: rgba( 220, 38, 38, 0.08 ) !important;
	border: 1px solid rgba( 220, 38, 38, 0.45 ) !important;
	border-radius: 12px !important;
	color: #991b1b !important;
	font-size: 14px !important;
	font-weight: 600 !important;
	list-style: none !important;
	margin: 0 0 14px !important;
	padding: 12px 14px !important;
}

.hadc-checkout-page .woocommerce-error li {
	list-style: none !important;
	margin: 0 !important;
}

.hadc-checkout-page .woocommerce-error::before {
	content: none !important;
}

/* ---------------------------------------------------------------------------
 * Two-up rows, fixed properly this time.
 *
 * 0.16.1 got this wrong twice over, and both were visible on a phone:
 *
 *   1. `.form-row-last` had width calc(50% - 7px) AND margin-left 14px, so the
 *      pair came to 100% + 7px. That 7px is why the whole page could be
 *      dragged sideways. The gap comes from the two widths alone - one floats
 *      left, one floats right, and the 14px they do not fill is the gutter.
 *      No margin needed, and adding one breaks the page.
 *
 *   2. The 50% rule was applied to EVERY `.form-row-last`. On this site
 *      `billing_phone_field` carries that class with no `form-row-first`
 *      before it (the Checkout Field Editor's layout settings), so the phone
 *      floated to half width and left an empty half beside it - the "weird
 *      empty field" under the number.
 *
 * So the pair rule now requires an actual pair: `.form-row-first +
 * .form-row-last`. An orphan of either class stays full width, which is what
 * it was always meant to be.
 * ------------------------------------------------------------------------ */
.hadc-checkout-page .form-row {
	box-sizing: border-box !important;
	clear: both !important;
	float: none !important;
	width: 100% !important;
}

/* TWO SEPARATE RULES, NOT ONE COMMA LIST, and this is the whole reason the
 * gap failed a third time. One invalid selector in a comma-separated list
 * invalidates the ENTIRE rule - so on a browser without :has() the pair rule
 * was thrown away whole and both fields went full width. Split, each stands or
 * falls alone. */
/* FLEX-BASIS 40%, NOT width 50% - 8px. Measured on the live page: the pair
 * came to 482 + 482 + 16 = 980, which is EXACTLY the container. Zero slack, so
 * a single sub-pixel rounding on a narrow phone tipped it over and flex wrapped
 * the second field onto its own line. The width was never too small; it had no
 * room to be wrong in.
 *
 * A 40% basis with flex-grow leaves 20% of slack before the gap is even
 * considered, then both grow to share the row equally. It cannot wrap, and it
 * cannot overflow. min-width: 0 because a flex item will not shrink below its
 * content otherwise, and a long placeholder would reintroduce the same bug. */
.hadc-checkout-page .form-row-first,
.hadc-checkout-page .form-row-first + .form-row-last {
	flex: 1 1 40% !important;
	min-width: 0 !important;
	width: auto !important;
}

/* FLEXBOX, NOT FLOATS - third attempt, and the reason is worth recording.
 *
 * Floats put the gutter in the leftover space between two widths, which means
 * the gap only exists if every width is exactly right. Twice it was not: once
 * a stray margin made the row wider than the page, and once the pair simply
 * looked too tight. A flex row with `gap` states the gutter directly, so it
 * cannot be eaten by a rounding error or a theme's own width rule, and it
 * cannot overflow.
 *
 * The float rules above are kept only to size the pair; the layout is the gap
 * below. Browsers without :has() stack them full width, which looks
 * deliberate rather than broken. */
.hadc-checkout-page .woocommerce-billing-fields__field-wrapper,
.hadc-checkout-page .woocommerce-shipping-fields__field-wrapper,
.hadc-checkout-page .woocommerce-additional-fields__field-wrapper {
	display: flex !important;
	flex-wrap: wrap !important;
	gap: 0 16px !important;
}

.hadc-checkout-page .woocommerce-billing-fields__field-wrapper > .form-row,
.hadc-checkout-page .woocommerce-shipping-fields__field-wrapper > .form-row,
.hadc-checkout-page .woocommerce-additional-fields__field-wrapper > .form-row {
	float: none !important;
}

.hadc-checkout-page .woocommerce-billing-fields__field-wrapper::after,
.hadc-checkout-page .woocommerce-shipping-fields__field-wrapper::after,
.hadc-checkout-page .woocommerce-additional-fields::after {
	clear: both !important;
	content: "" !important;
	display: block !important;
}

/* Nothing on a checkout may scroll sideways. A page that can be dragged left
   and right on a phone feels broken even when everything on it works. */
.hadc-checkout-body,
.hadc-checkout-page {
	max-width: 100% !important;
	overflow-x: hidden !important;
}

/* ---------------------------------------------------------------------------
 * The phone field's country flag (intl-tel-input).
 *
 * It positions its flag container at left: 0, hard against the border, while
 * our inputs carry 14px of padding - so the flag alone looked glued to the
 * edge. Padding the container rather than moving it keeps the plugin's own
 * positioning maths intact.
 * ------------------------------------------------------------------------ */
.hadc-checkout-page .iti__flag-container,
.hadc-checkout-page .iti__country-container {
	padding-left: 12px !important;
}

.hadc-checkout-page .iti {
	display: block !important;
	width: 100% !important;
}

/* Its INLINE dropdown is absolutely positioned and sized to its content, which
   is wider than a phone. Left unchecked it is a second cause of sideways drag.
 *
 * Inline only, deliberately. The fullscreen panel is a sheet that is SUPPOSED
 * to fill the screen, and it lives outside `.hadc-checkout-page` anyway (see
 * the country-code block near the top of this file) - capping it at
 * `100vw - 48px` would have drawn it 48px narrow with nothing beside it.
 *
 * `.iti__dropdown-content` used to be named here too. It is what versions
 * before v29 called the panel and it does not exist in the version this shop
 * loads, so it was styling nothing. */
.hadc-checkout-page .iti--inline-country-selector .iti__country-list {
	max-width: calc( 100vw - 48px ) !important;
}

/* ---------------------------------------------------------------------------
 * THE PAYMENT ROWS, WITHOUT THE SNIPPET.
 *
 * The existing alignment rules further up this file target `.hadd-pay-icon`
 * and `.hadd-pay-text` - wrappers the legacy WPCode snippet adds. Read off the
 * live markup, the three rows do not agree with each other:
 *
 *   Credit Card  <span.hadd-pay-icon.hadd-visa><img>  <span.fkwcs_stripe_icons>
 *   Google Pay   (bare text)                          <span.fkwcs_stripe_gpay_icons>
 *   Apple Pay    <span.hadd-pay-icon.hadd-wallet><img>  <span.fkwcs_stripe_apple_pay_icons>
 *
 * - Google Pay has no snippet wrapper at all, and the Apple Pay row's snippet
 * icon is a GOOGLE pay svg. So the rows were never consistently structured;
 * Aero's own styling was papering over it. That is why one row centres and
 * the others sit low and wrap.
 *
 * So this lays the row out from the LABEL, which every gateway has, instead of
 * from a wrapper only some rows carry - and it names the gateway's own icon
 * spans, which survive the snippet being deleted. The `.hadd-pay-*` rules can
 * go at that point; they are left for now so nothing changes before the
 * snippet is actually switched off.
 * ------------------------------------------------------------------------ */
.hadc-checkout-page #payment ul.wc_payment_methods li.wc_payment_method > label {
	align-items: center !important;
	display: flex !important;
	flex-wrap: nowrap !important;
	gap: 8px !important;
	line-height: 1.2 !important;
	margin: 0 !important;
	min-height: 28px !important;
}

/* The label text is the only part that may shrink. Without this the icon
   spans - which are fixed-width images - win the space and push the words
   onto a second line, which is the wrapping in the screenshot. */
.hadc-checkout-page #payment ul.wc_payment_methods li.wc_payment_method > label {
	overflow-wrap: anywhere !important;
}

/* ONLY OUR ICON - RESTATED AT THIS SPECIFICITY.
 *
 * The same pair of rules as further up the file, repeated here because these
 * selectors sit under `#payment` and so carry an ID: without the restatement
 * the hide below would outrank the show above and every row would go blank.
 * That ordering trap, in the other direction, is what put six card logos back
 * on the Credit Card row in 0.23.0.
 *
 * The WPCode snippet's `.hadd-pay-icon` span and the gateway's own icon spans
 * are both hidden outright - `own_icon()` has already replaced what they were
 * for. They can be deleted from this file once the snippet is switched off
 * and `silence_legacy_snippet()` goes with it; until then they are what stops
 * the snippet's uploads showing up beside ours. */
.hadc-checkout-page #payment ul.wc_payment_methods li.wc_payment_method > label img {
	display: none !important;
}

.hadc-checkout-page #payment ul.wc_payment_methods li.wc_payment_method > label img.hadc-pay-icon {
	display: block !important;
	flex: 0 0 auto !important;
	height: 22px !important;
	max-width: none !important;
	order: -1 !important;
	width: auto !important;
}

.hadc-checkout-page #payment .hadd-pay-icon,
.hadc-checkout-page #payment .fkwcs_stripe_icons,
.hadc-checkout-page #payment .fkwcs_stripe_gpay_icons,
.hadc-checkout-page #payment .fkwcs_stripe_apple_pay_icons {
	display: none !important;
}

/* THE APPLE PAY ROW STAYS VISIBLE ON DESKTOP - ON PURPOSE.
 *
 * Read off the live list, 16 Nov 2026, in desktop Chrome:
 *
 *     payment_method_fkwcs_stripe_apple_pay fkwcs_display_none
 *
 * `fkwcs_display_none` is the gateway hiding a wallet it thinks the browser
 * cannot offer. Our `li { display: flex !important }` outranks that plain
 * `display: none`, so the row shows anyway - and that is WANTED here, because
 * Stripe falls back to a QR code the shopper scans with their phone, which
 * Yanis confirmed works from desktop Chrome.
 *
 * So do NOT "fix" this by restating the hide. The only thing wrong with the
 * row on desktop was its name: the gateway relabels itself to whatever wallet
 * the browser has, so Chrome called it "Google Pay" and the list read as two
 * identical rows. `appleName()` in checkout.js puts the name back. */

/* Its icon needs no special case: `own_icon()` gives this gateway id the
   Apple Pay file, in every browser. 0.23.6 had a block here that swapped the
   snippet's wrong-brand `google-pay-123.svg` for the gateway's own
   `apple_pay.svg`; replacing all five icons in PHP made it redundant. */

/* The radio is a sibling of the label, not inside it. It carries NO margin of
   its own: the li is a flex row with `gap: 10px`, so a margin-right here is
   added to that gap rather than replacing it. 18px + 10px gap + 10px margin +
   a label asking for `calc(100% - 28px)` came to 100% + 10px, the row
   overflowed, and because the li wraps, the label dropped onto its own line
   below the radio. That is the "radio on one line, everything else under it"
   in the screenshot - an overflow, not an alignment bug.

   `top` is cleared because the WPCode snippet nudges the radio up by 4px for
   a layout that no longer exists. */
.hadc-checkout-page #payment ul.wc_payment_methods li.wc_payment_method > input[type="radio"] {
	align-self: center !important;
	margin: 0 !important;
	position: static !important;
	top: auto !important;
	vertical-align: middle !important;
}

/* `flex-start`, NOT `center`, and the difference only shows once a row is
   selected. The li wraps, so the gateway's card form is a third flex item on
   its own line; centring the whole container would centre the radio against
   that form - pushing it halfway down a 200px-tall card panel. With
   `flex-start` plus `align-self: center` on the radio, the radio centres
   inside its own flex LINE, which holds just the radio and the label. */
.hadc-checkout-page #payment ul.wc_payment_methods li.wc_payment_method {
	align-items: flex-start !important;
	display: flex !important;
	flex-wrap: wrap !important;
}

/* The gateway's own panel is a sibling too, and has to take the full row width
   once the row above it became a flex container. */
.hadc-checkout-page #payment ul.wc_payment_methods li.wc_payment_method > .payment_box {
	flex: 0 0 100% !important;
}

/* Step 2's shipping choice sits in a table cell WooCommerce draws, and that
   cell gets NO padding of its own.
 *
 * 0.23.0 put 14px on each side here, reading the flush left edge as a missing
 * indent. It was not: `ul#shipping_method` is the card, and its rows already
 * carry `padding: 13px 14px`. The cell padding therefore indented the whole
 * card rather than its contents, and since the card is `width: 100%` of the
 * cell it came out 28px narrower than `.hadc-delivery-card` directly above it
 * - two cards in a column that no longer lined up.
 *
 * So the rule is: the CARD spans the cell, and the padding lives inside the
 * card, exactly as it does on the delivery card and the payment list. */
.hadc-checkout-page .woocommerce-checkout-review-order-table td[data-title="Shipment"],
.hadc-checkout-page .woocommerce-checkout-review-order-table .shipping td {
	padding-left: 0 !important;
	padding-right: 0 !important;
}

.hadc-checkout-page #shipping_method {
	margin: 0 !important;
	padding: 0 !important;
}

/* ---------------------------------------------------------------------------
 * MAKING STEP 1 FIT ON A PHONE.
 *
 * Both of these are about getting Continue above the fold on Details, which is
 * the one screen where a shopper who has to scroll to find the button may just
 * decide they have not got time.
 *
 * The state row: see stateRows() in checkout.js for which countries lose it and
 * why that decision comes from WooCommerce's own data. The class is only ever
 * put on a row that country genuinely does not use, so there is never a hidden
 * field holding up a submit. Three classes beats any `.form-row` rule in this
 * file, which matters because several of them set `display` with !important.
 *
 * The EAS line: "Taxes and duties included" is reassurance about the PRICE, and
 * on step 1 there is no price on screen to reassure anyone about - the shopper
 * is typing their address. It is still there on Delivery and Payment, where the
 * order total is in front of them and the sentence means something. Hidden
 * rather than skipped, because EAS's own script writes into this element and
 * removing it would be a missing node, not a tidier page.
 * ------------------------------------------------------------------------ */
.hadc-checkout-page .form-row.hadc-state-hide {
	display: none !important;
}

/* "We will use this address for billing too." - see address_note() in
   class-hadc-checkout.php for why the sentence exists. Sized and coloured as
   a caption so the <h3> above it still reads as the heading of the section. */
.hadc-checkout-page .hadc-address-note {
	color: #6b7280 !important;
	font-size: 13px !important;
	line-height: 1.4 !important;
	margin: -6px 0 14px !important;
}

.hadc-checkout-page[data-hadc-step="1"] .hadc-eas-line {
	display: none !important;
}

/* "Ship to a different address?" when the setting is off.
 *
 * The checkbox is hidden, NOT removed - it is WooCommerce's own, it is forced
 * unticked server-side, and the shipping fields beneath it must stay in the
 * DOM because EAS reads them by id. See HADC_Checkout::ship_checked(). */
.hadc-no-ship-different #ship-to-different-address {
	display: none !important;
}

/* AND THE FIELDS UNDER IT, WHICH IS THE HALF THAT WAS MISSING.
 *
 * Hiding the checkbox left WooCommerce's shipping address fields on screen:
 * a second Street / Apartment / Town / Postcode / Country block underneath
 * the one the shopper had just filled in. Reported on the live guest
 * checkout, 16 Nov 2026 - never seen in testing because we were always
 * signed in, and a signed-in shopper's saved address changes what renders.
 *
 * A duplicate address block on a checkout is not untidy, it is frightening:
 * it reads as "that did not save, do it again".
 *
 * `display: none` rather than removing the markup, because the fields must
 * stay in the DOM - EAS reads twelve of them by id, and WooCommerce still
 * posts them. With ship-to-different forced off (see ship_checked()) the
 * billing address IS the shipping address, so nothing here is wanted on
 * screen at all. */
.hadc-no-ship-different .woocommerce-shipping-fields,
.hadc-no-ship-different div.shipping_address {
	display: none !important;
}

/* The delivery card on step 2: where it is going, and one way to change it. */
.hadc-delivery-card {
	background: #f8f9fa !important;
	border: 1px solid #ececec !important;
	border-radius: 16px !important;
	margin: 0 0 16px !important;
	padding: 14px 16px !important;
}

.hadc-delivery-head {
	align-items: center !important;
	display: flex !important;
	justify-content: space-between !important;
	margin: 0 0 8px !important;
}

.hadc-delivery-title {
	color: #6b7280 !important;
	font-size: 12px !important;
	font-weight: 700 !important;
	letter-spacing: 0.04em !important;
	text-transform: uppercase !important;
}

.hadc-delivery-edit {
	background: transparent !important;
	border: 0 !important;
	color: #4b5563 !important;
	cursor: pointer !important;
	font-size: 13px !important;
	font-weight: 600 !important;
	min-height: 0 !important;
	padding: 2px 0 !important;
	text-decoration: underline !important;
	text-underline-offset: 2px !important;
	width: auto !important;
}

.hadc-delivery-edit:hover {
	color: #111111 !important;
}

.hadc-delivery-body span {
	color: #111111 !important;
	display: block !important;
	font-size: 14px !important;
	line-height: 1.5 !important;
}

.hadc-delivery-body .hadc-delivery-empty {
	color: #9ca3af !important;
}

/* ---------------------------------------------------------------------------
 * Shipping choices as real radio rows.
 *
 * WooCommerce renders them as `ul#shipping_method > li > input + label` inside
 * the review table's shipping row - the same shape as the payment list, and
 * styled the same way here so a shopper meets one kind of choice-row on this
 * page rather than two.
 *
 * The row is the LI, not the label: the radio is a sibling of the label, the
 * lesson from the payment list. And Packlink injects its drop-off button and
 * hidden inputs into these same rows via `woocommerce_after_shipping_rate`, so
 * the row must wrap rather than clip.
 * ------------------------------------------------------------------------ */
.hadc-checkout-page tr.woocommerce-shipping-totals th {
	display: block !important;
	padding-bottom: 6px !important;
	width: 100% !important;
}

.hadc-checkout-page tr.woocommerce-shipping-totals td {
	display: block !important;
	padding: 0 0 10px !important;
	text-align: left !important;
	width: 100% !important;
}

.hadc-checkout-page ul#shipping_method {
	display: block !important;
	list-style: none !important;
	margin: 0 !important;
	padding: 0 !important;
}

.hadc-checkout-page ul#shipping_method > li {
	align-items: center !important;
	background: #ffffff !important;
	border: 1px solid #e3e5e8 !important;
	border-radius: 12px !important;
	display: flex !important;
	flex-wrap: wrap !important;
	gap: 10px !important;
	list-style: none !important;
	margin: 0 0 8px !important;
	padding: 12px 14px !important;
}

.hadc-checkout-page ul#shipping_method > li:last-child {
	margin-bottom: 0 !important;
}

/* The chosen one reads as chosen without colour doing all the work. */
.hadc-checkout-page ul#shipping_method > li:has( input:checked ) {
	border-color: #111111 !important;
	box-shadow: 0 0 0 1px #111111 inset !important;
}

.hadc-checkout-page ul#shipping_method > li > input[type="radio"] {
	flex: 0 0 auto !important;
	height: 18px !important;
	margin: 0 !important;
	min-height: 0 !important;
	padding: 0 !important;
	width: 18px !important;
}

.hadc-checkout-page ul#shipping_method > li > label {
	color: #111111 !important;
	cursor: pointer !important;
	flex: 1 1 auto !important;
	font-size: 15px !important;
	font-weight: 600 !important;
	margin: 0 !important;
}

/* Packlink's drop-off button lands here and must sit on its own line. */
.hadc-checkout-page ul#shipping_method > li .packlink-checkout-container,
.hadc-checkout-page ul#shipping_method > li button,
.hadc-checkout-page ul#shipping_method > li .packlink-drop-off {
	flex: 0 0 100% !important;
}

/* ===========================================================================
 * The order table, properly aligned.
 *
 * Product names were coming out right-aligned because the blanket rule put
 * every `td` on the right - correct for money, wrong for a product name, which
 * is what made the list look centred and ragged.
 * ======================================================================== */
.hadc-checkout-page .woocommerce-checkout-review-order-table th,
.hadc-checkout-page .woocommerce-checkout-review-order-table td {
	vertical-align: top !important;
}

.hadc-checkout-page .woocommerce-checkout-review-order-table .product-name,
.hadc-checkout-page .woocommerce-checkout-review-order-table td.product-name {
	font-size: 14px !important;
	font-weight: 500 !important;
	line-height: 1.45 !important;
	padding-right: 12px !important;
	text-align: left !important;
}

.hadc-checkout-page .woocommerce-checkout-review-order-table .product-total,
.hadc-checkout-page .woocommerce-checkout-review-order-table td.product-total {
	font-weight: 600 !important;
	text-align: right !important;
	white-space: nowrap !important;
}

/* The shipping row spans the full width, so its th and td stack rather than
   sharing the money column - otherwise the rate cards are squeezed into the
   narrow right-hand column, which is what made them stop half way. */
.hadc-checkout-page tr.woocommerce-shipping-totals {
	display: block !important;
	width: 100% !important;
}

.hadc-checkout-page tr.woocommerce-shipping-totals th {
	font-size: 14px !important;
	font-weight: 700 !important;
}

.hadc-checkout-page ul#shipping_method > li {
	width: 100% !important;
}

.hadc-checkout-page ul#shipping_method > li > label {
	font-size: 14px !important;
}

/* The payment block as one card, like the reference, with the methods
   hairline-separated inside it rather than floating on the page. */
.hadc-checkout-page #payment {
	background: #ffffff !important;
	border: 1px solid #e3e5e8 !important;
	border-radius: 16px !important;
	padding: 4px 16px !important;
}

/* The Place order row.
 *
 * The negative margins are what let the hairline above the button run the full
 * width of the card instead of stopping short of its padding. They are correct
 * and must stay.
 *
 * `width: auto` is what makes them WORK. Without it the row inherits
 * `width: 100%` - 946px, the card's content width - and a width that is already
 * fixed cannot grow. The -16px margins then only SHIFT the row 16px left
 * instead of widening it 16px on each side, so the button came out 914px wide
 * sitting 17px from the card's left edge and 49px from its right: not full
 * width, and visibly off-centre. Measured on the live page, which is the only
 * way this was ever going to be found - the stylesheet reads as if it works.
 *
 * With `auto` the row resolves to 978px, the button to 946px, and both edges
 * to 17px. That 946 is not a coincidence worth losing: it is exactly the width
 * of the Apple Pay and Google Pay rows above it, so the primary button and the
 * wallet buttons line up on both sides.
 */
.hadc-checkout-page #payment .place-order {
	border-top: 1px solid #f1f2f4 !important;
	margin: 0 -16px !important;
	padding: 14px 16px 6px !important;
	width: auto !important;
}

/* The wallet buttons span their row, like Place order spans its own.
 *
 * Woo's `.payment_box` carries its own inset, which on a card-number form is
 * right and on a single full-bleed button is a 12px margin that makes the
 * wallet button narrower than the black button directly beneath it. Only the
 * two wallet boxes are unpadded horizontally; the card form keeps its inset.
 *
 * What CANNOT be matched from here is the button's HEIGHT. Apple Pay and
 * Google Pay are drawn by Stripe inside an iframe at a height the gateway
 * hard-codes (42px, against our 52px), and neither Apple's nor Google's brand
 * rules allow us to draw our own button in their place. Width and alignment
 * are ours; the artwork is not.
 */
/* THE BUTTON BLEEDS OUT; THE TEXT DOES NOT.
 *
 * 0.19.3 zeroed the padding on these two boxes so the wallet button could span
 * the full row. It did - and it took the box's other child with it. The
 * "Pay with your Google Pay" line went flush to the card's edge while the same
 * line under Credit Card kept its 12px inset, so the two rows no longer looked
 * like the same component.
 *
 * Padding was the wrong tool for the job: it applies to everything inside, and
 * only ONE thing inside wanted to be wider. So the box keeps the same 12px as
 * every other payment box - which is what gives the description its inset back
 * - and the button's own wrapper reaches back out through it with a matching
 * negative margin. `width: auto` is what lets the negative margins widen it;
 * a pinned `width: 100%` would only shift it left, which is the same mistake
 * the Place order row was making. */
.hadc-checkout-page #payment .payment_box.payment_method_fkwcs_stripe_apple_pay,
.hadc-checkout-page #payment .payment_box.payment_method_fkwcs_stripe_google_pay {
	padding-left: 12px !important;
	padding-right: 12px !important;
}

.hadc-checkout-page #payment .payment_box .fkwcs_local_gateway_wrapper,
.hadc-checkout-page #payment .payment_box .fkwcs_apple_pay_gateway_wrap {
	margin-left: -12px !important;
	margin-right: -12px !important;
	max-width: none !important;
	width: auto !important;
}

/* "Save payment information" is a FIELDSET, and that is where the box came from.
 *
 * The gateway wraps that checkbox in `<fieldset id="fkwcs-save-cc-fieldset">`
 * carrying a 1px border, a 4px radius and - the part that mattered - 30px of
 * padding. Measured inside the payment box: the card-number field starts at
 * 12px, and the checkbox text started at 43px. Hence a second bordered card
 * sitting against the expiry and CVC fields, with its contents indented past
 * everything above them.
 *
 * All three go. The checkbox then starts at 12px like every other row in the
 * form, and the only border left in the box is the one around the card fields,
 * where it belongs. `min-width: 0` is there because a fieldset's default
 * `min-width: min-content` can refuse to shrink inside a flex or grid parent -
 * cheap insurance against a gateway update moving it.
 *
 * `margin-top` replaces what the border used to provide: separation. Without
 * it the checkbox would sit directly against the CVC field. */
.hadc-checkout-page #payment #fkwcs-save-cc-fieldset {
	background: transparent !important;
	border: 0 !important;
	border-radius: 0 !important;
	margin: 14px 0 0 !important;
	min-width: 0 !important;
	padding: 0 !important;
}

/* THE WALLET BUTTON SITS 4px LEFT OF CENTRE. Stripe's own iframe does it.
 *
 * When a wallet is selected, the button that replaces Place order is a Stripe
 * iframe, and Stripe ships it with `margin: 0 -4px`. Its width is pinned at the
 * same time, so those margins cannot widen it - they only SHIFT it, four pixels
 * to the left. Measured against the payment card's edges:
 *
 *     Place order      17 / 17
 *     Google Pay       13 / 21
 *
 * Which is the slightly-fatter right-hand gap, and nothing to do with our
 * layout: every wrapper above the iframe measured a clean 17 / 17.
 *
 * Scoped to `.form-row.place-order` on purpose, NOT to `#payment iframe`. The
 * card form is made of Stripe iframes too - card number, expiry, CVC - and they
 * may well want those margins for their own alignment. This is the one iframe
 * that is pretending to be our primary button, so it is the only one held to
 * our primary button's edges. */
.hadc-checkout-page #payment .form-row.place-order iframe {
	margin-left: 0 !important;
	margin-right: 0 !important;
}

/* Back belongs under the primary action, not above the payment methods where
   it sat between the order and the card fields. */
.hadc-step-back-last {
	margin: 10px 0 0 !important;
	order: 99 !important;
}

/* ---------------------------------------------------------------------------
 * Shipping rates: ONE card, rows inside it, radio always beside its text.
 *
 * Three separate outlined boxes read as three unrelated things. One card with
 * hairline-separated rows reads as one choice with three answers - the same
 * shape as the payment card, which is the point.
 *
 * THE WRAPPING RADIO: the row is a flex container that wraps (it has to, so
 * Packlink's drop-off button can drop to its own line), and a long rate label
 * was pushing itself onto the next line, leaving the circle stranded above its
 * own text. Giving the label an explicit basis of "everything except the
 * radio and the gap" means it can never be the thing that wraps - its TEXT
 * wraps inside it instead, which is what should happen.
 * ------------------------------------------------------------------------ */
.hadc-checkout-page ul#shipping_method {
	background: #ffffff !important;
	border: 1px solid #e3e5e8 !important;
	border-radius: 14px !important;
	overflow: hidden !important;
}

.hadc-checkout-page ul#shipping_method > li {
	background: transparent !important;
	border: 0 !important;
	border-bottom: 1px solid #f1f2f4 !important;
	border-radius: 0 !important;
	box-shadow: none !important;
	margin: 0 !important;
	padding: 13px 14px !important;
}

.hadc-checkout-page ul#shipping_method > li:last-child {
	border-bottom: 0 !important;
}

.hadc-checkout-page ul#shipping_method > li:has( input:checked ) {
	background: #fafbfc !important;
	border-color: #f1f2f4 !important;
	box-shadow: none !important;
}

.hadc-checkout-page ul#shipping_method > li > input[type="radio"] {
	flex: 0 0 18px !important;
}

/* 18px radio + 10px gap = 28px. The label takes exactly the rest, so the pair
   can never break across two lines. */
.hadc-checkout-page ul#shipping_method > li > label {
	flex: 0 1 calc( 100% - 28px ) !important;
	font-weight: 500 !important;
	margin: 0 !important;
	min-width: 0 !important;
}

.hadc-checkout-page ul#shipping_method > li:has( input:checked ) > label {
	font-weight: 700 !important;
}

/* The same guarantee for the payment rows, which have the same shape and the
   same failure waiting in them. */
.hadc-checkout-page ul.wc_payment_methods > li > input[type="radio"] {
	flex: 0 0 18px !important;
}

/* `1 1 0`, not a calc against the row width. A calc has to guess the radio,
   its margin and the gap, and it guessed wrong once already - see the
   overflow note on the radio above. Zero basis plus grow lets the label take
   whatever the radio and the gap leave, whatever those turn out to be. */
.hadc-checkout-page ul.wc_payment_methods > li > label {
	flex: 1 1 0 !important;
	min-width: 0 !important;
}

/* ===========================================================================
 * The order summary bar.
 *
 * Label and chevron left, total right - the shape every checkout uses, because
 * the total is the one number a shopper looks for and it belongs where the eye
 * lands last.
 *
 * The ITEM ROWS inside are the drawer's: .hadc-item, .hadc-item-media,
 * .hadc-item-name, .hadc-item-price, all defined in drawer.css, which is
 * enqueued here for exactly that reason. One item row in this project, not
 * two that drift.
 * ======================================================================== */
.hadc-summary-bar {
	background: #f8f9fa !important;
	border: 1px solid #ececec !important;
	border-radius: 14px !important;
	margin: 0 0 18px !important;
	overflow: hidden !important;
}

.hadc-summary-toggle {
	align-items: center !important;
	background: transparent !important;
	border: 0 !important;
	color: #111111 !important;
	cursor: pointer !important;
	display: flex !important;
	gap: 12px !important;
	justify-content: space-between !important;
	margin: 0 !important;
	min-height: 0 !important;
	padding: 14px 16px !important;
	text-align: left !important;
	width: 100% !important;
}

.hadc-summary-toggle-left {
	align-items: center !important;
	display: flex !important;
	gap: 8px !important;
	min-width: 0 !important;
}

.hadc-summary-cart {
	align-items: center !important;
	color: #4b5563 !important;
	display: flex !important;
	flex: 0 0 auto !important;
}

.hadc-summary-toggle-text {
	font-size: 15px !important;
	font-weight: 600 !important;
}

.hadc-summary-chevron {
	align-items: center !important;
	color: #6b7280 !important;
	display: flex !important;
	flex: 0 0 auto !important;
	transition: transform 0.18s ease;
}

.hadc-summary-bar.is-open .hadc-summary-chevron {
	transform: rotate( 180deg );
}

.hadc-summary-bar-total {
	flex: 0 0 auto !important;
	font-size: 17px !important;
	font-weight: 800 !important;
	margin-left: auto !important;
	text-align: right !important;
	white-space: nowrap !important;
}

/* The panel animates its own height. checkout.js measures the real height and
 * transitions to it, then hands the element back to `auto` - see setPanel()
 * there for why `height: auto` cannot be transitioned directly and why a
 * guessed `max-height` makes the duration depend on the cart's length.
 *
 * `overflow: hidden` is what makes the animation look like a drawer rather than
 * a list sliding out of a box. `transition` is on the EXEMPT list for the
 * !important rule this stylesheet otherwise follows - no theme targets it. */
.hadc-summary-items {
	background: #ffffff !important;
	border-top: 1px solid #ececec !important;
	display: block !important;
	overflow: hidden !important;
	padding: 4px 0 0 !important;
	transition: height 260ms cubic-bezier(0.4, 0, 0.2, 1);
}

/* Someone who has asked their device for less motion gets none: checkout.js
   skips the animation, and this stops the transition firing on the height it
   sets directly. */
@media ( prefers-reduced-motion: reduce ) {
	.hadc-summary-items {
		transition: none;
	}
}

/* The HEADER goes square at the bottom while the panel is open - not the card.
 *
 * Got this the wrong way round once: 0.20.2 squared `.hadc-summary-bar`, which
 * is the outer card, so the whole summary lost its bottom corners against the
 * page. The outer card keeps its 14px radius in both states; it is the grey
 * header's own bottom corners that should stop being round once something is
 * sitting directly beneath them.
 *
 * The radius it is losing is 12px, and it is the THEME's - measured on the live
 * page. Our `.hadc-summary-toggle` rule sets `background: transparent` but
 * never set a radius, so Astra's styling of a bare `<button>` came through
 * untouched. Collapsed, nothing shows it, because the card's own `overflow:
 * hidden` clips that corner anyway. Open, it cuts into the white panel
 * underneath.
 *
 * Zeroed only while open, so the collapsed pill is exactly as it was. */
.hadc-summary-bar.is-open .hadc-summary-toggle {
	border-bottom-left-radius: 0 !important;
	border-bottom-right-radius: 0 !important;
}

/* [hidden] is browser-default behaviour and loses to the display rule above,
   the same trap as everywhere else in this stylesheet. */
.hadc-summary-items[hidden] {
	display: none !important;
}

/* The drawer pads its rows for a 360px panel; this bar is narrower in feel,
   so only the horizontal padding is trimmed. Everything else is inherited. */
.hadc-summary-items .hadc-item {
	padding-left: 16px !important;
	padding-right: 16px !important;
}

.hadc-summary-items .hadc-item:last-of-type {
	border-bottom: 0 !important;
}

.hadc-summary-count {
	color: #6b7280 !important;
	font-size: 13px !important;
	font-weight: 600 !important;
}

.hadc-summary-lines {
	border-top: 1px solid #f1f2f4 !important;
	padding: 12px 16px 14px !important;
}

.hadc-summary-line {
	display: flex !important;
	font-size: 14px !important;
	justify-content: space-between !important;
	margin: 0 0 8px !important;
}

.hadc-summary-line span:first-child {
	color: #6b7280 !important;
}

.hadc-summary-line span:last-child {
	color: #111111 !important;
	font-weight: 600 !important;
}

/* The total gets the same green band as "Taxes and duties included".
 *
 * The exact values are copied from `.hadc-eas-line` rather than eyeballed -
 * the same 10% green, the same 10px radius, the same 10/12 padding - because
 * two nearly-identical greens a few rows apart look like a mistake, and the
 * day one of them is adjusted the other has to follow.
 *
 * The hairline above it goes: the band is already a boundary, and keeping both
 * drew a line immediately above a block with its own top edge. */
.hadc-summary-line.is-total {
	background: rgba( 22, 163, 74, 0.1 ) !important;
	border-radius: 10px !important;
	border-top: 0 !important;
	margin: 12px 0 0 !important;
	padding: 10px 12px !important;
}

.hadc-summary-line.is-total span {
	color: #111111 !important;
	font-size: 17px !important;
	font-weight: 800 !important;
}

/* The per-item tax, sitting under that item's own price.
 *
 * Quiet on purpose. It is context for the price above it, not a figure anyone
 * is meant to add up - the authoritative tax is the total further down - so it
 * reads at the weight of the Qty label opposite it rather than competing with
 * the price. `.hadc-item-row` is already space-between, so this lands hard
 * right, directly beneath the price, with no alignment rules of its own.
 */
.hadc-summary-items .hadc-item-tax {
	color: #6b7280 !important;
	flex: 0 0 auto !important;
	font-size: 12px !important;
	font-weight: 500 !important;
	line-height: 1.3 !important;
	margin-left: auto !important;
	text-align: right !important;
	white-space: nowrap !important;
}

/* The Remove link on a summary line.
 *
 * A text link, not a bin icon and not a button that looks like one. This sits
 * inside a panel the shopper opened to CHECK their order, so the destructive
 * thing in it has to be clearly secondary to everything around it - quiet
 * grey, underlined so it reads as a link, and only picking up colour on the
 * press. A red icon here would be the loudest thing on the panel.
 *
 * `margin-left: auto` puts it hard right under the price, in the same column
 * the per-item tax uses - and when both are present the tax takes that margin
 * first, so Remove follows it rather than fighting it.
 */
.hadc-summary-items .hadc-sum-remove {
	background: none !important;
	border: 0 !important;
	border-radius: 0 !important;
	box-shadow: none !important;
	color: #6b7280 !important;
	cursor: pointer !important;
	flex: 0 0 auto !important;
	font-size: 12px !important;
	font-weight: 500 !important;
	line-height: 1.3 !important;
	margin: 0 0 0 auto !important;
	min-height: 0 !important;
	min-width: 0 !important;
	padding: 2px 0 2px 10px !important;
	text-decoration: underline !important;
	text-transform: none !important;
	width: auto !important;
}

.hadc-summary-items .hadc-sum-remove:hover,
.hadc-summary-items .hadc-sum-remove:focus-visible {
	color: #b91c1c !important;
}

/* The account-creation block, belt behind no_signup().
 *
 * The PHP stops WooCommerce rendering it at all, so on a fresh page there is
 * nothing here to hide. This catches the one case the PHP cannot: a checkout
 * fragment cached in a browser from before the change, which would otherwise
 * put the tick back on a page whose server no longer offers it.
 */
.hadc-checkout-page .woocommerce-account-fields {
	display: none !important;
}

/* THE FLASH, when Continue is pressed and the answer is already on screen.
 *
 * Two beats, not a loop: long enough to catch the eye landing after a scroll,
 * short enough that it is over before it reads as an error state of its own.
 * It moves the SHADOW and the border, never the layout - a notice that grows
 * pushes the form under it and the shopper loses their place.
 *
 * `animation` is on this file's exempt list - no theme targets it, and an
 * !important here would stop the reduced-motion rule below switching it off.
 */
@keyframes hadc-notice-flash {
	0%, 100% {
		box-shadow: 0 0 0 0 rgba( 185, 28, 28, 0 );
	}
	20%, 60% {
		box-shadow: 0 0 0 4px rgba( 185, 28, 28, 0.28 );
	}
	40%, 80% {
		box-shadow: 0 0 0 0 rgba( 185, 28, 28, 0 );
	}
}

.hadc-checkout-page .woocommerce-notices-wrapper .hadc-notice-flash {
	animation: hadc-notice-flash 1.1s ease-in-out 1;
}

/* No motion: the ring stays put for the same beat instead of pulsing. The
   point is "look here", and that survives without movement. */
@media ( prefers-reduced-motion: reduce ) {
	.hadc-checkout-page .woocommerce-notices-wrapper .hadc-notice-flash {
		animation: none;
		box-shadow: 0 0 0 4px rgba( 185, 28, 28, 0.28 ) !important;
	}
}

/* Continue, while the cart is over the EU duty limit.
 *
 * Greyed rather than removed, and still clickable: a button that vanishes is a
 * shopper hunting for the way forward, and `disabled` takes the element out of
 * the tab order and silences the click that scrolls them to the reason. It
 * looks unavailable and behaves as a pointer back to the banner, which is the
 * honest version of both.
 */
body.hadc-over-limit .hadc-step-next {
	cursor: not-allowed !important;
	filter: grayscale(100%) !important;
	opacity: .45 !important;
}

/* A bundle: one card around its components.
 *
 * The box is what does the work. Without it the component rows read as three
 * ordinary lines that happen to have no Remove of their own, which is exactly
 * the misreading this change exists to stop - the shopper has to see that the
 * group is the thing being bought and the thing being removed.
 */
.hadc-summary-items .hadc-sum-bundle {
	background: #fafafa !important;
	border: 1px solid #e5e7eb !important;
	border-radius: 12px !important;
	display: block !important;
	list-style: none !important;

	/*
	 * Inset to the same 16px the plain rows are padded to, so the card's edge
	 * lines up with the text above it instead of running into the panel's own
	 * sides. Without this the card reads as a panel inside a panel with no
	 * gap, which is the one thing that made the grouping look like a mistake.
	 */
	margin: 10px 16px 12px !important;
	padding: 10px 12px !important;
}

.hadc-summary-items .hadc-sum-bundle-head {
	align-items: baseline !important;
	display: flex !important;
	gap: 10px !important;
	justify-content: space-between !important;
}

.hadc-summary-items .hadc-sum-bundle-label {
	color: #111111 !important;
	flex: 1 1 auto !important;
	font-size: 14px !important;
	font-weight: 700 !important;
	line-height: 1.3 !important;
	min-width: 0 !important;
}

/* The component list, inset so it reads as contents rather than siblings. */
.hadc-summary-items .hadc-sum-bundle-items {
	list-style: none !important;
	margin: 8px 0 0 !important;
	padding: 0 !important;
}

/* A component. No price of its own: the card's price is what is charged, and
   a per-line figure next to it is the question "do these add up?" that the
   bundle discount can only answer confusingly. */
.hadc-summary-items .hadc-sum-part {
	border: 0 !important;
	padding: 6px 0 !important;
}

.hadc-summary-items .hadc-sum-bundle-foot {
	display: flex !important;
	justify-content: flex-end !important;
	margin-top: 4px !important;
}

/* Taken out, and on its way. The row is removed by the server a moment later
   when the fragment comes back; this is only so the tap feels answered. */
.hadc-summary-items .hadc-sum-bundle.is-going {
	opacity: .4 !important;
	pointer-events: none !important;
}

.hadc-summary-items .hadc-item.is-going {
	opacity: .4 !important;
	pointer-events: none !important;
}

/* ===========================================================================
 * Step 2's order table: shipping choice and total, nothing else.
 *
 * The summary bar at the top now carries the line items with thumbnails, so
 * repeating "Product / Subtotal" underneath is the same information twice -
 * and the duplicate is the one without pictures.
 *
 * The rows are HIDDEN rather than removed. WooCommerce rebuilds this table on
 * every recalculation and reads it back on submit; deleting rows from it is
 * the kind of change that works until the day a tax line matters.
 * ======================================================================== */
.hadc-checkout-page .woocommerce-checkout-review-order-table thead,
.hadc-checkout-page .woocommerce-checkout-review-order-table tr.cart_item,
.hadc-checkout-page .woocommerce-checkout-review-order-table tr.cart-subtotal,
/* The total goes too.
 *
 * Step 2 was showing it twice: once in the summary bar at the top of the page,
 * and again at the bottom of this table, directly above Continue. Two figures
 * saying the same thing is one too many, and the lower one is the worse of the
 * pair - it sits where a shopper is about to press a button, so it reads as
 * "this is what you are agreeing to" on a step that agrees to nothing.
 *
 * The summary bar is the one that stays: it is live, it is at the top where it
 * can be checked at any point, and it opens to show what the money is made of.
 *
 * The row is HIDDEN, not removed - the same reason as the rows above it.
 * WooCommerce rebuilds this table on every recalculation and reads it back on
 * submit, and `tr.order-total td` is also where checkout-steps.js used to read
 * the total from. Deleting it works right up until something wants it. */
.hadc-checkout-page .woocommerce-checkout-review-order-table tr.order-total {
	display: none !important;
}

/* "Your order" goes with them - the bar above already says what this is. */
.hadc-checkout-page #order_review_heading {
	display: none !important;
}

/* ---------------------------------------------------------------------------
 * THE SHIPPING CARDS WERE ~70% WIDE. Here is why, and the real fix.
 *
 * A table lays its columns out together: the shipping row's `td` shares its
 * width with the money column of every other row, so the rate cards were
 * confined to whatever width the prices needed - about two thirds - no matter
 * what width the list inside was given.
 *
 * Setting display:block on the row alone was not enough, because the TABLE
 * was still a table and still sizing its columns. So the table itself drops
 * out of table layout. It can: with the line items hidden, all that is left is
 * the shipping choice and the total, and neither wants columns.
 * ------------------------------------------------------------------------ */
.hadc-checkout-page .woocommerce-checkout-review-order-table,
.hadc-checkout-page .woocommerce-checkout-review-order-table tbody,
.hadc-checkout-page .woocommerce-checkout-review-order-table tfoot,
.hadc-checkout-page .woocommerce-checkout-review-order-table tr,
.hadc-checkout-page .woocommerce-checkout-review-order-table th,
.hadc-checkout-page .woocommerce-checkout-review-order-table td {
	border-collapse: collapse !important;
	display: block !important;
	width: 100% !important;
}

.hadc-checkout-page tr.woocommerce-shipping-totals th {
	border: 0 !important;
	padding: 4px 0 8px !important;
}

.hadc-checkout-page tr.woocommerce-shipping-totals td {
	border: 0 !important;
	max-width: none !important;
	padding: 0 0 4px !important;
}

.hadc-checkout-page ul#shipping_method {
	box-sizing: border-box !important;
	max-width: none !important;
	width: 100% !important;
}

/* Rows that are a label and a figure become flex, so they keep reading as two
   columns now that the table no longer provides any.
   `tr.order-total` was in this list and had to come OUT: it is hidden further
   up now, and a `display: flex` of equal specificity sitting LOWER in the file
   would have beaten `display: none` and put the total straight back. Same trap
   that re-showed the shipping rows in 0.17.1. */
.hadc-checkout-page .woocommerce-checkout-review-order-table tr.tax-rate,
.hadc-checkout-page .woocommerce-checkout-review-order-table tr.fee {
	align-items: baseline !important;
	display: flex !important;
	justify-content: space-between !important;
	gap: 12px !important;
}

.hadc-checkout-page .woocommerce-checkout-review-order-table tr.tax-rate th,
.hadc-checkout-page .woocommerce-checkout-review-order-table tr.tax-rate td,
.hadc-checkout-page .woocommerce-checkout-review-order-table tr.fee th,
.hadc-checkout-page .woocommerce-checkout-review-order-table tr.fee td {
	width: auto !important;
}

.hadc-checkout-page .woocommerce-checkout-review-order-table tr.tax-rate td,
.hadc-checkout-page .woocommerce-checkout-review-order-table tr.fee td {
	text-align: right !important;
}

/* ===========================================================================
 * STEP HIDING WINS. ALWAYS. Put last on purpose.
 *
 * 0.17.1 broke this. Dropping the review table out of table layout meant
 * writing `display: block !important` on the table, its rows and its cells -
 * and that rule has the SAME specificity as `.hadc-checkout-page
 * .hadc-step-hide`, so the later one won. It came later, so the table ignored
 * the step flow entirely and the shipping options appeared on steps 1 and 3.
 *
 * Two rules of equal weight fighting over the same element is a coin toss
 * decided by file order, which is not something to leave to chance in a
 * stylesheet this long. So the hide rule is restated at the END of the file,
 * where nothing can come after it, and against the specific elements that
 * need it rather than relying on the generic one.
 *
 * THE PRINCIPLE: a pane that is not on the current step must never be visible,
 * whatever any layout rule says. Visibility is a correctness concern here, not
 * a cosmetic one - a shopper who can see the shipping options on step 1 can
 * change them before the address that prices them has been entered.
 * ======================================================================== */
.hadc-checkout-page .hadc-step-hide,
.hadc-checkout-page table.hadc-step-hide,
.hadc-checkout-page .woocommerce-checkout-review-order-table.hadc-step-hide,
.hadc-checkout-page #payment.hadc-step-hide,
.hadc-checkout-page .hadc-delivery-card.hadc-step-hide,
.hadc-checkout-page #customer_details .col-1.hadc-step-hide,
.hadc-checkout-page #customer_details .col-2.hadc-step-hide,
.hadc-step-nav.hadc-step-hide,
.hadc-step-back-last.hadc-step-hide {
	display: none !important;
}

/* The rate cards line up with the delivery card above them.
 *
 * The table kept the 16px of padding it was given back when it was styled as a
 * card in its own right - which inset the shipping options relative to every
 * other card on the step and made them look narrower than they are. It is not
 * a card any more, so it carries no padding. */
.hadc-checkout-page .woocommerce-checkout-review-order-table {
	background: transparent !important;
	border: 0 !important;
	border-radius: 0 !important;
	margin: 0 0 14px !important;
	padding: 0 !important;
}

/* VAT out of the shipping block.
 *
 * WooCommerce prints the tax rows straight after the shipping rows, so on step
 * 2 a tax line landed directly under the rate cards - reading as part of the
 * question the shopper is answering, as though choosing a courier changed the
 * VAT. It did not; the destination did. The summary dropdown carries it now,
 * beside the subtotal and the total it actually belongs to.
 *
 * Hidden, not removed: WooCommerce rebuilds and re-reads this table, and a tax
 * line is not something to delete from a checkout to tidy a layout. */
.hadc-checkout-page .woocommerce-checkout-review-order-table tr.tax-rate,
.hadc-checkout-page .woocommerce-checkout-review-order-table tr.tax-total {
	display: none !important;
}

/* ---------------------------------------------------------------------------
 * "COMPLETING YOUR PAYMENT" — the cover between authorising and the thank-you
 * page.
 *
 * Shown by paying() in checkout.js the moment the checkout form is submitted,
 * which is also the moment an Apple Pay or Google Pay sheet hands back. See
 * the note there for why that window must not look idle.
 *
 * Fixed and over everything, because the point is that nothing else can be
 * pressed - least of all Place order a second time.
 * ------------------------------------------------------------------------ */
/* ---------------------------------------------------------------------------
 * THE CHECKOUT WITH NOTHING IN IT.
 *
 * Centred, quiet, and one way onward. It replaces a bounce to the theme's cart
 * page, which carried the site header, the full footer and WooCommerce's grey
 * notice - a different website as far as the shopper is concerned, arrived at
 * by pressing Remove in ours.
 * ------------------------------------------------------------------------ */
.hadc-empty {
	align-items: center !important;
	display: flex !important;
	flex-direction: column !important;
	padding: 48px 20px 64px !important;
	text-align: center !important;
}

/* An empty bag, drawn rather than shipped: one less asset to cache-bust, and
   it cannot arrive after the text it belongs to. */
.hadc-empty-mark {
	border: 2px solid #d1d5db !important;
	border-radius: 6px 6px 14px 14px !important;
	display: block !important;
	height: 46px !important;
	margin-bottom: 20px !important;
	position: relative !important;
	width: 56px !important;
}

.hadc-empty-mark::before {
	border: 2px solid #d1d5db !important;
	border-bottom: 0 !important;
	border-radius: 10px 10px 0 0 !important;
	content: '' !important;
	height: 12px !important;
	left: 50% !important;
	position: absolute !important;
	top: -12px !important;
	transform: translateX( -50% ) !important;
	width: 24px !important;
}

.hadc-empty-title {
	color: #111111 !important;
	font-size: 22px !important;
	font-weight: 800 !important;
	line-height: 1.25 !important;
	margin: 0 0 8px !important;
}

.hadc-empty-text {
	color: #4b5563 !important;
	font-size: 15px !important;
	line-height: 1.5 !important;
	margin: 0 0 24px !important;
	max-width: 420px !important;
}

/* The same black pill as Continue, because it is the same kind of thing: the
   one action on the screen. */
.hadc-empty-cta {
	background: #111111 !important;
	border: 0 !important;
	border-radius: 999px !important;
	color: #ffffff !important;
	display: inline-block !important;
	font-size: 16px !important;
	font-weight: 700 !important;
	padding: 14px 28px !important;
	text-decoration: none !important;
}

.hadc-empty-cta:hover,
.hadc-empty-cta:focus {
	background: #000000 !important;
	color: #ffffff !important;
}

/* ---------------------------------------------------------------------------
 * THE GREEN NOTICE.
 *
 * Deliberately the same shape as the red one EAS prints above it, so the
 * shopper reads it as the same thing having changed its mind rather than as a
 * new element arriving. Every property carries !important for the usual
 * reason: Elementor restyles bordered boxes inside shortcode output and loads
 * after this file.
 * ------------------------------------------------------------------------ */
.hadc-ok-notice {
	background: #ecfdf5 !important;
	border: 1px solid #a7f3d0 !important;
	border-radius: 12px !important;
	color: #065f46 !important;
	font-size: 15px !important;
	font-weight: 600 !important;
	line-height: 1.45 !important;
	margin: 0 0 14px !important;
	padding: 14px 16px !important;
}

/*
 * ANCHORED FROM THE TOP, NOT CENTRED IN THE VIEWPORT.
 *
 * It used to centre itself between top:0 and bottom:0, which on a phone is not
 * a fixed distance: Safari's address bar retracts and expands, and the visual
 * viewport changes height underneath a `position: fixed` element. The box
 * tracked the middle of whatever was left, so the words moved up or down
 * between one phase and the next - and a reload, which always brings the
 * address bar back, moved them every time.
 *
 * `vh` is measured against the LARGE viewport - the page as if the toolbars
 * were hidden - so it does not change when they come and go. A fixed fraction
 * of it puts the box in the same place on every paint, on every screen.
 */
.hadc-paying {
	align-items: flex-start !important;
	background: rgba( 255, 255, 255, 0.92 ) !important;
	bottom: 0 !important;
	display: none !important;
	justify-content: center !important;
	left: 0 !important;
	padding: 24px !important;
	position: fixed !important;
	right: 0 !important;
	top: 0 !important;
	z-index: 2147483000 !important;
}

.hadc-paying.is-on {
	display: flex !important;
}

/* Scrolling underneath a cover is movement the shopper did not ask for and
   cannot act on. */
body.hadc-is-paying {
	overflow: hidden !important;
}

/*
 * ONE SHAPE FOR EVERY WAITING STATE.
 *
 * The box is a fixed width and the two lines have reserved heights, so the
 * spinner, the title and the note sit at exactly the same place on the screen
 * in every phase and in both languages. Before this, a title that wrapped to
 * two lines in Latvian pushed everything up relative to a title that did not,
 * and a phase with no second line sat lower still: the words changed, so the
 * layout moved, so one wait looked like several.
 *
 * Width rather than max-width for the same reason - a shorter sentence used to
 * draw a narrower box.
 */
.hadc-paying-box {
	align-items: center !important;
	display: flex !important;
	flex-direction: column !important;
	gap: 6px !important;
	justify-content: flex-start !important;
	margin-top: 32vh !important;
	text-align: center !important;
	width: 320px !important;
	max-width: 100% !important;
}

/* The one spin in this stylesheet, and it lives next to its only user now.
 *
 * It used to be declared down by the Continue button's spinner, which is the
 * rule 0.36.2 deleted - taking the keyframes with it and leaving this circle
 * sitting perfectly still over a payment. Declared here it cannot be orphaned
 * by removing something else. */
@keyframes hadc-spin {
	to {
		transform: rotate( 360deg );
	}
}

.hadc-paying-spin {
	animation: hadc-spin 0.7s linear infinite !important;
	border: 3px solid rgba( 17, 17, 17, 0.15 ) !important;
	border-radius: 50% !important;
	border-top-color: #111111 !important;
	display: block !important;
	height: 34px !important;
	margin-bottom: 4px !important;
	width: 34px !important;
}

/*
 * THE FONT IS NAMED HERE, AND THAT IS THE POINT.
 *
 * Nothing else in this stylesheet sets a family - the checkout inherits the
 * theme's, which is a WEBFONT. The cover raised before the first paint of a
 * reloaded page is drawn before that font has loaded, so it came up in the
 * browser's fallback - heavier and wider - and then the next phase, with the
 * font in cache, came up lighter. Same markup, same rules, two different
 * looking screens, purely because of when each one was painted.
 *
 * A system stack is in the browser already, so it is identical in both paints.
 * 700 rather than 800 because a stack with no 800 face gets a SYNTHETIC bold,
 * which is the other half of why one of them looked heavier.
 */
.hadc-paying-title {
	color: #111111 !important;
	font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Helvetica, Arial, sans-serif !important;
	font-size: 17px !important;
	font-weight: 700 !important;
	line-height: 1.3 !important;

	/*
	 * NO RESERVED SECOND LINE ANY MORE. There is one sentence per language on
	 * this cover now, so there is nothing left to reserve space for - and
	 * reserving it was visible: after a title that fits on one line, the empty
	 * half of the reserved block sat on top of the gap and pushed the second
	 * line most of a line-height too far down.
	 */
}

.hadc-paying-note {
	color: #4b5563 !important;
	font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Helvetica, Arial, sans-serif !important;
	font-size: 14px !important;
	font-weight: 400 !important;
	line-height: 1.4 !important;

	/* One line's worth, held even when the note is empty, so a phase that
	   somehow has no note does not change the height of the box. */
	min-height: 20px !important;
}

/* Reduced motion: keep the cover and the words, drop the spin. The message is
   the part that matters. */
@media ( prefers-reduced-motion: reduce ) {
	.hadc-paying-spin {
		animation: none !important;
	}
}
