/* ========================================================================== MyCabin Design System — theme-compat.css (v0.1.5) DEFENSIVE FALLBACK ONLY as of v0.1.5. The real fix for theme button/ typography contamination is now class-mgds-theme-compat.php's add_page_builder_class_for_mycabin_content() — it stamps the active theme's own `elementor-page` escape-hatch class onto on genuinely MyCabin-managed pages, which makes the theme's contaminating rule (below) never match MyCabin markup at all. This file's own selector is IDENTICAL to that theme rule's own `body:not(.elementor-page) ...` selector, so on every page where the body-class fix is active, THIS file's rule also stops matching, for the same reason — it has nothing left to do there. It only still fires as a safety net for the unlikely case the body-class filter doesn't run for some reason. === v0.1.4 → v0.1.5: why this file no longer uses !important === v0.1.4 used `!important` on `border-radius` specifically (the one property the theme's own contaminating rule also marks `!important`, confirmed via a live disable/re-enable isolation test) so this file's reset could out-rank it. That worked against the theme — but it also out-ranked every Page Pack's/Site Part's OWN non-`!important` radius (e.g. a filled pill CTA's `border-radius: var(--pp-r-pill)`), flattening every non-zero-radius button on the site to 0, a real, user-visible regression confirmed live and reported back. Now that the body-class fix (see class-mgds-theme-compat.php) is the primary mechanism and already prevents the theme's rule from matching MyCabin content at all, this file never needs to out-rank a real `!important` competitor on MyCabin pages in normal operation — so `!important` has been removed here entirely, on every property including radius. That also means this fallback, if it ever DOES fire (the edge case above), is intentionally weaker than the primary fix: it can still be out-ranked by a real Page Pack/Site Part rule, but can also still be out-ranked BY a real theme `!important` rule if the primary fix didn't apply — an accepted tradeoff, since the primary fix is expected to be what actually runs. === Original root cause (still accurate — this is the same rule) === Confirmed live on dev.mycabin.lv (Hostinger AI theme v2.1.5): the active theme ships its own static stylesheet (assets/css/style.min.css) containing: body:not(.elementor-page) .wp-block-button__link, body:not(.elementor-page) .wp-element-button:not([type="submit"]) { border-width: 2px; border-style: solid; border-radius: var(--wp--custom--border-radius,8px) !important; padding: 8px 16px; font-weight: 500; display: inline-flex; ... } theme.json overrides can't touch this file at all — it isn't Global Styles output, it's ordinary author CSS the theme itself enqueues. `font-weight: 500` was added to this file's own reset list in v0.1.5 (not present in v0.1.4 — that round's own reported issue was radius/ border/padding only; header dropdown and footer link boldness were reported and root-caused this round, traced to this exact rule). ========================================================================== */ body:not(.elementor-page) .wp-block-button__link, body:not(.elementor-page) .wp-element-button:not([type="submit"]) { display: inline-block; align-items: unset; justify-content: unset; min-height: 0; line-height: inherit; font-size: inherit; font-weight: inherit; box-sizing: border-box; border-width: 0; border-style: none; padding: 0; border-top-left-radius: 0; border-top-right-radius: 0; border-bottom-right-radius: 0; border-bottom-left-radius: 0; }