[Webkit-unassigned] [Bug 60770] [Qt] QtWebKit bridge assignToHTMLImageElement() results in invalid Image for WebGLRenderingContext

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed May 18 04:03:00 PDT 2011


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


Benjamin Poulain <benjamin at webkit.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|QtWebKit bridge             |[Qt] QtWebKit bridge
                   |assignToHTMLImageElement()  |assignToHTMLImageElement()
                   |results in invalid Image    |results in invalid Image
                   |                            |for WebGLRenderingContext
           Keywords|                            |Qt, QtTriaged
           Priority|P2                          |P5
                 CC|                            |benjamin at webkit.org,
                   |                            |jarkko.j.sakkinen at gmail.com
                   |                            |, noam.rosenthal at nokia.com




--- Comment #3 from Benjamin Poulain <benjamin at webkit.org>  2011-05-18 04:03:00 PST ---
The patch looks more like a big workaround.

If an origin has to be set, I would rather see the origin of the frame.

The code of WebGLRenderingContext.cpp might also be bogus. Is there no way to reproduce the same issue by manipulating the image directly or with Canvas?

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