[Webkit-unassigned] [Bug 68905] [chromium] Add a setVisibility method to WebGraphicsContext3D.

[bugzilla-daemon at webkit.org]

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





--- Comment #10 from Michal Mocny <mmocny at chromium.org>  2011-10-14 12:56:53 PST ---
(In reply to comment #9)
> (In reply to comment #7)
> > I'm not sure that I understand the comment about being compositor specific. One could imagine other contexts (like Pepper3D or WebGL) wanting to release some resources if they aren't visible. E.g. AFAIK for WebGL, we double buffer; we could release one of those buffers in the GLES2Decoder if we had the appropriate signals plumbed (perhaps we'd only want to do that when the compositor context is not visible?).
> 
> The signaling in the current patch is compositor specific so the intent wasn't clear.
> 
> The direction WebGL is going is to move the back buffer handling up to WebKit. See bug 53201. This means that any discarding of secondary buffers could be done in common code without plumbing anything through the WebGraphicsContext3D interface. The issue of secondary buffers doesn't really become relevant for WebGL until threaded compositing is in place though.
> 
> I'd still like to see the Chromium side patch that uses this signal.

The Chromium patch is: http://codereview.chromium.org/7890046

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