/* Rules that exist only to beat Hello Elementor, which loads after plugin CSS
   and restyles controls hard. Niblo lost this exact fight once, to
   [type="button"]:hover.

   Every selector here names one of OUR components. There was a blanket
   `.ts-oblici h1,h2,h3,h4 { font-family: !important; font-weight: !important }`
   in this file, and because the body class was on every page it re-set every
   heading on the live site. A defensive rule that can reach outside the
   component it defends is not a defence, it is a bug with wider blast radius. */

.ts-oblici .ts-burger,
.ts-oblici button.ts-opt,
.ts-oblici button.ts-rail-item,
.ts-oblici .ts-panel {
  background-image: none !important;
  text-transform: none;
  letter-spacing: inherit;
}

.ts-oblici .ts-burger:hover,
.ts-oblici .ts-burger:focus,
.ts-oblici button.ts-rail-item:hover,
.ts-oblici button.ts-rail-item:focus {
  background: none !important;
  box-shadow: none !important;
}

/* The parent theme caps img width; the silhouette crop needs to fill its frame. */
.ts-oblici .ts-window img { max-width: none !important; }

/* Headlines inside our own components are hagrid 800. A theme h3 rule that
   sets 600 is hard to spot, because it only looks slightly wrong. */
.ts-scope :is(h1, h2, h3, h4),
.ts-oblici :is(.ts-row, .ts-card, .ts-panel, .ts-quiz-card, .ts-tease,
               .ts-sec-head, .ts-video-card, .ts-relcard, .ts-interrupt,
               .ts-arch-txt, .ts-art-txt, .ts-lead, .ts-stack, .ts-mix,
               .ts-list, .ts-top10, .ts-menu-grid) :is(h1, h2, h3, h4) {
  font-family: var(--ts-display) !important;
  font-weight: 800 !important;
}