In JW 8.2, the player will react to the combination of the browser’s restrictions and the publisher’s setup configuration by autoplaying with or without sound, or falling back to a click-to-play player. With the impending release of Chrome 66 in April, we invested a lot of time in simplifying the expected behavior so that we can provide viewers the right feedback to know if and when they need to interact with the player to start playing, while also mitigating the impact on our publishers’ ability to monetize their content. In JW 8.1, we implemented functionality to pause playback instantly when the browser blocks an autoplaying video. Safari 11 was first to take a strong stance by giving viewers the power to prevent videos from starting automatically. Better Handling of Browser Autoplay PoliciesĪs browser autoplay policies evolve to create a better video experience for viewers, it has become increasingly challenging for publishers, especially those that monetize their content, to ensure consistency.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |