Home | History | Annotate | Download | only in WebKit2

Lines Matching full:dirty

3781         dirty region, so ask it if it needs display rather than checking our own dirty region.
5126 by clearing the dirty region when a page has a custom representation (like a PDF).
5127 Also, avoid the issue where possible by not setting the dirty region in the same case.
7362 If the plug-in is transparent, clear the dirty rect before painting.
10447 (WebKit::DrawingAreaImpl::exitAcceleratedCompositingMode): Always update our dirty region,
10531 (WebKit::DrawingAreaImpl::updateBackingStoreState): Update our dirty region even if painting
10533 Rather than unite our existing dirty region with the page's new bounds, overwrite our dirty
10534 region with the page's new bounds. This prevents us from accumulating a dirty region that is
11404 Pass the right dirty rect to Plugin::paint
11414 (WebKit::PluginView::paint): Pass the dirty rect we calculated earlier to Plugin::paint,
11415 rather than just passing along the dirty rect that was passed into this function. This is
11904 The WebProcess implementation to response to UIProcess messages and actually do the dirty-work in WebCore:
12312 always dirty the entire page.
12624 The WebProcess implementation to response to UIProcess messages and actually do the dirty-work in WebCore: