These sources provide an extensive technical explanation of how the Chrome compositor manages dynamic properties, specifically focusing on transformations and scrolling, using a structure called PropertyTrees. The core mechanism for efficiency relies on granular dirty state propagation: when a property changes (like a scroll offset or animation), only the affected TransformNodes are marked as dirty (needs_local_transform_update) rather than forcing a full re-evaluation of the entire scene. The process, governed by UpdateTransformTree, ensures that changes—including complex interactions like elastic overscroll, fixed/sticky positioning, and pinch-zoom—are translated into updated screen-space layer matrices (transforms) by traversing only the dependent edges, thereby minimizing computational cost during each render frame. The sources clarify the tight coordination between the ScrollTree (which tracks offsets) and the TransformTree (which incorporates those offsets into actual layer movement matrices).