A snap area that moves under :hover -- a scaled card, a
lifted tile -- changes the snap container's data, so the post-layout
re-snap pulls the scroll offset to the area's new position. That moves the
content out from under the pointer, :hover drops, the area
moves back, and the next re-snap pulls the offset the other way. The offset
oscillates between two values for as long as the pointer rests there:
reported in 2021 as "terrible scroll jank and jiggle".
The CL still re-snaps to the same snap areas, it just leaves the scroll
offset alone when the area moved because of :hover.
css-scroll-snap explicitly leaves the scrolling behaviour of re-snapping to
the same box up to the UA. Behind the default-on
ScrollSnapNoHoverAdjustment kill switch.
100,125,100,125,... -- a new offset every frame, and the
item is caught mid-flip at full size.
100,100,100,..., the hovered item simply stays
scaled.
:hover. Leaving it
moves the area back just the same, so it is now set on both
transitions.fast/scroll-snap/resnap-hover-snap-area-change.html fails
with --disable-blink-features=ScrollSnapNoHoverAdjustment
with exactly the oscillation
(125,100,125,100,...) and passes with it.fast/scroll-snap, wpt/css/css-scroll-snap
and fast/scrolling: 372 tests as expected; the one outlier
passes in isolation.*Snap* / *ScrollableArea* unit tests
pass.