Fwiw, you can’t even trust the browsers to handle HTML5 media spec behavior the same way. I just dealt with cross-browser issues in how setting currentTime on

Fwiw, you can’t even trust the browsers to handle HTML5 media spec behavior the same way. I just dealt with cross-browser issues in how setting currentTime on <audio> is handled because I needed a player to resume from a preset time. On WebKit browsers, including desktop safari and all iOS browsers, you must wait for the ‘dataloadded’ or ‘canplay’ events to fire before trying to set currentTime. On desktop Firefox / Chrome, you must set currentTime immediately prior to .play() or it won’t pick it up.