links (e.g. the "Fatal Pattern" and "from the publisher" links inside
* her own copy, not just the trailing "Click here" fallback link) — these
* get wrapped in real tags by Formidable's own wpautop() call, so plain
* `p` margin + `line-height` is sufficient for readable paragraph spacing;
* no white-space hack needed. No card/background is added here, matching
* the same "sits directly on the dark navy page, no card" direction Kate
* set for the rest of the form in v1.0.6 — only spacing/color/typography are
* applied. Emoji (🥳, 💛) are untouched: `color` never affects the color of
* native color-emoji glyphs in any modern browser, so no exclusion rule is
* needed for them.
*/
.with_frm_style .frm-redirect-msg,
.frm-redirect-msg {
display: block;
color: #EEF2F8 !important;
font-family: 'Poppins', 'Helvetica Neue', Arial, sans-serif;
line-height: 1.6;
max-width: 700px;
padding: 32px 36px;
}
.with_frm_style .frm-redirect-msg p,
.frm-redirect-msg p {
color: inherit;
margin: 0 0 1.15em 0;
}
.with_frm_style .frm-redirect-msg p:last-of-type,
.frm-redirect-msg p:last-of-type {
margin-bottom: 0;
}
.with_frm_style .frm-redirect-msg a,
.frm-redirect-msg a {
color: #F5D000 !important;
text-decoration: underline;
font-weight: 600;
}
.with_frm_style .frm-redirect-msg a:hover,
.with_frm_style .frm-redirect-msg a:focus,
.frm-redirect-msg a:hover,
.frm-redirect-msg a:focus {
color: #FFE033 !important;
}
/* ── v1.2.4: invisible reCAPTCHA badge repositioning ─────────────────────
* Any Formidable form using an invisible reCAPTCHA (data-size="invisible",
* e.g. field id 6 / .frm-g-recaptcha on the Contact form) gets a badge
* that Google's own script injects as `.grecaptcha-badge`, position:fixed,
* appended directly to
— NOT nested inside the form or any of our
* markup. Flagged live on /contact/ as "hanging off the right edge."
* Google's Terms of Service require the badge stay visible (it cannot be
* hidden), but explicitly allow repositioning it via CSS, which is what
* this does — a small, deliberate offset from the true viewport corner
* instead of wherever it lands by default. Unscoped (sitewide) since the
* badge can appear on any page with an invisible-reCAPTCHA Formidable
* form, not just Contact.
*
* CAVEAT: the badge's on-screen position also depends on whether any
* ancestor of has its own CSS `transform` (a `position:fixed`
* descendant becomes relative to the nearest transformed ancestor instead
* of the real viewport) — that can't be fully confirmed without live
* browser devtools. This fix corrects the badge's own coordinates; if it
* still renders off-position after upload, the next step is to find and
* remove/adjust whatever transformed ancestor is capturing it.
*/
/* ── v1.2.9 fix (L4): bottom offset increased, 16px → 96px, to clear the
* shared footer's (template #7765) bottom-right corner — the badge (fixed
* bottom-right, ~60px tall per Google's standard invisible-badge box) was
* landing on top of the footer's right-aligned "Connect" column content
* at full scroll. Measured from the footer's own real, verified generated
* CSS (post-7765.css): the footer's LAST section on the page is a
* copyright bar (`.elementor-element-13ac3a8f`, 18px top + 18px bottom
* padding = 36px chrome) whose right column is a right-aligned social-
* icons row (`--icon-size:17px`, plus the icon widget's own default
* padding — roughly 35-40px tall rendered) — a real, measured total of
* ~71-76px for that bar alone. The OLD 16px offset put the badge's own
* span at 16-76px from the true page bottom, which is almost exactly that
* copyright bar's own height — meaning the top few pixels of the badge
* were landing just above it, on the "Connect" column immediately above
* (confirmed live as "slightly overlapping," consistent with only a
* ~5-10px intrusion at that boundary). Moving the badge's own span to
* 96-156px clears the ENTIRE copyright bar with room to spare (~20-25px
* of margin above it) and, by the same margin, clears the Connect
* column's own bottom edge (which sits right where the copyright bar
* starts) rather than just barely grazing it. Horizontal position (right:
* 16px) is unchanged — the reported collision was vertical/footer-height,
* not horizontal, and Connect is still the rightmost column so the badge
* stays visually aligned with it, just higher up.
*/
.grecaptcha-badge {
right: 16px !important;
bottom: 96px !important;
z-index: 999 !important;
}