Searched refs:areMemoryCacheClientCallsEnabled (Results 1 – 10 of 10) sorted by relevance
46 encoder->encode(areMemoryCacheClientCallsEnabled); in encode()87 if (!decoder->decode(parameters.areMemoryCacheClientCallsEnabled)) in decode()
61 bool areMemoryCacheClientCallsEnabled; member
284 bool areMemoryCacheClientCallsEnabled() const { return m_areMemoryCacheClientCallsEnabled; } in areMemoryCacheClientCallsEnabled() function
680 if (page->areMemoryCacheClientCallsEnabled()) { in suspendPostAttachCallbacks()
3128 if (!page->areMemoryCacheClientCallsEnabled()) { in loadedResourceFromMemoryCache()3509 ASSERT(m_frame->page()->areMemoryCacheClientCallsEnabled()); in tellClientAboutPastMemoryCacheLoads()
217 setMemoryCacheMessagesEnabled(parameters.areMemoryCacheClientCallsEnabled); in WebPage()
2813 parameters.areMemoryCacheClientCallsEnabled = m_areMemoryCacheClientCallsEnabled; in creationParameters()
2401 return _private->page->areMemoryCacheClientCallsEnabled();
10794 Encode and decode areMemoryCacheClientCallsEnabled.10797 Add areMemoryCacheClientCallsEnabled member variable.10807 Set areMemoryCacheClientCallsEnabled.
57278 … there's no inspector or client call needed. Added code to check areMemoryCacheClientCallsEnabled57286 * page/Page.h: Added setMemoryCacheClientCallsEnabled, areMemoryCacheClientCallsEnabled,