Collect some basic data and explore sending simple compositor frame deltas.
Initial target include sending replacement diff and no insertion or deletion to avoid changing data structure:
- animation
- scrolling
- replacing resource id for texture
- (Local)SurfaceId per crbug.com/714379
After MUS salamander, compositor frame would look different for general web content (possibly instead of quads, send actual layers+property trees). Cases such as Canvas, WebGL, and, UI would continue to use compositor frame. Need to figure out what compositor frame diff looks like for these cases for long term.
Comment 1 by danakj@chromium.org
, Jun 13 2017