summaryrefslogtreecommitdiff
path: root/Source/WebKit/chromium/src/ApplicationCacheHost.cpp
diff options
context:
space:
mode:
Diffstat (limited to 'Source/WebKit/chromium/src/ApplicationCacheHost.cpp')
-rw-r--r--Source/WebKit/chromium/src/ApplicationCacheHost.cpp8
1 files changed, 5 insertions, 3 deletions
diff --git a/Source/WebKit/chromium/src/ApplicationCacheHost.cpp b/Source/WebKit/chromium/src/ApplicationCacheHost.cpp
index 73f258b0c..bbf740dfd 100644
--- a/Source/WebKit/chromium/src/ApplicationCacheHost.cpp
+++ b/Source/WebKit/chromium/src/ApplicationCacheHost.cpp
@@ -193,10 +193,12 @@ void ApplicationCacheHost::maybeLoadFallbackSynchronously(const ResourceRequest&
// N/A to the chromium port
}
-bool ApplicationCacheHost::canCacheInPageCache() const
+bool ApplicationCacheHost::canCacheInPageCache()
{
- // N/A to the chromium port which doesn't use the page cache.
- return false;
+ // Chromium doesn't use the page cache, however, that's controlled by WebCore::Settings, which has usesPageCache() return
+ // false. So we return an hyptothetical here: Chromium won't end up using the PageCache, but the statistics in PageCache.cpp
+ // will be reported correctly for re-evaluating that decision.
+ return !isApplicationCacheEnabled() || status() == UNCACHED;
}
void ApplicationCacheHost::setDOMApplicationCache(DOMApplicationCache* domApplicationCache)