[Webkit-unassigned] [Bug 86504] [Chromium] Expose WebView to graphics context creation.

[bugzilla-daemon at webkit.org]

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





--- Comment #13 from James Robinson <jamesr at chromium.org>  2012-05-15 13:26:03 PST ---
(In reply to comment #12)
> (In reply to comment #11)
> > The rules for contexts in WebKit are pretty simple:
> > 
> > 2.) Offscreen contexts are not associated with anything and are able to share resources with each other and with any or all onscreen contexts (including ones that don't exist yet when the offscreen context is created).
> 
> But at least for WebGL, we seem to know which WebView is initiating the request. What are other cases where offscreen contexts are created?(In reply to comment #11)

Canvas 2d is the case that will probably be most bothersome for you.  For canvas, every canvas context (regardless of WebView) shares one GC3D.  Each canvas context may share a texture with one WebView's context (for compositing) and will definitely share textures with other canvas contexts in the page to do things like draw from one canvas into another canvas.

Even for WebGL I think that the WebView initiating the request is not enough - WebGL canvases can move from one WebView to another and they can use or export resources to canvas or WebGL contexts associated with different WebViews.


> > The rules for contexts in WebKit are pretty simple:
> > 
> 
> > 2.) Offscreen contexts are not associated with anything and are able to share resources with each other and with any or all onscreen contexts (including ones that don't exist yet when the offscreen context is created).
> 
> Within a render process, some WebViews might be guests and some might not be.

I can't see how that would work.

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