/*!
 * assets/forms.css - styling for the two elements this lane adds to a page,
 * and nothing else.
 *
 * Sprint rule: no lane consolidates or tidies this site's CSS. Every selector
 * here targets markup that did not exist on the page before, so nothing that
 * was already rendering can change appearance because of this file.
 *
 * WHY THE TURNSTILE WRAPPER HAS NO PADDING.
 *
 * WPForms' own captcha slot is spaced by a rule already in the captured CSS:
 * `.wpforms-container .wpforms-recaptcha-container .wpforms-turnstile
 * { padding: 10px 0 0 }`. Reaching it would mean giving the widget WPForms'
 * `wpforms-recaptcha-container` class, and that class is what the plugin's
 * `formHasCaptcha()` test looks for. A truthy result there sends it down a
 * branch that calls `grecaptcha.reset()` on a global that no longer exists
 * once the Google widget is removed, so the class is deliberately not used.
 *
 * That leaves the question of spacing, and the honest answer is that it has
 * not been observed. The widget is configured `appearance="interaction-only"`,
 * which renders nothing at all unless Turnstile decides the visitor needs to
 * act, and no sitekey existed while this was written, so what the widget
 * actually occupies in a browser is unknown. Padding added on that assumption
 * would put a gap above the submit button on nine pages and nobody would know
 * why. So there is none, and the lane's findings file asks for one look in a
 * browser once a real sitekey is in place.
 */

/* Shown by assets/forms.js only when the Turnstile script did not load,
   usually a privacy extension or a network filter. */
.scaledon-forms-turnstile-blocked {
  margin: 10px 0 0;
  font-size: 0.875em;
  line-height: 1.5;
  color: #a4262c;
}