These technical documents provide an in-depth analysis of Chromium's compositor property tree mechanics, focusing on the differences between two methods for updating transform nodes: SetTransformChanged() and SetScrollOffset(). The sources explain that both methods, when paired with the needs_local_transform_update and set_needs_update(true) flags, trigger the recalculation of a node's transform matrix. The critical distinction lies in their intended use and impact on performance and correctness: SetScrollOffset() is preferred for content scrolling because it correctly updates the scroll offset used by features like sticky positioning and provides accurate damage attribution (e.g., kCompositorScroll), whereas SetTransformChanged() is reserved for generic, non-scroll-based transform changes, such as the elastic overscroll effect. For the elastic overscroll scenario specifically, the sources conclude that using SetTransformChanged() is correct and has minimal performance cost, as the change is handled efficiently by the GPU and does not benefit from the scroll-specific damage optimizations offered by SetScrollOffset().
