-
bdakin@apple.com authored
incremental layout https://bugs.webkit.org/show_bug.cgi?id=115330 -and corresponding- <rdar://problem/12722365> Reviewed by Simon Fraser. Source/WebCore: To meet the needs of all of our clients, we really need two milestones. One indicating that a layout has happened after setVisualUpdatesAllowed(true), and another indicating that painting has happened. If layout is needed when setVisualUpdatesAllowed(true) is called, we need to update it so that we can guarantee the first paint is really happening at this time. Also fire the DidFirstLayoutAfterSuppressedIncrementalRendering milestone, and call add DidFirstPaintAfterSuppressedIncrementalRendering to the FrameView's pending paint milestones. up the painting milestone. * dom/Document.cpp: (WebCore::Document::setVisualUpdatesAllowed): FrameView now stores m_milestonesPendingPaint. We'll send and clear them once we have painted. * page/FrameView.cpp: (WebCore::FrameView::FrameView): (WebCore::FrameView::paintContents): (WebCore::FrameView::addPaintPendingMilestones): (WebCore::FrameView::firePaintRelatedMilestones): * page/FrameView.h: (WebCore::FrameView::milestonesPendingPaint): Two new milestones. * page/LayoutMilestones.h: (WebCore): We don't need m_headerLayerAwaitingFirstFlush anymore since we can use FrameView's pending paint milestones instead. * rendering/RenderLayerCompositor.cpp: (WebCore::RenderLayerCompositor::RenderLayerCompositor): (WebCore::RenderLayerCompositor::flushPendingLayerChanges): (WebCore::RenderLayerCompositor::updateLayerForHeader): * rendering/RenderLayerCompositor.h: (RenderLayerCompositor): Source/WebKit2: Two new millstones. * Shared/API/c/WKPageLoadTypes.h: * Shared/API/c/WKSharedAPICast.h: (WebKit::toWKLayoutMilestones): (WebKit::toLayoutMilestones): This null-check is necessary now since this code ends up running at WebFrame::init() time while we're setting up the Document. setVisualUpdatesAllowed(true) has always been called as a part of that process, and now the updateLayout(), ends up calling this code too, but we don't actually have a mainFrame yet since it's still being created. * WebProcess/WebCoreSupport/WebChromeClient.cpp: (WebKit::findLargestFrameInFrameSet): git-svn-id: http://svn.webkit.org/repository/webkit/trunk@149317 268f45cc-cd09-0410-ab3c-d52691b4dbfc
72d30d8b