diff options
| author | danakj@chromium.org <danakj@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-07-19 01:48:46 +0000 |
|---|---|---|
| committer | danakj@chromium.org <danakj@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-07-19 01:48:46 +0000 |
| commit | 9992898cbe9872e5b5e0b9cead5b02ea9e830756 (patch) | |
| tree | 135d47e6ce6ae51e5e49fdff446464c922b187c1 /remoting/protocol/errors.h | |
| parent | 78ad45541eb6dfadd0edbaff2a3d8f173ad21f2a (diff) | |
| download | chromium_src-9992898cbe9872e5b5e0b9cead5b02ea9e830756.zip chromium_src-9992898cbe9872e5b5e0b9cead5b02ea9e830756.tar.gz chromium_src-9992898cbe9872e5b5e0b9cead5b02ea9e830756.tar.bz2 | |
cc: Fix hud bounds on the first frame it is displayed.
We were computing the huds bounds in Update() and then expecting
to push a correct content_bounds based on those bounds. However
content_bounds are computed in CalcDrawProps which happens before
Update, so we are actually pushing the content_bounds based on
the previous frame's bounds.
This means that if we don't push properties again for the hud
layer due to early outs, we have the wrong bounds on the impl
side forever.
Compute the bounds in CalculateContentsScale instead of Update,
which is during CalcDrawProps, and will have the right
content_bounds for the frame as a result.
R=enne
BUG=261506
Review URL: https://chromiumcodereview.appspot.com/19471010
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212495 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'remoting/protocol/errors.h')
0 files changed, 0 insertions, 0 deletions