/*
 * Site chrome — the parts RasoCMS manages.
 *
 * The menu and the footer are managed regions (cms:nav, cms:footer), which
 * means their markup has to be byte-identical on every page: publish takes one
 * page's copy and writes it to all of them.
 *
 * Elementor marked the current page with `elementor-item-active` on the <a> and
 * `current-menu-item current_page_item page-item-<id>` on the <li>. Those say
 * per-page state in a form RasoCMS cannot normalise away — it strips
 * `aria-current="page"` when comparing regions and re-applies it per page, and
 * nothing else. Left in place, the first publish would have stamped whichever
 * page was edited onto the other seven, highlighting the wrong menu item
 * everywhere.
 *
 * So the state classes are gone and `aria-current="page"` is the single source
 * of truth. These two rules restore exactly what those classes were doing —
 * one declaration each, copied from post-35.css and post-40.css, using the same
 * global custom properties rather than hardcoded colours.
 */

.elementor-35 .elementor-element.elementor-element-2b9f8aa5 .elementor-nav-menu--main .elementor-item[aria-current="page"] {
  color: var(--e-global-color-secondary);
  fill: var(--e-global-color-secondary);
}

.elementor-40 .elementor-element.elementor-element-1efadd2e .elementor-nav-menu--main .elementor-item[aria-current="page"] {
  color: var(--e-global-color-secondary);
}