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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Oct 14 11:17:09 PDT 2011


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





--- Comment #6 from Kenneth Russell <kbr at google.com>  2011-10-14 11:17:09 PST ---
(From update of attachment 111025)
View in context: https://bugs.webkit.org/attachment.cgi?id=111025&action=review

> Source/WebKit/chromium/public/WebGraphicsContext3D.h:144
> +    virtual void setVisibility(bool visible) = 0;

It seems clear that this is only useful for the compositor's context. What resources are released when called with argument "false"? Would it make more sense to just destroy the context and recreate it from scratch when visibility becomes true again? Without knowing more, it seems to me that any releasing of resources would be better done at the WebKit level.

Also, you would need to either temporarily provide an empty body for this or land all of the Chromium side implementations first (and roll Source/WebKit/chromium/DEPS) in order to fix the pure virtual compilation problem on the EWS bots.

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