Note also https://github.com/whatwg/html/issues/2296 which is kind of related to this.

Tested this issue on Mac OS 10.12 using chrome latest Dev M57-57.0.2987.8 by following steps mentioned in the original comment. By opening the provided html file baz.html observed the below content displayed saying "event.defaultPrevented: true, value: true" "event.defaultPrevented: false, value: false" in first 2 lines.

Tested the same on other browsers like firefox and safari observed the same behavior over there as well.

bzbarsky@ Could you please let us know on which browser this issue is working fine?

Thanks!

> Tested the same on other browsers like firefox and safari
> observed the same behavior over there as well.

I did say Firefox has the same behavior, yes.  But Safari does not.  Safari 10 shows:

  event.defaultPrevented: false, value: true
  event.defaultPrevented: true, value: false

and so does WebKit nightly.  Are you sure you tested Safari?

> Could you please let us know on which browser this issue is working fine?

I said this in the initial report: Safari and Edge.

Note that I filed https://github.com/whatwg/html/issues/2296 on some subtle aspects of what's going on here on the spec end, so you may want to wait for that to get sorted out before making behavior changes here.

Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Surprising that WebKit would get this right and blink would get it wrong.  Did we regress or did WebKit fix it at some point? tkent@ can you please triage?

WebKit has been doing a ton of IDL and HTML spec compliance work in the last year or two.  There's all sorts of stuff that they get right that you guys get wrong, and not surprising at all to run into things like that, fwiw.

The spec around this has recently been clarified, but the bug here still stands. I added a bunch of tests around error event handling which are present in http://w3c-test.org/html/webappapis/scripting/events/event-handler-processing-algorithm-error/.

Chrome fails the following three:

- http://w3c-test.org/html/webappapis/scripting/events/event-handler-processing-algorithm-error/window-synthetic-event.html
- http://w3c-test.org/html/webappapis/scripting/events/event-handler-processing-algorithm-error/synthetic-errorevent-click.worker.html
- http://w3c-test.org/html/webappapis/scripting/events/event-handler-processing-algorithm-error/workerglobalscope-synthetic-errorevent.worker.html

however the last two are failing partially because ErrorEvent is not exposed in workers, so I am not sure if Chrome's behavior in them is correct or not.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot