--enable-blink-features=FractionalScrollOffsets to go green.
Blink stores scroll offsets internally. When DSF or zoom produces a fractional physical-pixel offset, does the scroller keep the fraction or truncate to int? Tested by scrolling to a position that at 150% zoom (simulated via CSS zoom) maps to a fractional physical pixel, then reading back.
A scroll-snap container with items at positions that produce fractional physical-pixel offsets. Without FSO, snapping truncates and can land at the wrong integer. With FSO, the fraction is preserved.
Set scrollTop to a fractional CSS-pixel value and verify
getBoundingClientRect().top of a child reflects the sub-pixel
shift. The web API floors scrollTop (web compat) but the rendering
offset should still move the child by a fractional amount.
Simulates the original 2014 bug: applying many small fractional scroll
deltas via scrollBy(). Without FSO each delta gets truncated
and total drift accumulates. With FSO, the final position is accurate.