From af33356e96e56310c66b47b6db913e1a61981ca3 Mon Sep 17 00:00:00 2001 From: Chris Craik Date: Mon, 1 Aug 2011 13:44:44 -0700 Subject: Support registering page swap callback, content inval bug:5062896 Depends on the following frameworks/base change: https://android-git.corp.google.com/g/#change,124879 a WebView may now register a page swap callback and content invalidate to benchmark tile rendering performance Change-Id: I97f6ed05cff12b11266a472163aab1f3b3ddc87e --- Source/WebCore/platform/graphics/android/GLWebViewState.h | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'Source/WebCore/platform/graphics/android/GLWebViewState.h') diff --git a/Source/WebCore/platform/graphics/android/GLWebViewState.h b/Source/WebCore/platform/graphics/android/GLWebViewState.h index 4f8d4fe..82b6f12 100644 --- a/Source/WebCore/platform/graphics/android/GLWebViewState.h +++ b/Source/WebCore/platform/graphics/android/GLWebViewState.h @@ -129,6 +129,12 @@ class LayerAndroid; // paint the tile and the second id (B) represents the pictureSet in which the // tile was invalidated by webkit. Thus, if A < B then tile is dirty. // +// Since invalidates can occur faster than a full tiled page update, the tiled +// page is protected by a 'lock' (m_baseLayerUpdate) that is set to true to +// defer updates to the background layer, giving the foreground time to render +// content instead of constantly flushing with invalidates. See +// lockBaseLayerUpdate() & unlockBaseLayerUpdate(). +// // Painting scheduling // ------------------- // -- cgit v1.1