Repro (3-artist-music)
.reveal/.reveal-d1..3/.pl elements start at opacity: 0 and are revealed by JS (IntersectionObserver adds an in-view class). The JS isn't carried into WP. So:
- If the site CSS carries (it's materialized into the theme) with
opacity:0, those elements stay invisible forever — a correctness bug (hidden press quote, tour rows, etc.), not just a missing animation.
- If the CSS doesn't carry, the reveal simply doesn't happen (content visible, static).
Ask (priority order)
- Correctness first: never leave content hidden when its reveal/animation driver (JS) wasn't carried. Detect reveal-gated initial-hidden state (
opacity:0 + animation/JS-hook class) and neutralize it (ensure final visible state) when the driving behavior isn't materialized.
- Fidelity (secondary): optionally rebuild scroll-reveal via the Interactivity API or a tiny scoped companion-plugin script so the animation is preserved.
Pure-CSS keyframe animations (e.g. .scroll-hint { animation: fadeUp … forwards }) should be preserved if the CSS carries; the dangerous case is JS-gated reveals left at opacity:0.
Repro (3-artist-music)
.reveal/.reveal-d1..3/.plelements start atopacity: 0and are revealed by JS (IntersectionObserver adds an in-view class). The JS isn't carried into WP. So:opacity:0, those elements stay invisible forever — a correctness bug (hidden press quote, tour rows, etc.), not just a missing animation.Ask (priority order)
opacity:0+ animation/JS-hook class) and neutralize it (ensure final visible state) when the driving behavior isn't materialized.Pure-CSS keyframe animations (e.g.
.scroll-hint { animation: fadeUp … forwards }) should be preserved if the CSS carries; the dangerous case is JS-gated reveals left at opacity:0.