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

Unified Diff: content/browser/android/content_view_core_impl.h

Issue 11854013: Use input events to improve vsync scheduling (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: Don't set last-input-for-vsync bit on pages with touch handlers. Created 7 years, 11 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
Index: content/browser/android/content_view_core_impl.h
diff --git a/content/browser/android/content_view_core_impl.h b/content/browser/android/content_view_core_impl.h
index 11ca62835e22d6318027209b038bc7856abc254d..269a2e27980919f9aece299349e648514b93d883 100644
--- a/content/browser/android/content_view_core_impl.h
+++ b/content/browser/android/content_view_core_impl.h
@@ -308,6 +308,9 @@ class ContentViewCoreImpl : public ContentViewCore,
// Whether input events will be consistently delivered at vsync time.
bool input_events_delivered_at_vsync_;
+ // Whether the page has JavaScript handlers for touch events.
+ bool has_touch_event_handlers_;
+
// Whether a new frame from the renderer is waiting to be displayed by the
// browser compositor.
bool renderer_frame_pending_;

Powered by Google App Engine
This is Rietveld 408576698