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

[bugzilla-daemon at webkit.org]

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


Tom Hudson <tomhudson at google.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |alokp at chromium.org,
                   |                            |jamesr at chromium.org,
                   |                            |kbr at google.com,
                   |                            |reed at google.com,
                   |                            |tomhudson at google.com,
                   |                            |vangelis at chromium.org




--- Comment #2 from Tom Hudson <tomhudson at google.com>  2011-07-26 13:02:23 PST ---
This is a proof-of-concept patch to solve http://code.google.com/p/chromium/issues/detail?id=86369. The issue is that a webpage that:
1. creates a canvas
2. creates a popup window
3. removes the canvas from the main window
4. adds the canvas to the popup window
did not work using the Chromium accelerated canvas.

The patch has two parts:
1. correctly reinitialize drawing when the canvas is added to a new document (and correspondingly shut down drawing when the canvas is removed from a document)
2. save the image when the canvas is removed from a document, and re-upload it to the graphics hardware when added to a new document

Known problems:
1. we're not sure how to test aside from manually
2. manual testing is fraught because the GPU renderer is frequently failing over into software

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