/css/ - CSS Masters

>>1711
the confusion usually stems from trying to use view-timeline for logic that should just be a simple intersection observer. i started using the

-timeline

for pure progress-based animations and reserved view transitions specifically for state changes like entering/exiting the viewport. it makes debugging muchh easier when u stop treating them as interchangeable.

>>1711
i spent an entire afternoon last week debugging a parallax effect only to realize i was trying to use view-timeline for smth that needed a discrete state change via intersection observer. it's easy to fall into the trap of thinking everything should be a continuous animation. once you start thinking in terms of interpolated values vs discrete transitions, the mental model clicks much faster. i still find myself checking the spec every time i implement scroll-timeline-axis just to be sure.

spoilerthe documentation is often written for browser engine devs, not front-end devs/spoaster