WebGLContextEvent should have its own JS wrapper
Created attachment 105887 [details] Patch
Comment on attachment 105887 [details] Patch Attachment 105887 [details] did not pass qt-ews (qt): Output: http://queues.webkit.org/results/9581072
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
Created attachment 105978 [details] Patch
Created attachment 105982 [details] Patch
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
Committed r94319: <http://trac.webkit.org/changeset/94319>
(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?