/* In Arch Shop — the few rules that must load on every page.
   shop.css is deliberately narrow (project pages only, see
   inarch_shop_is_project_context()); this file is the opposite and so
   carries one rule and one rule only.

   „GAUTI PASIŪLYMĄ" is an Elementor button widget, styled per element in
   each template (portfolio single 7959: dark ground, white text). On the
   project pages it now sits under a second dark CTA — two black buttons
   stacked — so the offer button is the outline one everywhere: white
   ground, black text, black line. Matched on the destination rather than
   on a widget id, so a button added to a new template is styled too.
   The width is set here too: the live button computes `border-width: 0`
   whatever its Elementor setting says, so colour alone left no line.
   Buttons are border-box, so 2px changes no outer width.
   !important because Elementor's per-element CSS
   (`.elementor-7959 .elementor-element.elementor-element-<id> .elementor-button`)
   outweighs anything a plugin stylesheet can say about a class. */
.elementor-button[href*="/gauti-pasiulyma"],
a.elementor-button[href*="/gauti-pasiulyma"]:visited {
  background-color: #fff !important;
  color: #000 !important;
  fill: #000 !important;
  border-style: solid !important;
  border-width: 2px !important;
  border-color: #000 !important;
}
.elementor-button[href*="/gauti-pasiulyma"]:hover,
.elementor-button[href*="/gauti-pasiulyma"]:focus {
  background-color: #000 !important;
  color: #fff !important;
  fill: #fff !important;
  border-color: #000 !important;
}

/* The footer is the one place the rule above must not reach. The footer's
   own instance (template 11878, element 7700a84) is a ghost button on the
   black band: the site's own custom CSS forces
   `.elementor-element-7700a84 .elementor-button { background: transparent }`
   with !important, and at equal specificity (0,2,0) it is written after this
   file, so it wins the background — while `color: #000` above still wins the
   text. Black text on a transparent button on a black band: the CTA has been
   invisible on every page of the site. Found 2026-09-22.

   Rather than fight the site CSS for the background, keep the ghost button
   the footer was designed as and give it the white text and line that match
   it. Three classes (0,3,0) outrank both rules, so no !important war. */
.elementor-location-footer .elementor-button[href*="/gauti-pasiulyma"],
.elementor-location-footer a.elementor-button[href*="/gauti-pasiulyma"]:visited {
  background-color: transparent !important;
  color: #fff !important;
  fill: #fff !important;
  border-color: #fff !important;
}
.elementor-location-footer .elementor-button[href*="/gauti-pasiulyma"]:hover,
.elementor-location-footer .elementor-button[href*="/gauti-pasiulyma"]:focus {
  background-color: #fff !important;
  color: #000 !important;
  fill: #000 !important;
  border-color: #fff !important;
}

/* Home page, „DAUGIAU APIE PASLAUGAS". The button is an Elementor widget
   in the services band's mobile-only variant, set to align right — but
   its own container is 310px inside a 330px band, so the right edge it
   aligned to was 20px short of the band's. The result read as neither
   right-aligned nor centred: it just sat off to the left.

   Two rules rather than one: the container takes the band's full width,
   then the button centres in it. Matched on the destination and scoped
   to the home page, the way the „GAUTI PASIŪLYMĄ" rule above is matched
   — a widget id would break the next time the section is rebuilt. */
body.home .e-con:has(> .elementor-widget-button > .elementor-widget-container
  > .elementor-button-wrapper > .elementor-button[href*="/interjero-paslaugos"]) {
  width: 100%;
}
body.home .elementor-button-wrapper:has(> .elementor-button[href*="/interjero-paslaugos"]) {
  text-align: center;
}