Make surface scale set after construction immediately effective
In the attached bug launching some Android applications such as Adobe Acrobat results in a flash where shadow bounds are twice larger than they should be. This is due to the shadow bounds being computed before the first commit even though the pending scale is correctly set which results in the default hard-coded scale (=1.0) being used. The pending scale set via SetScale() only becomes effective after a commit. Rather than implicitly relying on this commit for the scale to be effective exo::Display now commits it explicitly right after setting it. Bug: b/118827262 Change-Id: I4bd6cf395ba186be2dfd4f4e3b42e6591bd5382d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1612937Reviewed-by:Mitsuru Oshima <oshima@chromium.org> Commit-Queue: Philippe Liard <pliard@google.com> Auto-Submit: Philippe Liard <pliard@google.com> Cr-Commit-Position: refs/heads/master@{#660659}
Showing
Please register or sign in to comment