[Webkit-unassigned] [Bug 58834] New: [chromium] Draw the root/"non-composited content" in compositor side
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Apr 18 14:53:23 PDT 2011
https://bugs.webkit.org/show_bug.cgi?id=58834
Summary: [chromium] Draw the root/"non-composited content" in
compositor side
Product: WebKit
Version: 528+ (Nightly build)
Platform: PC
OS/Version: Mac OS X 10.5
Status: NEW
Severity: Normal
Priority: P2
Component: New Bugs
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: jamesr at chromium.org
CC: enne at google.com, nduca at chromium.org
Blocks: 58799
Currently the root content (what the WK2 compositor calls the non-composited content) is special-cased by LayerRendererChromium and rendered differently from how *LayerChromium or CCLayerImpls are rendered. We need to somehow render this from the compositor side.
I currently think that the easiest way to do this will be to create a CCLayerImpl of the appropriate type (probably the same type as ContentLayerChromiums have) and during the tree syncing phase set it up at the appropriate point. From the compositor thread side the "root layer" content can be treated the same way as any other layer, IMO. This will be clearer when the other issues blocking bug 58799 are resolved.
--
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