[Webkit-unassigned] [Bug 55257] Support creating compositing layers for scrollable frames and iframes

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Apr 14 14:53:28 PDT 2011


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





--- Comment #40 from Daniel Sievers <sievers at google.com>  2011-04-14 14:53:28 PST ---

> > Also it seems like the overflow would have to be detected by the child in one form or another anyway, because it has to happen after the child FrameView has completed layout.
> > 
> > About using 'RenderLayerCompositor::m_forceCompositing', that seems to work fine too. However, not sure what a good place to force it would be. Somewhere at the end of FrameView::layout() is called? It could probably go into FrameView::layout before updateCompositingLayers() is called after the actual layout, so that if the document changes and does not overflow anymore we can disable m_forceCompositing again (compositing will still have to be updated because we don't know if 'force' was the only reason to turn it on).
> 
> Something like that.
> 

Ok, see new patch.

I have tried to add tests for entering and leaving compositing when the iframe content changes, but can someone tell me if there is a way to do this that is not conceptually flaky and ugly with respect to the setTimeout() (which I copied from other tests)?

-- 
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