Rename WebKeyValueStorageManagerProxy to WebKeyValueStorageManager
https://bugs.webkit.org/show_bug.cgi?id=116361

Reviewed by Andreas Kling.

There's nothing proxy about this class anymore!

* UIProcess/API/C/WKAPICast.h:
* UIProcess/API/C/WKContext.cpp:
* UIProcess/API/C/WKKeyValueStorageManager.cpp:
* UIProcess/WebKeyValueStorageManager.cpp: Renamed from Source/WebKit2/UIProcess/WebKeyValueStorageManagerProxy.cpp.
* UIProcess/WebKeyValueStorageManager.h: Renamed from Source/WebKit2/UIProcess/WebKeyValueStorageManagerProxy.h.
* WebKit2.xcodeproj/project.pbxproj:

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@150306 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Headers and footers will sometimes disappear and re-appear during page loads
https://bugs.webkit.org/show_bug.cgi?id=116336
-and corresponding-
<rdar://problem/13886753>

Reviewed by Simon Fraser.

This patch changes the WebCore-level API that WebKit uses to create a banner. 
Specifically this patch removes FrameView::setWantsLayerForHeader(), which created 
and returned a layer. Instead, WK2 will call Page::addHeaderWithHeight(). When the 
layer has been created, it will call back into WK2 via ChromeClient. This will 
allow WebCore to re-create the header/footer layers as needed whenever the 
FrameView/RenderLayerCompositor have been destroyed and recreated.

Source/WebCore: 

Remove references to old FrameView functions. Add references to new Page 
functions.
* WebCore.exp.in:

New ChromeClient functions will pass the new layers up to WK2.
* page/ChromeClient.h:
(WebCore::ChromeClient::didAddHeaderLayer):
(WebCore::ChromeClient::didAddFooterLayer):
(ChromeClient):

Remove setWantsLayerForHeader/Footer.
* page/FrameView.cpp:
* page/FrameView.h:
(FrameView):

Page now caches the header and footer height. When the FrameView/RLC have been 
destroyed, and the cached layer/height information on those classes has been lost, 
this data on Page will persist so that we can build the layers back up.
* page/Page.cpp:
(WebCore::Page::Page):
(WebCore::Page::addHeaderWithHeight):
(WebCore::Page::addFooterWithHeight):
* page/Page.h:
(WebCore::Page::headerHeight):
(WebCore::Page::footerHeight):

As soon as the root gets a backing, recreate the header and footer layers if 
needed.
* rendering/RenderLayerCompositor.cpp:
(WebCore::RenderLayerCompositor::updateBacking):

Call into ChromeClient.
(WebCore::RenderLayerCompositor::updateLayerForHeader):
(WebCore::RenderLayerCompositor::updateLayerForFooter):

Source/WebKit2: 

Send the layers over to PageBanner.
* WebProcess/WebCoreSupport/WebChromeClient.cpp:
(WebKit::WebChromeClient::didAddHeaderLayer):
(WebKit::WebChromeClient::didAddFooterLayer):
* WebProcess/WebCoreSupport/WebChromeClient.h:
(WebChromeClient):

PageBanner::addToPage() now does much less work since it can’t get the parent 
layer right away. The work that is used to do once it had the parent layer is now 
performed in didAddParentLayer()
* WebProcess/WebPage/PageBanner.cpp:
(WebKit::PageBanner::didAddParentLayer):
* WebProcess/WebPage/PageBanner.h:
* WebProcess/WebPage/mac/PageBannerMac.mm:
(WebKit::PageBanner::addToPage):
(WebKit::PageBanner::didAddParentLayer):



git-svn-id: http://svn.webkit.org/repository/webkit/trunk@150307 268f45cc-cd09-0410-ab3c-d52691b4dbfc