[Webkit-unassigned] [Bug 65202] Support moving GPU accelerated canvas to a new document (popup window)

Tue Jul 26 13:47:28 PDT 2011

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

--- Comment #7 from Alok Priyadarshi <alokp at chromium.org>  2011-07-26 13:47:28 PST ---
(In reply to comment #6)
> There are potentially multiple canvases using the shared context, however. What do you do when a subset of those canvases move to a different compositor?

Yes. I was suggesting re-parenting only in the case when the whole document is moved to another page. When the document moves, don't all canvases move along as well? I am fuzzy on difference between WebKit's page and Javascript's document.

When individual canvases are moved, Tom's current approach would work.

BTW from resource consumption aspect, there may be benefits of having a shared GraphicsContext3D per process.

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