You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This in turn ends up getting logged as an error since the exception is raised all the way to the global exception logger, but it isn't really since the user has intentionally removed the element. I think there should be a check to see if the component has been destroyed or not.
The text was updated successfully, but these errors were encountered:
Thank you very much for reporting. Unfortunately I'm having quite a few issues with the async initialization. Any ideas where to put that check?
I tried toggling an ember-youtube component in a template but couldn't get the error to throw. Are you using the lazyload option on the component in the modal?
Because of the async nature of the initialization it's possible for someone to have removed the component that's being initialized raising:
This is very evident on mobile browsers for us where we have the player in a modal that can be closed and removed. The cause is here: https://github.com/oskarrough/ember-youtube/blob/master/addon/components/ember-youtube.js#L133
This in turn ends up getting logged as an error since the exception is raised all the way to the global exception logger, but it isn't really since the user has intentionally removed the element. I think there should be a check to see if the component has been destroyed or not.
The text was updated successfully, but these errors were encountered: