/*
 * Blog — full-bleed edge-to-edge fix (bug 65).
 * These band sections rely on being 100% of their nearest full-width
 * ancestor to reach the true viewport edge. Blocksy's own container-width
 * chain (--theme-container-width: min(100%, calc(100vw - Npx*2))) mixes
 * percentage and vw math that can drift out of sync with the true viewport
 * (large/zoomed-out screens), leaving cream gaps on both sides instead of
 * a full-width row. The classic vw-breakout ties these sections directly
 * to the real viewport width instead, independent of any ancestor's width.
 */
body.log-blog-page {
  /* 100vw breakouts below can exceed the true viewport by the scrollbar's
     width, causing a horizontal scrollbar of their own; guard against it. */
  overflow-x: hidden;
}

.log-blog-page .bl2-hero-masthead,
.log-blog-page .bl2-cat-strip,
.log-blog-page .bl2-newsletter-band,
.log-blog-page .bl2-faq-section,
.log-blog-page .bl2-contact-band {
  /* Same Blocksy ".is-layout-constrained > *" !important auto-margin rule
     as the cta-banner fix (these are all wp:html direct children of
     entry-content too) — must match its !important to win. */
  width: 100vw !important;
  max-width: 100vw !important;
  position: relative;
  left: 50%;
  right: 50%;
  margin-left: -50vw !important;
  margin-right: -50vw !important;
}

/*
 * Bugs 66/67 — Blocksy also adds margin-block-start/end: var(--theme-content-
 * spacing) to every direct child of entry-content, leaving a thin cream seam
 * between adjacent full-bleed rows (hero->cat-strip, newsletter->faq).
 * Zero it for the pairs that must sit flush against each other.
 */
.log-blog-page .bl2-hero-masthead,
.log-blog-page .bl2-newsletter-band {
  margin-bottom: 0 !important;
}

.log-blog-page .bl2-cat-strip,
.log-blog-page .bl2-faq-section {
  margin-top: 0 !important;
}