/**
 * Pro frontend styles.
 *
 * Pro had no frontend stylesheet at all. Every panel it rendered on the
 * storefront carried its colours as inline style attributes - a light blue
 * fill, an indigo rule, three greys - written straight into the PHP. That had
 * three consequences, all of them invisible until someone changed a theme:
 *
 *   1. Dark mode could not reach them. The store went dark, the free plugin's
 *      card went dark with it, and Pro's volume-discount panel stayed light
 *      blue while its text followed the theme to light grey. Measured 1.49:1.
 *   2. The store's brand could not reach them either. The panel was #2196f3
 *      blue on a store whose accent was something else entirely.
 *   3. `border-left` is a physical property, so on an RTL store the accent rule
 *      sat on the wrong edge.
 *
 * Everything here resolves through the FREE plugin's --wcpq-* tokens, so Pro
 * follows the same theme chain and the same dark mode as the rest of the quote
 * UI, with no colour of its own to keep in sync. The stylesheet declares the
 * token sheet as a dependency, so those variables are always defined by the
 * time this loads.
 *
 * Email HTML is deliberately NOT covered here - mail clients strip <style>, so
 * the inline styles in the email builders are correct and stay where they are.
 *
 * @package Woocommerce_Price_Quote_Pro
 * @since   2.1.1
 */

/* Volume and role discount panels, shown above the submit area on the quote
 * form. The role panel tells the signed-in customer about their personal
 * discount and shares the volume panel's styling so the two read as one system. */
.wcpq-volume-discount-info,
.wcpq-role-discount-info {
	margin: var(--wcpq-space-md) 0;
	padding: var(--wcpq-space-md);
	background: var(--wcpq-surface-subtle);
	border-inline-start: 4px solid var(--wcpq-accent);
	border-radius: var(--wcpq-radius-sm);
	color: var(--wcpq-text);
}

/*
 * The heading takes the normal text colour, NOT the accent.
 *
 * Accent-as-text was measured at 4.17:1 on this store - under the 4.5 floor -
 * and that store's accent is a fairly dark blue. The accent token is tuned to
 * sit BEHIND white text as a fill, so its contrast as text depends entirely on
 * how dark the owner's brand colour happens to be: a yellow or pale-green
 * accent would fail far harder than this one did, on a store we never see.
 *
 * The panel still reads as branded - the accent lives on the border rule below,
 * where it is decorative and carries no contrast requirement.
 */
.wcpq-volume-discount-info__heading,
.wcpq-role-discount-info__heading {
	margin: 0 0 var(--wcpq-space-sm);
	color: var(--wcpq-text);
	font-size: 1.05em;
}

.wcpq-volume-discount-info__intro,
.wcpq-role-discount-info__intro {
	margin: 0 0 var(--wcpq-space-sm);
	color: var(--wcpq-text-muted);
}

/* The role panel has no bottom-margin intro list, so drop its last-child gap. */
.wcpq-role-discount-info__intro:last-child {
	margin-bottom: 0;
}

.wcpq-volume-discount-info__tiers {
	margin: 0;
	padding-inline-start: var(--wcpq-space-lg);
	color: var(--wcpq-text);
}

/* File-upload hint under the attachment field. */
.wpq-field-hint {
	display: block;
	margin-top: var(--wcpq-space-xs);
	color: var(--wcpq-text-muted);
}

/*
 * Owner-only configuration warning (an unconfigured reCAPTCHA, for example).
 * Only administrators ever see it, but it renders on the storefront, so it
 * needs the same dark-mode treatment as everything else.
 */
.wcpq-pro-notice--error {
	color: var(--wcpq-error);
}

/*
 * Submission errors rendered by wcpq-pro-public.js.
 *
 * The class is applied by the script; the script no longer carries the colours.
 */
.wcpq-pro-error-message {
	margin: var(--wcpq-space-sm) 0;
	padding: var(--wcpq-space-sm) var(--wcpq-space-md);
	background: var(--wcpq-error-bg);
	border: 1px solid var(--wcpq-error);
	border-radius: var(--wcpq-radius-sm);
	color: var(--wcpq-error);
}
