diff options
| author | asargent@chromium.org <asargent@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-02-01 00:21:46 +0000 |
|---|---|---|
| committer | asargent@chromium.org <asargent@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-02-01 00:21:46 +0000 |
| commit | 76f5e03b8e08272fb542dce8359b20144e8f60ce (patch) | |
| tree | f13e5cf214529d2608aa7a1cb6b9b09c1442452a /ash/tooltips | |
| parent | 96ab38bbd94221053b71fa6f0cfc73c5daae07ec (diff) | |
| download | chromium_src-76f5e03b8e08272fb542dce8359b20144e8f60ce.zip chromium_src-76f5e03b8e08272fb542dce8359b20144e8f60ce.tar.gz chromium_src-76f5e03b8e08272fb542dce8359b20144e8f60ce.tar.bz2 | |
Revert 119977 - Defer render_widget draw until host window is available
In accelerated compositing mode we can't start rendering until the
native window (HWND/gtk widget) are created on Windows and GTK without
aura. For most render_widgets the code today is racy, but for
window.open() and similar creation paths this is a race that we pretty
much always lose. This defers the first DoDeferredUpdate on a render_widget
until its host_window_ is available.
Also defers querying for GL_CHROMIUM_supports_swapbuffers_callback
extension until the first draw, since the context isn't ready until the
host window is available.
BUG=106815
TEST=start with --force-compositing-mode and --show-fps-counter, load up
a page that uses window.open() to open a popup, and confirm that the
popup is in compositing mode
Review URL: http://codereview.chromium.org/9225050
TBR=jamesr@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9316015
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@119996 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'ash/tooltips')
0 files changed, 0 insertions, 0 deletions