diff options
| author | scottbyer@google.com <scottbyer@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-09-10 18:59:47 +0000 |
|---|---|---|
| committer | scottbyer@google.com <scottbyer@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-09-10 18:59:47 +0000 |
| commit | fbeec7b0ca0085d379da8672d887d11c4eea0298 (patch) | |
| tree | 4a8f98428b327bb3b2e65fab2bf0dcdc3895c88a /DEPS | |
| parent | dc1a80d7c830a09c8f5281af69fc746a86f558b7 (diff) | |
| download | chromium_src-fbeec7b0ca0085d379da8672d887d11c4eea0298.zip chromium_src-fbeec7b0ca0085d379da8672d887d11c4eea0298.tar.gz chromium_src-fbeec7b0ca0085d379da8672d887d11c4eea0298.tar.bz2 | |
The fix for http://code.google.com/p/chromium-os/issues/detail?id=5987
sets the initial allocation for a widget when a size is passed in to
WidgetGtk::Init(). The timing of the init call as part of creating a
new tab contents view means that the arrangment of the hierarchy isn't
complete yet, so incorrect contents get shown. This goes back to the original behavior which is to ignore the initial size request (it's now ignored at the TabContentsViewGtk::CreateView level instead of being implicitly ignored in the WidgetGtk::Init code).
BUG=53870
TEST=Create new tabs, no flash of old tabs seen.
Review URL: http://codereview.chromium.org/3290016
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@59122 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'DEPS')
0 files changed, 0 insertions, 0 deletions