In the process of developing a group watch feature I have observed unexpected API events from the player:
Within a fraction of a second after the initial play event, a seeked event usually fires at player.currentTime around 0.08 seconds.
When the user seeks forward or backwards while the player is already playing, there’s a sequence of events starting with a seemingly extraneous pause followed quickly by a redundant play, then finally the expected seeked event.
When the video ends, there is a pause event followed 1ms later by the ended event.
Are these behaviors all normal or could any of them be considered bugs?
I did not notice any of this when I first starting using the API, but then I did just a couple days ago, which leads to the question of whether the API version changed and whether there could be future changes that break my code since the only URL I’m aware of is this one:
Is it possible to specify a version number to maintain compatibility with my code?
If not, does sdk.latest.js do anything about browser caching?
Tested in Firefox and Chrome for Ubuntu and here is my CodePen with output to the browser console: