/* Prevents a layout shift (fields appearing to change width) whenever page
   content height changes enough to make a scrollbar appear/disappear - e.g.
   revealing the Forgot Password panel. Reserving the scrollbar's width
   permanently means it's always accounted for, so nothing ever reflows
   because of it. */
html { scrollbar-gutter: stable; overflow-y: scroll; }

.sp-form-heading { margin: 0 0 0.8em; font-size: 1.3em; font-weight: 700; }
.sp-account-header { display: flex; align-items: center; justify-content: space-between; gap: 1em; }
.sp-account-header .sp-form-heading { margin: 0; }
.sp-required-note { font-size: 0.85em; color: #666; margin: 1em 0; }
.sp-required-marker { color: #d63638; font-weight: 700; }

/* Centres the form horizontally whenever its max-width (above/below) ends up
   narrower than the space Elementor gives its wrapper - e.g. once the Login
   Form widget's "Align Self" (Advanced tab) is set to Stretch so the new
   Form Width control has room to work, the widget wrapper spans the full
   row but the form itself stops at its max-width, and would otherwise sit
   flush against the left edge of that row rather than centred in it. Auto
   left/right margins are a no-op when the form is already as wide as its
   container (e.g. Align Self left at its default), so this is safe either
   way and doesn't depend on which Align Self setting is chosen. */
.sp-form { max-width: 420px; margin-left: auto; margin-right: auto; }

/* Same variable-with-fallback pattern as .sp-register-form below: the
   Login Form widget's own "Max Width" control (Style tab) sets
   --sp-form-max-width inline, scoped to that one widget instance, so
   widening one login form on the site never affects another instance or
   the register form (which reads the same variable name but always gets
   its own value, since Elementor scopes the inline custom property to
   {{WRAPPER}}). Falls back to the plain .sp-form 420px above when the
   control is left at its default. Must come after .sp-form (same
   specificity - a single class each - so source order decides), and
   .sp-login-form specifically rather than broadening .sp-form itself,
   so the fallback for a login form widget that never gets this control
   stays exactly what it always was. */
.sp-login-form { max-width: var(--sp-form-max-width, 420px); }

/* Registration has a lot of fields - lay them out in a responsive grid
   (auto-fit wraps to however many columns fit, and collapses to one
   column on narrow screens automatically, no media queries needed)
   instead of one long single-column form down the middle of the page. */
.sp-register-form {
	max-width: var(--sp-form-max-width, 900px);
	display: grid;
	grid-template-columns: repeat(auto-fit, minmax(240px, 1fr));
	column-gap: 1.5em;
}
.sp-register-form > .sp-required-note,
.sp-register-form > .sp-message,
.sp-register-form .sp-field-full {
	grid-column: 1 / -1;
}

.sp-password-strength { display: flex; align-items: center; gap: 8px; margin-top: 6px; }
.sp-strength-bar { flex: 1; height: 6px; background: #e0e0e0; border-radius: 3px; overflow: hidden; }
.sp-strength-bar-fill { height: 100%; width: 0; transition: width 0.2s ease, background-color 0.2s ease; }
.sp-strength-label { font-size: 0.8em; font-weight: 600; min-width: 80px; }
.sp-password-requirements { font-size: 0.8em; color: #666; margin: 4px 0 0; }

.sp-password-wrapper { position: relative; display: block; width: 100%; }
.sp-password-wrapper input[type="password"],
.sp-password-wrapper input[type="text"] { padding-right: 40px; box-sizing: border-box; width: 100%; }
.sp-password-toggle {
	position: absolute;
	right: 6px;
	top: 50%;
	transform: translateY(-50%);
	background: none;
	border: none;
	color: #666;
	cursor: pointer;
	padding: 4px;
	display: flex;
	align-items: center;
	justify-content: center;
	line-height: 0;
}
.sp-password-toggle:hover { color: #2271b1; }
.sp-field { margin-bottom: 1em; }
.sp-field label { display: block; margin-bottom: 0.3em; font-weight: 600; }
.sp-field input { width: 100%; padding: 0.6em; box-sizing: border-box; }
.sp-field input:disabled { background: #f0f0f1; color: #666; cursor: not-allowed; }
.sp-button {
	display: inline-block;
	padding: 0.7em 1.4em;
	border: none;
	border-radius: 4px;
	background: var(--e-global-color-primary, #2271b1);
	color: #fff;
	cursor: pointer;
	text-decoration: none;
	font-weight: 600;
	transition: background-color 0.15s ease, color 0.15s ease, transform 0.1s ease;
}
.sp-button-secondary { background: #6c757d; }
.sp-button-loading, .sp-button:disabled { opacity: 0.65; cursor: not-allowed; }

/* Rendered as a <button> (not an <a>) so there's no href for the browser to preview on
   hover - here it needs to look like an inline text link, not a boxed button. */
.sp-link-button {
	background: none;
	border: none;
	padding: 0;
	margin: 0;
	font: inherit;
	color: #2271b1;
	text-decoration: underline;
	cursor: pointer;
}
.sp-link-button:hover { color: #135e96; }
.sp-notice { padding: 0.8em 1em; background: #f0f0f1; border-left: 4px solid #2271b1; }
.sp-message { margin-top: 1em; padding: 0.6em 1em; border-radius: 4px; }
.sp-message.sp-success { background: #d1e7dd; color: #0f5132; }
.sp-message.sp-error { background: #f8d7da; color: #842029; }
/* Added 2026-09-30, per Martin: on the account page, the "2FA required"
   notice sits directly under the profile form's own success/error message
   (.sp-message, inside the form) with no gap between the two boxes.
   Scoped to just this one adjacent-sibling case (the account() shortcode's
   markup) rather than a blanket .sp-notice margin-top, so it doesn't add
   unwanted spacing to every other .sp-notice usage on the site (My
   Downloads/My Courses empty states, the "already logged in" notice, etc). */
.sp-profile-form + .sp-notice { margin-top: 1em; }

.sp-download-item {
	border: 1px solid #e0e0e0;
	border-radius: 6px;
	padding: 1em 1.2em;
	margin-bottom: 1em;
	display: flex;
	gap: 1em;
	align-items: flex-start;
}
.sp-download-icon img { width: 56px; height: 56px; object-fit: cover; border-radius: 4px; }
.sp-download-body { flex: 1; }
.sp-download-title { font-weight: 700; font-size: 1.1em; margin-bottom: 0.2em; }
.sp-download-meta { font-size: 0.85em; color: #666; margin-bottom: 0.6em; }
.sp-download-meta .sp-download-version { font-weight: 600; margin-right: 1em; }
.sp-download-desc { margin-bottom: 0.8em; color: #444; }

.sp-2fa-challenge, #sp-2fa-totp-setup { max-width: 420px; margin-top: 1.5em; }
.sp-2fa-resend { margin: 0.5em 0 0; font-size: 0.9em; }
#sp-2fa-qr-code { margin: 0.8em 0; }
.sp-2fa-secret-text { font-family: monospace; font-size: 1.1em; background: #f0f0f1; padding: 0.5em 0.8em; border-radius: 4px; letter-spacing: 1px; word-break: break-all; }
.sp-2fa-options .sp-button { margin-right: 0.5em; margin-bottom: 0.5em; }
/* Added 2026-09-28, per Martin: every button on the standalone [sp_2fa_setup]
   page should read in uppercase - widened from an earlier version of this
   rule that only covered the "Use email codes instead" button, once Martin
   asked for all of them. Scoped to .sp-2fa-setup-shortcode (the wrapper
   class SP_Shortcodes::two_factor_setup() renders itself in) rather than
   .sp-button generally, since [sp_account] renders this exact same
   render_2fa_panel() markup/IDs for Customers and was NOT asked to change -
   without that scoping class there'd be no way to tell the two apart, since
   both render identical HTML otherwise. Done with text-transform rather
   than uppercasing the PHP strings themselves, so the underlying
   translatable text stays normal sentence case for translators/screen
   readers - only the visual rendering changes. */
.sp-2fa-setup-shortcode .sp-button { text-transform: uppercase; }

/* Added 2026-09-29, per Martin: explicit brand colours for the /choose-access/
   chooser page's two buttons (Sidekick Admin / StockDB Panel), rendered by
   SP_Redirects::render_panel_chooser_page() - matches the RTGL colour
   scheme's Primary CTA (#FF0000) and its hover (#CC0000), with the same
   light text colour (#F8F9FA) in both states and uppercase text. Scoped to
   .sp-choose-access-page (the wrapper class that method renders itself in)
   rather than .sp-button generally, same reasoning as the
   .sp-2fa-setup-shortcode scoping just above - this page's buttons are the
   only ones that should look like this, not every .sp-button on the site. */
.sp-choose-access-page .sp-button {
	background: #FF0000;
	color: #F8F9FA;
	text-transform: uppercase;
}
.sp-choose-access-page .sp-button:hover {
	background: #CC0000;
	color: #F8F9FA;
}

/* Same fix as the .sp-form comment above, for the two panels that live
   alongside the login form rather than inside it (SP_Shortcodes::login_form()
   renders .sp-2fa-challenge and .sp-forgot-password-panel as siblings of
   the <form class="sp-form">, not inside it, so they never inherited that
   rule's centring). Deliberately NOT applied to #sp-2fa-totp-setup, which
   only appears inside the account/profile settings page - a different,
   already-wide layout context this hasn't been reported as affecting. */
.sp-2fa-challenge { margin-left: auto; margin-right: auto; }

.sp-forgot-password-link { margin-top: 0.5em; }
.sp-forgot-password-link a { font-size: 0.9em; }
.sp-forgot-password-panel { max-width: 420px; margin-top: 1em; padding: 1em; border: 1px solid #e0e0e0; border-radius: 6px; margin-left: auto; margin-right: auto; }

.sp-popup-overlay {
	position: fixed;
	top: 0; left: 0; right: 0; bottom: 0;
	background: rgba(0, 0, 0, 0.5);
	display: flex;
	align-items: center;
	justify-content: center;
	z-index: 999999;
}
.sp-popup-box {
	background: #fff;
	border-radius: 8px;
	padding: 2em;
	max-width: 420px;
	width: 90%;
	text-align: center;
	box-shadow: 0 10px 40px rgba(0,0,0,0.2);
}
.sp-popup-box p { margin: 0 0 1.2em; font-size: 1.05em; line-height: 1.5; }
/* Added 2026-09-29, per Martin: the registration confirmation popup's Close
   button should read in uppercase - text-transform rather than uppercasing
   the JS string itself, same reasoning as the other uppercase rules in this
   file (translatable text stays normal sentence case; only the rendering
   changes). This popup is shared by showPopup() generally, so this affects
   any future use of it too, not just registration - fine since every
   current use of a Close button here should look the same. */
.sp-popup-close { text-transform: uppercase; }

.sp-folder-tree .sp-folder { margin-bottom: 0.4em; }
.sp-folder-header {
	display: flex;
	align-items: center;
	gap: 0.5em;
	padding: 0.6em 0.8em;
	background: #f6f7f7;
	border: 1px solid #e0e0e0;
	border-radius: 6px;
	cursor: pointer;
	font-weight: 600;
	user-select: none;
}
.sp-folder-toggle { display: inline-block; width: 1em; }
/* Groups Download All + the file-count badge together and pins the GROUP
   flush to the header's right edge (margin-left: auto lives here, on the
   wrapper, not on the badge itself) - so the badge always sits right next
   to Download All rather than the two ending up stranded at opposite ends
   of the row, and the group's position doesn't depend on whether the
   button inside it happens to be visible, so nothing jumps when a folder
   is expanded or collapsed. */
.sp-folder-header-right {
	margin-left: auto;
	display: flex;
	align-items: center;
	gap: 0.5em;
}
.sp-folder-count {
	background: #e0e0e0;
	border-radius: 10px;
	padding: 0.2em 0.7em;
	font-weight: 600;
	display: flex;
	flex-direction: column;
	align-items: center;
	line-height: 1.15;
	text-align: center;
}
.sp-folder-count-number { font-size: 0.95em; }
.sp-folder-count-label {
	font-size: 0.65em;
	font-weight: 500;
	text-transform: uppercase;
	letter-spacing: 0.03em;
	opacity: 0.75;
}
.sp-folder-contents { margin-top: 0.5em; }
.sp-folder-collapsed > .sp-folder-contents { display: none; }
/* Download All sits to the left of the file-count badge, both grouped
   together via .sp-folder-header-right above. Only shows once the
   folder's been opened, so it's a look-then-download action rather than
   something to click blind. */
.sp-folder-collapsed > .sp-folder-header .sp-download-all { display: none; }
.sp-download-all {
	flex-shrink: 0;
	padding: 0.4em 0.9em;
	font-size: 0.85em;
	font-weight: 600;
}

/* Training tab - My Courses cards. Same card shape as .sp-download-item on
   purpose, so the two tabs feel like one system. */
.sp-course-item {
	border: 1px solid #e0e0e0;
	border-radius: 6px;
	padding: 1em 1.2em;
	margin-bottom: 1em;
	display: flex;
	gap: 1em;
	align-items: flex-start;
}
.sp-course-thumb img { width: 96px; height: 64px; object-fit: cover; border-radius: 4px; }
.sp-course-body { flex: 1; }
.sp-course-title { font-weight: 700; font-size: 1.1em; margin-bottom: 0.3em; }
.sp-course-meta { margin-bottom: 0.6em; }
.sp-course-status {
	display: inline-block;
	font-size: 0.75em;
	font-weight: 600;
	text-transform: uppercase;
	letter-spacing: 0.03em;
	padding: 0.2em 0.7em;
	border-radius: 10px;
	background: #e0e0e0;
}
.sp-course-status-not-started { background: #e0e0e0; color: #444; }
.sp-course-status-progress { background: #fff3cd; color: #664d03; }
.sp-course-status-completed { background: #d1e7dd; color: #0f5132; }
.sp-course-desc { margin-bottom: 0.8em; color: #444; }
.sp-course-button { display: inline-block; }

/* Help Center (self-service FAQ/knowledge base) - see class-sp-shortcodes.php
   help_center()/render_faq_item() and assets/js/help-center.js. All search/
   filter/accordion behaviour is plain client-side JS against these classes;
   there's no AJAX involved. */
/* width:100% (not just max-width) is what stops the whole widget shrinking
   to fit its narrowest visible content - without it, filtering the list down
   to fewer/shorter cards let the block shrink-wrap in some layouts (seen
   live: the box visibly narrows when a category with only one short
   question is selected), since a block child with only a max-width doesn't
   reliably fill its container in every flex/grid context Elementor can put
   it in. No max-width here (unlike .sp-form/.sp-register-form, which are
   deliberately narrow login/registration forms) - like .sp-downloads-list,
   .sp-courses-list and .sp-account, this is tab CONTENT and should fill
   whatever width its container gives it, full stop. Confirmed live: capping
   it at --sp-form-max-width (900px) was exactly why it wouldn't go full
   width like the other tabs on a wider container. */
.sp-help-center { width: 100%; box-sizing: border-box; }
.sp-faq-search {
	width: 100%;
	padding: 0.7em 1em;
	box-sizing: border-box;
	border: 1px solid #e0e0e0;
	border-radius: 6px;
	font-size: 1em;
	margin-bottom: 1em;
}
.sp-faq-categories {
	display: flex;
	flex-wrap: wrap;
	gap: 0.5em;
	margin-bottom: 1.2em;
}
.sp-faq-category-pill {
	display: inline-block;
	padding: 0.35em 1em;
	border-radius: 20px;
	background: #f0f0f1;
	color: #444;
	font-size: 0.85em;
	font-weight: 600;
	cursor: pointer;
	border: 1px solid transparent;
	user-select: none;
	transition: background-color 0.15s ease, color 0.15s ease;
}
.sp-faq-category-pill:hover { background: #e0e0e0; }
.sp-faq-category-pill.active {
	background: var(--e-global-color-primary, #2271b1);
	color: #fff;
}
.sp-faq-item {
	border: 1px solid #e0e0e0;
	border-radius: 6px;
	margin-bottom: 0.8em;
	box-shadow: 0 1px 2px rgba(0,0,0,0.03);
	overflow: hidden;
}
/* Rendered as a <button> (see SP_Shortcodes::render_faq_item()), so button
   chrome is stripped back to a plain full-width row first. "body"-prefixed
   for specificity insurance, same pattern as the LearnPress overrides
   further down this file - the theme has its own generic `button {...}`
   styling (confirmed live: without this, question rows inherited the
   theme's default button colours instead of these), and a plain
   `.sp-faq-question` rule isn't reliably guaranteed to win against it
   depending on the theme's own selectors. Elementor's own Style-tab output
   (see class-widget-help-center.php's button_style_section() call) is
   scoped with an ID selector and always outranks this regardless. */
body .sp-faq-question {
	display: flex;
	align-items: center;
	justify-content: space-between;
	gap: 1em;
	width: 100%;
	padding: 1em 1.2em;
	margin: 0;
	background: transparent;
	border: none;
	font: inherit;
	font-weight: 700;
	font-size: 1em;
	text-align: left;
	color: #1a1a1a;
	cursor: pointer;
	user-select: none;
	transition: background-color 0.15s ease;
}
body .sp-faq-question:hover { background: #f6f7f7; }
/* The currently-open/expanded question - a distinct default from the plain
   hover state above, and from the theme's button styling (see the "body"
   prefix note above), so it's visually obvious which card is expanded.
   Higher specificity (3 classes) than the hover rule above, so this wins
   even while hovering an already-open question. Elementor's own "Active"
   tab (see class-widget-help-center.php's button_style_section() call, and
   SP_Elementor_Widget_Base::button_style_section()'s active_selector
   option) overrides this via an ID-scoped selector, same as every other
   Style-tab control here. */
body .sp-faq-item.open .sp-faq-question { background: #f0f6fc; }
/* Plain CSS chevron (no separate icon element/asset) that rotates to point
   up once help-center.js toggles .open onto the item. */
.sp-faq-question::after {
	content: '';
	flex-shrink: 0;
	width: 0.5em;
	height: 0.5em;
	border-right: 2px solid #666;
	border-bottom: 2px solid #666;
	transform: rotate(45deg);
	transition: transform 0.2s ease;
}
.sp-faq-item.open .sp-faq-question::after { transform: rotate(-135deg); }
/* max-height (not height) is what JS animates, since the answer's rendered
   height is only known once its content is measured - see help-center.js.
   Starts at 0 so a collapsed item takes up no space at all; the inner
   wrapper carries the padding so that padding doesn't get counted while
   collapsed (which would otherwise leave a visible sliver). */
.sp-faq-answer {
	max-height: 0;
	overflow: hidden;
	transition: max-height 0.25s ease;
}
.sp-faq-answer-inner {
	padding: 0 1.2em 1.2em;
	color: #444;
	line-height: 1.6;
}
.sp-faq-answer-inner > *:first-child { margin-top: 0; }
.sp-faq-answer-inner > *:last-child { margin-bottom: 0; }

/* Course page - "Passing grade progress: X%" row (with its non-functional "?"
   tooltip icon). Deliberate exception to the unhook-via-filter pattern used
   everywhere else in class-sp-learnpress-course-display.php: both this row
   and the "Course progress: X%" row Martin wants kept come out of one PHP
   method (UserCourseTemplate::html_progress()) as a single combined HTML
   string, with no LearnPress filter finer-grained than that whole string,
   and both rows share the .course-progress__label class. :has() lets this
   target only the row that actually contains the "?" icon, so if LearnPress
   ever adds another .course-progress__label row without that icon it stays
   visible by default rather than silently being swept up here too. */
.course-progress__label:has(.lp-icon-question-circle) { display: none; }

/* LearnPress's generic confirm popup (templates/global/lp-modal-overlay.php)
   - reused for "Complete lesson", among other things - recoloured to match
   the RTGL brand palette instead of LearnPress's default purple (#7c60d9).
   See rtgl-colour-scheme-implementation for the source palette: header/nav
   background #333333, primary CTA #FF0000 (hover #CC0000), surface #F8F9FA,
   border #E2E8F0, body text #1A1A1A. Every rule is prefixed with "body" to
   out-specificity LearnPress's own equally-specific selectors regardless of
   which stylesheet the browser happens to load second. */
body .lp-modal-dialog .lp-modal-header {
	background: #333333;
}
body .lp-modal-dialog .lp-modal-header .modal-title {
	color: #ffffff;
}
body .lp-modal-dialog .lp-modal-footer {
	background-color: #F8F9FA;
}
body .lp-modal-dialog .btn-yes {
	background-color: #FF0000;
	border-color: #FF0000;
	color: #ffffff;
}
body .lp-modal-dialog .btn-yes:hover {
	background-color: #CC0000;
	border-color: #CC0000;
	color: #ffffff;
}
body .lp-modal-dialog .btn-no {
	background-color: #ffffff;
	border: 1px solid #E2E8F0;
	color: #1A1A1A;
}
/* LearnPress's own generic ".learnpress-page .lp-button:hover" rule (in its
   learnpress.css) turns hover text white on every .lp-button, including
   this one (btn-no also carries the lp-button class) - explicitly holding
   the text colour here on hover is what actually overrides that, not just
   background-color, since that generic rule is exactly as specific as an
   unqualified ".btn-no:hover" would be. */
body .lp-modal-dialog .btn-no:hover {
	background-color: #F8F9FA;
	color: #1A1A1A;
}

/* Course page: the right-hand info card (progress bar, course thumbnail,
   Continue/Start button) sat behind the site header on every course page.
   Root cause, confirmed against the installed LearnPress source
   (assets/css/learnpress.css): LearnPress's own "modern" course layout pulls
   that card up by a fixed -280px at desktop widths
   (`.lp-single-course .lp-single-course-main__right { margin-top: -280px; }`
   inside `@media (min-width: 992px)`), designed for a theme where a tall
   hero banner sits above it so the card floats up to overlap the bottom of
   that banner. This site's course header has been decluttered down to much
   less than 280px of height (breadcrumb/instructor/category/meta/last-
   updated/share-widget all removed - see the course-display class), so the
   card now gets pulled up past the header entirely, into the site's actual
   nav bar. `body` prefix for specificity insurance, same pattern as the
   .lp-modal-dialog overrides above - LearnPress's own rule is exactly as
   specific otherwise, so load order alone wouldn't guarantee this wins. */
@media (min-width: 992px) {
	body .lp-single-course .lp-single-course-main__right {
		margin-top: 0;
	}
}

/* Lesson/quiz "focus mode" popup: the X ("back to course") button in the
   top-right corner. Verified against the installed source
   (templates/single-course/content-item/popup-header.php: `<a class="back-
   course"><i class="lp-icon-times"></i></a>`) and its default styling
   (learnpress.css: `#popup-course .back-course { color: #fff; }` /
   `:hover` only lightens the background, never changes the icon/text
   colour). On hover the button's background turns brand red and the X
   icon itself stays white - `color: #fff` is set explicitly here (not just
   relied on from the default rule) so this keeps working even if that
   default ever changes. `body` prefix for specificity insurance, same
   pattern as the other LearnPress overrides above, since the ID in
   LearnPress's own selector otherwise ties with ours on specificity and
   load order alone wouldn't guarantee a win. */
body #popup-course .back-course:hover {
	background: #FF0000;
	color: #fff;
}

/* Course info-meta row: the inline SVG "quiz" icon (see
   SP_LearnPress_Course_Display::remove_meta_fields()) sits where LearnPress's
   own <i class="lp-icon-..."> icons normally do, but LearnPress's colour
   rule for that row (learnpress.css: `.info-metas i { color: ... }`) only
   targets <i> elements, so it wouldn't otherwise pick up the same brand
   colour as the "lesson" icon next to it. The SVG uses currentColor for its
   fill/stroke, so setting `color` here is enough to match. */
.lp-single-course-main .info-metas .sp-quiz-icon {
	color: var(--lp-primary-color, #ffb606);
	vertical-align: middle;
}

/* ============================================================
   Portal: Troubleshooter - guided decision-tree self-service support.
   See SP_Shortcodes::troubleshoot() / assets/js/troubleshoot.js. Deliberately
   mirrors the Help Center block's own conventions: full width (no max-width -
   see the Help Center v1.22.1 fix above for why), and the same `body`-prefix
   specificity-insurance pattern on the two real <button> elements so a
   theme's own default button styling can't bleed through regardless of load
   order (this exact bug hit the Help Center's question button once already).
   ============================================================ */
.sp-troubleshoot {
	width: 100%;
	box-sizing: border-box;
	background: #fff;
	border: 1px solid #e2e2e2;
	border-radius: 8px;
	padding: 1.6em;
}
/* Shown above the question/step text while inside a flow, so it's always
   clear which topic you're partway through - see troubleshoot.js. Kept
   visually distinct (smaller, muted, uppercase) from .sp-ts-prompt so it
   reads as a label, not another line of the question itself. */
.sp-ts-flow-title {
	font-size: 0.8em;
	font-weight: 600;
	text-transform: uppercase;
	letter-spacing: 0.04em;
	color: #6b7280;
	margin: 0 0 0.5em;
}
/* Already-answered steps, oldest first, kept on screen above the live
   question so the path taken through the flow so far stays visible - see
   troubleshoot.js's renderTrail(). Deliberately muted/smaller than the live
   .sp-ts-prompt below it, with a divider, so it reads as "done" rather than
   competing with the current question for attention. */
.sp-ts-trail-entry {
	padding-bottom: 1em;
	margin-bottom: 1em;
	border-bottom: 1px solid #e8e8e8;
}
.sp-ts-trail-prompt {
	font-size: 1em;
	font-weight: 600;
	color: #6b6b6b;
	margin: 0 0 0.6em;
}
.sp-ts-trail-prompt p:last-child { margin-bottom: 0; }
.sp-ts-trail-answer {
	display: inline-block;
	padding: 0.3em 0.9em;
	background: #eef4fa;
	border: 1px solid #d3e3f1;
	border-radius: 999px;
	color: #2271b1;
	font-size: 0.9em;
	font-weight: 600;
}
.sp-ts-prompt {
	font-size: 1.1em;
	font-weight: 600;
	color: #1a1a1a;
	margin: 0 0 1.2em;
}
.sp-ts-prompt p:last-child { margin-bottom: 0; }
.sp-ts-options {
	display: flex;
	flex-direction: column;
	gap: 0.6em;
	margin-bottom: 1.2em;
}
/* Answer options only (not the flow-picker menu, which stays a plain
   vertical list of topics via the bare .sp-ts-options above) - laid out
   side by side and wrapping onto more rows only once they no longer fit,
   so a plain Yes/No pair always sits side by side rather than stacked, and
   longer or more numerous answers wrap naturally instead of overflowing.
   See troubleshoot.js, which adds this class only to a step's own answer
   options wrapper. */
.sp-ts-answer-options {
	flex-direction: row;
	flex-wrap: wrap;
}
.sp-ts-answer-options .sp-ts-option-btn {
	display: inline-block;
	width: auto;
	flex: 1 1 160px;
	max-width: 100%;
	text-align: center;
}
body .sp-ts-option-btn {
	display: block;
	width: 100%;
	box-sizing: border-box;
	text-align: left;
	padding: 0.8em 1em;
	background: #f6f7f7;
	border: 1px solid #ddd;
	border-radius: 6px;
	color: #1a1a1a;
	font: inherit;
	cursor: pointer;
	transition: background 0.15s ease, border-color 0.15s ease;
}
body .sp-ts-option-btn:hover {
	background: #eef4fa;
	border-color: #2271b1;
}
.sp-ts-controls {
	display: flex;
	gap: 0.6em;
}
/* box-sizing: border-box is deliberate here (and on the option button above) -
   the Elementor widget's Style tab (see button_style_section() in
   class-widget-base.php) lets a site editor set a different border for the
   Hover state than for Normal. With the default content-box sizing, a
   heavier hover border grows the button's outer footprint, which (a) can
   nudge the button out from under a stationary mouse pointer - cancelling
   :hover the instant it applies, which reads as "hover doesn't work" - and
   (b) pushes everything after it (including the page footer, since these
   sit at the bottom of the flow card) down the page while hovered. Fixed
   sizing means any hover border just eats into the button's own padding
   instead of changing its outer size, so neither can happen regardless of
   what border widths get set per-state. */
body .sp-ts-back-btn,
body .sp-ts-restart-btn {
	display: inline-block;
	box-sizing: border-box;
	padding: 0.5em 1.1em;
	background: transparent;
	border: 1px solid #ccc;
	border-radius: 6px;
	color: #444;
	font: inherit;
	cursor: pointer;
}
body .sp-ts-back-btn:hover,
body .sp-ts-restart-btn:hover {
	background: #f6f7f7;
}
.sp-ts-empty {
	color: #666;
	margin: 0;
}
