Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(171)

Unified Diff: chrome/browser/renderer_host/render_widget_host.cc

Issue 3176025: RenderWidget::WasRestored should repaint the view when accelerated compositin... (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src/
Patch Set: Created 10 years, 4 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: chrome/browser/renderer_host/render_widget_host.cc
===================================================================
--- chrome/browser/renderer_host/render_widget_host.cc (revision 56813)
+++ chrome/browser/renderer_host/render_widget_host.cc (working copy)
@@ -225,8 +225,11 @@
BackingStore* backing_store = BackingStoreManager::Lookup(this);
// If we already have a backing store for this widget, then we don't need to
// repaint on restore _unless_ we know that our backing store is invalid.
+ // When accelerated compositing is on, we must always repaint, even when
+ // the backing store exists.
bool needs_repainting;
- if (needs_repainting_on_restore_ || !backing_store) {
+ if (needs_repainting_on_restore_ || !backing_store ||
+ is_gpu_rendering_active()) {
needs_repainting = true;
needs_repainting_on_restore_ = false;
} else {
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698