[Webkit-unassigned] [Bug 100718] Invalidate non-composited content host when page scale factor changes

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Nov 19 14:10:25 PST 2012


https://bugs.webkit.org/show_bug.cgi?id=100718


Grace Kloba <klobag at chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |klobag at chromium.org




--- Comment #12 from Grace Kloba <klobag at chromium.org>  2012-11-19 14:12:23 PST ---
(In reply to comment #11)
> (In reply to comment #8)
> > 3. Supposedly if the compositor wants to change the contents scale to repaint a high-res version, it is the compositor's responsibility to invalidate the layer. The compositor actually does it, but on the RenderView layer, which is a no-op since RenderView layer is non-drawing layer because its content is stolen by the non-composited content layer.
> 
> WebCore is responsible for this property, not the compositor.

NonCompositedContentHost is owned by WebViewImpl in WebKit. So it seems reasonable to do the way the patch does. 

When WebCore needs to invalidate a region, it invalids a rect. This propagates to NonCompositedContentHost through WebViewImpl::invalidateRect. But when scale factor changed, we want to invalidate everything, not just the visible part.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the webkit-unassigned mailing list