Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

removeEventListener exception on IE 11

See original GitHub issue

Get this error when navigating away from a route with a dropdown in IE 11 when i have the developer tools open and i run a production build. Can’t be sure it happens when the tools are closed and it doesn’t happen when using a development build.

Dropdown declaration.

{{#power-select-multiple renderInPlace=true options=assets selected=filteredAssets searchField="name" placeholder=(t 'track.trackEventsChooseAssetsToShow') onchange=(action "assetFilterChanged") as |asset|}}
              {{icon-asset asset=asset class="text-bottom" width="20px" height="20px"}}
              {{asset.name}}
              {{#if asset.registration}}<div class="description">({{asset.registration}})</div>{{/if}}
{{/power-select-multiple}}

Stack Trace

"TypeError: Unable to get property 'removeEventListener' of undefined or null reference
   at removeGlobalEvents (https://myapp/assets/vendor-d42d5df2bd86ce26959f3ab73da5b5bd.js:34:23452)
   at _teardown (https://myapp/assets/vendor-d42d5df2bd86ce26959f3ab73da5b5bd.js:34:24415)
   at willDestroyElement (https://myapp/assets/vendor-d42d5df2bd86ce26959f3ab73da5b5bd.js:34:20486)
   at r (https://myapp/assets/vendor-d42d5df2bd86ce26959f3ab73da5b5bd.js:11:30486)
   at trigger (https://myapp/assets/vendor-d42d5df2bd86ce26959f3ab73da5b5bd.js:16:814)
   at r (https://myapp/assets/vendor-d42d5df2bd86ce26959f3ab73da5b5bd.js:11:30486)
   at d.prototype.willDestroyElement (https://myapp/assets/vendor-d42d5df2bd86ce26959f3ab73da5b5bd.js:9:10395)
   at d.prototype.remove (https://myapp/assets/vendor-d42d5df2bd86ce26959f3ab73da5b5bd.js:"

Issue Analytics

State:
Created 7 years ago
Comments:16 (16 by maintainers)

Top GitHub Comments

2reactions

cibernoxcommented, Aug 31, 2016

Ok, I’ll get a VM to debug this at some point today.

1reaction

Kilowhiskycommented, Sep 1, 2016

Yea that’ll fix it. Though I’m not sure the method even needs to be called on willdestroy(). Didn’t check that case though.

Good enough for me!

On Aug 31, 2016, at 7:02 PM, Jim notifications@github.com wrote:

@Kilowhisky can you check if #145 fixes your issue?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.