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.

Safari 11 DOMError "AbortError" - Programmatic play prevented

See original GitHub issue

Probably related to #14 and prevention of autoplay.

Safari 11, both desktop and mobile.

DOMError {name: "AbortError", message: "The operation was aborted."}

once VideoContext run .play() on a cached video element.

Issue Analytics

State:
Created 6 years ago
Reactions:2
Comments:11 (6 by maintainers)

Top GitHub Comments

7reactions

jesperstarkarcommented, Nov 18, 2017

It seems that the attribute muted is needed for Safari 11 (both platforms) to play.

This really feels like a battle we can never win. The <video /> spec is constantly moving.

0reactions

yakcacommented, Mar 10, 2020

Hi @susiwen8 - the best options I see at the moment are to either prompt the user to interact to start video, or to autoplay the video muted as part of its attributes, for example:

var videoNode = videoContext.video("../assets/introductions-rant.mp4", 0, 4, { loop: true, muted: true, autoplay: true });

With the Chrome policy on autoplay that has been active since April 2018, any workaround would likely be temporary and circumventing intended browser behaviour.

Separately, I will look into adding some documentation around autoplay. I think it’s best we move on from this rather old issue and acknowledge the landscape for autoplay video has changed since VideoContext was originally written.