/**
 * CW Button Preset widget — Elementor markup (.elementor-button-icon) + cw-hero-homepage.css skins.
 */

.elementor-widget-cw-button-preset .elementor-button.cw-hero__btn--ghost:hover .elementor-button-icon {
	transition: transform 0.3s ease;
	transform: translateX(4px);
}

.elementor-widget-cw-button-preset .elementor-button.cw-hero__btn .elementor-button-icon svg {
	width: 1.125rem;
	height: 1.125rem;
	fill: currentColor;
}

/* ---- Cross-widget hero-btn parity ----
 * Elementor's per-page CSS emits `.elementor-widget-cw-button-preset .elementor-button`
 * rules that pull `font-size/family/weight/line-height` from the kit's "Accent"
 * typography globals. Specificity (0,2,0) beats `.cw-hero__btn` (0,1,0), so the
 * cw-button-preset widget renders with the kit's `font-weight:600 / line-height:1.5em`
 * while the Gated Content Button (which has no Button_Trait, so Elementor never
 * emits that override) renders with our `.cw-hero__btn` defaults — making the two
 * widgets visibly different even though they share the exact same class set.
 *
 * Pin our hero-btn typography on any `.elementor-button.cw-hero__btn` inside an
 * Elementor widget. Specificity (0,3,0) beats the kit injection at every viewport
 * — Elementor's `@media(max-width:…)` re-assertions are still (0,2,0) and lose. */
.elementor-widget .elementor-button.cw-hero__btn {
	padding: 1rem 2rem;
	font-size: 0.875rem;
	font-weight: 700;
	line-height: 1.2;
}