Chromium Code Reviews| Index: content/browser/renderer_host/render_widget_host_view_aura.cc |
| =================================================================== |
| --- content/browser/renderer_host/render_widget_host_view_aura.cc (revision 192187) |
| +++ content/browser/renderer_host/render_widget_host_view_aura.cc (working copy) |
| @@ -771,6 +771,14 @@ |
| if (!compositor->HasObserver(this)) |
| compositor->AddObserver(this); |
| +// On Windows while resizing, the the resize locks makes us mis-paint a white |
| +// vertical strip (including the non-client area) if the content composition is |
| +// lagging the UI composition. So here we disable the throttling so that the UI |
| +// bits can draw ahead of the content thereby reducing the amount of whiteout. |
| +// Because this causes the content to be drawn at wrong sizes while resizing |
| +// we compensate by blocking the UI thread in Compositor::Draw() by issuing a |
| +// FinishAllRendering() if we are resizing. |
|
piman
2013/04/04 21:56:14
Can you file a bug to reinstate the logic once we
cpu_(ooo_6.6-7.5)
2013/04/05 17:05:51
I am not closing the existing bug because it is no
|
| +#if !defined (OS_WIN) |
| bool defer_compositor_lock = |
| can_lock_compositor_ == NO_PENDING_RENDERER_FRAME || |
| can_lock_compositor_ == NO_PENDING_COMMIT; |
| @@ -780,6 +788,7 @@ |
| resize_locks_.push_back(make_linked_ptr( |
| new ResizeLock(root_window, rect.size(), defer_compositor_lock))); |
| +#endif |
| } |
| } |
| window_->SetBounds(rect); |