android: Don't use partial damage with SurfaceControl.
When using the SurfaceControl API, the damage rect specified for doing partial invalidations of a Surface should be in the content space (including pre-transform for rotations). Since we were currently setting it in screen space, this caused a rendering bug on devices using the damage rect. For now, avoid setting any damage rect on the Surface. This will result in full invalidation of the Surface for each draw. While its not ideal, its consistent with SurfaceView based rendering path. We can attempt to use partial damage going forward, with some benchmarking, once SurfaceControl is launched/stable. Note that we still take advantage of only compositing the damaged region in chrome's display compositor. This change only makes it so this region is not forwarded to the system compositor. R=zmo@chromium.org Bug: 988857 Change-Id: I625dcda578e90aa81324c4e35f739bd44b83c3f8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1725416 Auto-Submit: Khushal <khushalsagar@chromium.org> Reviewed-by:Zhenyao Mo <zmo@chromium.org> Commit-Queue: Khushal <khushalsagar@chromium.org> Cr-Commit-Position: refs/heads/master@{#682145}
Showing
Please register or sign in to comment