/* 01 — Bloom Editorial: carousel-specific styling.
   Design tokens come from Figma via inline styles + Tailwind arbitrary
   values already in index.html; this covers what those can't express. */

.canvas {
  position: relative;
}

.slide {
  position: absolute;
  inset: 0;
  opacity: 0;
  visibility: hidden;
  transition: opacity 0.5s ease, transform 0.5s ease;
  transform: translateX(24px);
}

.slide.active {
  opacity: 1;
  visibility: visible;
  transform: translateX(0);
}

/* Every slide ships its own copy of the nav/bullets/prev-next chrome
   (that's how Figma exported each screen) -- only the active slide's
   copy should be interactive/visible to avoid 4 stacked nav bars. */
.slide:not(.active) [data-name="main menu"],
.slide:not(.active) [data-name="bullets"] {
  display: none;
}

[data-name="bullets"] > div {
  cursor: pointer;
  transition: width 0.25s ease, opacity 0.2s ease;
}
[data-name="bullets"] > div:hover {
  opacity: 0.8;
}

/* Some screens ship their own native prev/next caret buttons; we drive
   navigation from the single persistent .carousel-btn pair instead, so
   hide the per-slide ones to avoid two overlapping button pairs. */
.slide *:has(> [data-name="CaretRight"]) {
  display: none;
}

.carousel-btn {
  width: 44px;
  height: 44px;
  border-radius: 999px;
  border: 1px solid rgba(255, 255, 255, 0.4);
  background: rgba(255, 255, 255, 0.12);
  backdrop-filter: blur(6px);
  color: #fff;
  font-size: 22px;
  line-height: 1;
  cursor: pointer;
  transition: background 0.2s ease, transform 0.15s ease;
}
.carousel-btn:hover {
  background: rgba(255, 255, 255, 0.28);
  transform: translateY(-1px);
}
.carousel-btn:active {
  transform: translateY(0);
}