Bug 67352

Summary: WebGLContextEvent should have its own JS wrapper
Product: WebKit Reporter: Sam Weinig <sam>
Component: New BugsAssignee: Sam Weinig <sam>
Status: RESOLVED FIXED    
Severity: Normal CC: dglazkov, jamesr, webkit.review.bot
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch
none
Patch
none
Patch andersca: review+, webkit.review.bot: commit-queue-

Sam Weinig
Reported 2011-08-31 19:51:21 PDT
WebGLContextEvent should have its own JS wrapper
Attachments
Patch (19.84 KB, patch)
2011-08-31 19:55 PDT, Sam Weinig
no flags
Patch (20.38 KB, patch)
2011-09-01 09:37 PDT, Sam Weinig
no flags
Patch (20.48 KB, patch)
2011-09-01 09:52 PDT, Sam Weinig
andersca: review+
webkit.review.bot: commit-queue-
Sam Weinig
Comment 1 2011-08-31 19:55:10 PDT
Early Warning System Bot
Comment 2 2011-08-31 20:03:24 PDT
WebKit Review Bot
Comment 3 2011-08-31 20:34:38 PDT
Comment on attachment 105887 [details] Patch Attachment 105887 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/9578222 New failing tests: fast/canvas/webgl/WebGLContextEvent.html
Sam Weinig
Comment 4 2011-09-01 09:37:35 PDT
Sam Weinig
Comment 5 2011-09-01 09:52:15 PDT
WebKit Review Bot
Comment 6 2011-09-01 10:54:48 PDT
Comment on attachment 105982 [details] Patch Attachment 105982 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/9586082 New failing tests: fast/canvas/webgl/WebGLContextEvent.html
Sam Weinig
Comment 7 2011-09-01 11:19:44 PDT
James Robinson
Comment 8 2011-09-01 11:44:53 PDT
(In reply to comment #6) > (From update of attachment 105982 [details]) > Attachment 105982 [details] did not pass chromium-ews (chromium-xvfb): > Output: http://queues.webkit.org/results/9586082 > > New failing tests: > fast/canvas/webgl/WebGLContextEvent.html Unsurprisingly this is now failing on the actual waterfall. Why did you land it if you knew it would make the tree red? Do you have any pointers about what to do to fix this?
Note You need to log in before you can comment on or make changes to this bug.