/*
 * rhk — polish that has no equivalent block control:
 * a soft cyan glow under the sticky nav and under each section's
 * neon top divider. Everything else on the front page is plain
 * block markup/theme.json tokens — this file only adds box-shadow
 * and resets the theme's global block-gap inside rhk sections
 * (we hand-set margins on every child instead of stacking WP's
 * default ~19px gap on top of them).
 */
.rhk-section {
	--wp--style--block-gap: 0px;
}

/*
 * Force true edge-to-edge width by direct CSS, independent of
 * WordPress's own "alignfull" mechanism (whatever wrapper ends up
 * around the header/section in the final markup, this always wins).
 */
.rhk-section,
.rhk-nav-glow,
.rhk-full-bleed {
	width: 100vw !important;
	max-width: 100vw !important;
	margin-left: calc(50% - 50vw) !important;
	margin-right: calc(50% - 50vw) !important;
	left: auto !important;
	right: auto !important;
	/* WP puts "has-global-padding" and "alignfull" on this same element
	   instead of on parent+child, so the padding never gets cancelled
	   by WordPress's own rule. Kill it directly — confirmed via curl on
	   the live HTML: every one of our 10 full-bleed sections has both
	   classes stacked on itself. */
	padding-left: 0 !important;
	padding-right: 0 !important;
}

/*
 * No pseudo-element glow anymore — removed entirely. Both the nav's
 * bottom border and each section's top divider are already plain
 * solid borders set inline on the block itself; nothing else needed.
 */

/*
 * WordPress ships a global rule — html :where([style*=border-color])
 * { border-style: solid } — that matches ANY inline style containing
 * the substring "border-color", including our "border-bottom-color",
 * "border-top-color" and "border-left-color". Any element that only
 * sets a WIDTH for the one side it actually wants a border on gets
 * the other three sides filled in by the browser default ("medium",
 * ~3px) using currentColor — an unwanted line/bar WordPress itself is
 * drawing, not us.
 *
 * General fix, not per-element: zero all four sides on ANY element
 * whose inline style sets a single-side border-color, full stop. The
 * specific side(s) it actually wants stay correct regardless, because
 * inline border-*-width (no !important) always wins over this
 * stylesheet rule for that exact same longhand property — this rule
 * only fills the gap for the sides nothing else touches. Covers the
 * nav, every section divider, the mock panel's window-bar strip, the
 * "how funciona"/"princípios" step columns, and any future block we
 * add with a one-sided border, without needing a class on each.
 */
[style*="border-top-color"],
[style*="border-bottom-color"],
[style*="border-left-color"],
[style*="border-right-color"] {
	border-width: 0;
}

/*
 * The hero's split white/ink background is a fixed 56%/44% gradient
 * designed to line up with the two-column desktop layout (text |
 * product mock). Below WordPress's own column-stacking breakpoint
 * (781px — where core/columns switches to flex-direction:column),
 * the columns go single-file but the gradient doesn't know that and
 * keeps splitting at the same fixed point, so the headline/paragraph
 * text ends up sitting on top of the dark half, unreadable. Flatten
 * it to plain white below that breakpoint, matching when the columns
 * actually stack.
 */
@media (max-width: 781px) {
	.has-rhk-hero-split-gradient-background {
		background: #ffffff !important;
	}
}