Show a UI element to let the user manually start playback. In browsers that don’t yet support this functionality, This lets you write intuitive code like the following: var playPromise = document. If playback succeeds, the Promise is fulfilled, and if playback fails, the Promise is rejected along with an error message explaining the failure. An improvement to the underlying play() method to address this uncertainty is long overdue, and this has now made it to the web platform, with an initial implementation in Chrome 50.Ī play() call on an a or element now returns a Promise. Various workarounds exist, but are less than ideal.
It’s historically been difficult to determine whether user interaction is required to start playback, and to detect the failures that happen when (automatic) playback is attempted and fails. This helps ensure that mobile users, many of whom pay for bandwidth or who might be in a public environment, don’t accidentally start downloading and playing media without explicitly interacting with the page. Most mobile browsers, however, require an explicit user gesture before JavaScript-initiated playback can occur. Today, most desktop browsers will always allow web pages to begin or playback via JavaScript without user interaction. Automatically playing audio and video on the web is a powerful capability, and one that’s subject to different restrictions on different platforms.
0 kommentar(er)
