/* GENERATED by _build/css.py. Unlayered on purpose: it must outrank Elementor's CSS.

   The design CSS lives entirely in cascade layers. Elementor's CSS is unlayered, and an
   unlayered rule beats a layered one whatever its specificity, so on its own Elementor would
   restyle every container and widget the design draws. These rules cancel that:

   1. On design elements inside Elementor content (containers marked solace-raw, widgets
      marked solace-leaf, and everything inside them that is not Elementor's own UI),
      `all: revert-layer` throws away every UNLAYERED declaration, Elementor's and
      WordPress's alike, so only the design's layered rules (and inline styles) remain.
      Styles a client sets in the Elementor panel use longer, element-specific selectors and
      still win.
   2. Widget wrappers take no part in layout (display: contents), so the wrapped element sits
      exactly where the design puts it. site.css carries wrapper-aware variants of the
      parent/child rules for the same reason.
   3. In the editor only: wrappers keep a box (so they can be hovered and dragged) and
      every accordion answer is open (so it can be edited). Visitors never get these. */
.elementor.elementor.elementor :is(.solace-raw,.solace-leaf),
.elementor.elementor.elementor :is(.solace-raw,.solace-leaf) :not([class*="elementor-"]){all:revert-layer}
.elementor.elementor.elementor .elementor-widget.solace-leaf{display:contents}
.elementor-editor-active .elementor.elementor.elementor .elementor-widget.solace-leaf{display:block}
.elementor-editor-active .elementor.elementor.elementor details.acc > .acc-wrap{height:auto!important;overflow:visible!important}