/*
  Local, theme-independent overrides for this site. Kept separate from any
  al_folio_core/al_folio_bootstrap_compat file so gem upgrades never touch or
  conflict with it. Add new fixes below with a comment explaining why.
*/

/*
  al_folio_bootstrap_compat's bootstrap-compat.css loads after tailwind.css and
  redeclares .collapse{visibility:hidden}, which (same specificity, later in the
  cascade) wins over tailwind.css's .collapse{visibility:visible} and hides the
  entire nav menu even though display:flex still applies. #navbarNav.collapse
  has higher specificity than either plain .collapse rule, so this stays correct
  regardless of stylesheet load order.
*/
#navbarNav.collapse {
  visibility: visible;
}

/*
  al_folio_core's main.css (loads last, after bootstrap-compat.css) carries
  legacy .af-popover/.af-tooltip rules that set position:absolute. But
  bootstrap-compat.js positions these bubbles using getBoundingClientRect(),
  which is viewport-relative and only correct for position:fixed (what
  bootstrap-compat.css itself actually specifies). With position:absolute the
  bubble is placed relative to the document instead of the viewport, so for
  anything below the first screenful the popover/tooltip renders off-screen —
  hovering the icon silently does nothing. !important because main.css always
  loads last and a plain override would just lose the same way.
*/
.af-popover,
.af-tooltip {
  position: fixed !important;
}