diff options
| author | bokan@chromium.org <bokan@chromium.org> | 2014-10-29 22:29:47 +0000 |
|---|---|---|
| committer | bokan@chromium.org <bokan@chromium.org> | 2014-10-29 22:29:47 +0000 |
| commit | 14150d03adf77c8798424654c225a31b8e4e0eff (patch) | |
| tree | 7c01c92cd28c304838108c2ce346573e49eac845 /third_party/WebKit/LayoutTests/fast/parser/innerhtml-with-prefixed-elements-expected.txt | |
| parent | 9ad770830ce42bb8a3129ffbc0fafa996268a60f (diff) | |
| download | chromium_src-14150d03adf77c8798424654c225a31b8e4e0eff.zip chromium_src-14150d03adf77c8798424654c225a31b8e4e0eff.tar.gz chromium_src-14150d03adf77c8798424654c225a31b8e4e0eff.tar.bz2 | |
Move didUpdateTopControls call from WebViewImpl::resize to layoutUpdated.
This call was put there recently in case we received a change to the top
controls before the WebView had a size. Unfortunately, the FrameView doesn't
get resized until after layout, meaning when didUpdateTopControls gets
called, the PinchViewport has been resized but the FrameView hasn't. This
led to an incorrect maximumScrollPosition being calculated since the
FrameView adjustment assumes the two viewports have the same aspect ratio.
BUG=428193
Review URL: https://codereview.chromium.org/688083002
git-svn-id: svn://svn.chromium.org/blink/trunk@184608 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Diffstat (limited to 'third_party/WebKit/LayoutTests/fast/parser/innerhtml-with-prefixed-elements-expected.txt')
0 files changed, 0 insertions, 0 deletions