The test started failing on Chromium after http://trac.webkit.org/changeset/94061
Original Chromium bug report: http://code.google.com/p/chromium/issues/detail?id=94737
Created attachment 105642 [details] Patch
Comment on attachment 105642 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=105642&action=review > Source/WebCore/bindings/v8/V8AbstractEventListener.cpp:185 > // FIXME: Add example, and reference to bug entry. Since this code is being modified, can we address the FIXME here?
Comment on attachment 105642 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=105642&action=review >> Source/WebCore/bindings/v8/V8AbstractEventListener.cpp:185 >> // FIXME: Add example, and reference to bug entry. > > Since this code is being modified, can we address the FIXME here? I think we should simply remove this FIXME as this behavior is unambiguously described in the spec( http://www.w3.org/TR/html5/webappapis.html#event-handler-attributes) which reads as following: "When an event handler's Function object is invoked, its call() callback must be invoked with one argument, set to the Event object of the event in question. The handler's return value must then be processed as follows: If the event type is mouseover If the return value is a boolean with the value true, then the event must be canceled. If the event object is a BeforeUnloadEvent object If the return value is a string, and the event object's returnValue attribute's value is the empty string, then set the returnValue attribute's value to the return value. Otherwise If the return value is a boolean with the value false, then the event must be canceled."
Created attachment 105748 [details] Patch
Created attachment 105760 [details] Patch
(In reply to comment #6) > Created an attachment (id=105760) [details] > Patch Added a couple more tests for window.onerror.
Committed r94643: <http://trac.webkit.org/changeset/94643>