This is a workaround for the issue #453 where IE (11) will not seek to 0 after the first play/pause toggling while setting up the YouTube wrapper.
Without this patch the wrapper is stuck, paused and not seeking, waiting for the current time (as reported by the YT API) to become 0 before firing the ready event. This seems to be related to browser caching as it rarely, if at all, happens when files are first fetched by the browser but it's much more common once the page is reloaded with the caches full.
I also noticed that if calling Popcorn's currentTime() after the video has been setup (and not yet played) method it would not report 0 unless the player.seek( 0 ) call was moved to after the player.pauseVideo() call.
This is a workaround for the issue #453 where IE (11) will not seek to 0 after the first play/pause toggling while setting up the YouTube wrapper.
Without this patch the wrapper is stuck, paused and not seeking, waiting for the current time (as reported by the YT API) to become 0 before firing the ready event. This seems to be related to browser caching as it rarely, if at all, happens when files are first fetched by the browser but it's much more common once the page is reloaded with the caches full.
I also noticed that if calling Popcorn's
currentTime()after the video has been setup (and not yet played) method it would not report 0 unless theplayer.seek( 0 )call was moved to after theplayer.pauseVideo()call.