[next] addEventListener does not go through zones

[blois]

The streams do, but addEventListener does not.

[blois]

The difficulty here is that in Dartium we have to have multiple implementations of addEventListener to work around 17408.

In order to wrap in zones we would make addEventListener private and expose a new public one which does the wrapping, but this is susceptible to subtle breakage (and invalid C++ casts) if the C++ classes change.

[blois]

Marked this as being blocked by #17408.

[kevmoo]

Removed Area-HTML label.
Added Area-Library, Library-Html labels.

[blois]

Issue #19508 has been merged into this issue.

[jmesserly]

idea: rename native method to addEventListenerWithoutZone, then introduce a written-in-dart addEventListener?

Pete any ideas how to support removeEventListener? I guess we'll need to associate our wrapped function with the original function closure using an Expando.

[sethladd]

What's the priority of this issue?

[blois]

Perhaps deprecate removeEventListener and just have removeEventListenerWithoutZone?

[blois]

Issue #19905 has been merged into this issue.

[alan-knight]

Might be addressed in the next rev.

---

Removed the owner.
Changed the title to: "[next] addEventListener does not go through zones".

[jacob314]

Angular2 has to work around this issue resulting in less efficient codegen.
https://github.com/angular/angular/blob/60885da0445bc62f065c6c6d8e805a930295783e/modules/angular2/src/dom/browser_adapter.dart

[matanlurey]

I believe we are not planning on forcing all JS interop through zones at this time.