From 58e1222d6d07cdb8bfec609ce46ac246fe5771d8 Mon Sep 17 00:00:00 2001 From: ldayananda Date: Mon, 26 Mar 2018 10:29:48 -0400 Subject: [PATCH 1/3] Update README.md --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index dc81a626..4d282a2e 100644 --- a/README.md +++ b/README.md @@ -120,6 +120,10 @@ The following events are slated for removal from contrib-ads and will have no sp * `adscanceled` (EVENT) -- In the future, this event will no longer result in special behavior in contrib-ads. It was intended to cancel all ads, but it was never fully implemented. Instead, trigger `nopreroll` and `nopostroll`. * `adserror` (EVENT) -- In the future, this event will no longer result in special behavior in contrib-ads. Today, this event skips prerolls when seen before a preroll ad break. It skips postrolls if seen after contentended and before a postroll ad break. It ends linear ad mode if seen during an ad break. These behaviors should be replaced using `skipLinearAdMode` and `endLinearAdMode` in the ad integration. +## Autoplay + +Using the `autoplay` attribute on the video element is not supported. Due to Autoplay Restrictions imposed by browsers, using the `autoplay` attribute on the player will often not behave as expected. The current recommendation of browsers is to use the `player.play()` method to autoplay when autoplay is not restricted and have access to the play promise if it is available on that browser. + ### Public Methods These are methods on `player.ads` that can be called at runtime to inspect the ad plugin's state. You do not need to implement them yourself. From 756250ad719f1d0e98937ceaf1e150ce3f8c1282 Mon Sep 17 00:00:00 2001 From: ldayananda Date: Mon, 26 Mar 2018 10:47:53 -0400 Subject: [PATCH 2/3] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 4d282a2e..5f43e424 100644 --- a/README.md +++ b/README.md @@ -122,7 +122,7 @@ The following events are slated for removal from contrib-ads and will have no sp ## Autoplay -Using the `autoplay` attribute on the video element is not supported. Due to Autoplay Restrictions imposed by browsers, using the `autoplay` attribute on the player will often not behave as expected. The current recommendation of browsers is to use the `player.play()` method to autoplay when autoplay is not restricted and have access to the play promise if it is available on that browser. +Using the `autoplay` attribute on the video element is not supported. Due to Autoplay Restrictions [introduced](https://developers.google.com/web/updates/2017/09/autoplay-policy-changes) by [browsers](https://webkit.org/blog/7734/auto-play-policy-changes-for-macos/), using the `autoplay` attribute on the player will often not behave as expected. The recommended [best practice](https://developers.google.com/web/updates/2017/09/autoplay-policy-changes#best-practices) is to use the `player.play()` method to autoplay when autoplay without user interaction is not restricted and have access to the [play promise](https://developer.mozilla.org/en-US/docs/Web/API/HTMLMediaElement/play) if it is available on that browser. ### Public Methods From 20d7b910514ad423e137c8846d0a6ce265f794cc Mon Sep 17 00:00:00 2001 From: ldayananda Date: Mon, 26 Mar 2018 11:57:51 -0400 Subject: [PATCH 3/3] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 5f43e424..aa1f7b2e 100644 --- a/README.md +++ b/README.md @@ -122,7 +122,7 @@ The following events are slated for removal from contrib-ads and will have no sp ## Autoplay -Using the `autoplay` attribute on the video element is not supported. Due to Autoplay Restrictions [introduced](https://developers.google.com/web/updates/2017/09/autoplay-policy-changes) by [browsers](https://webkit.org/blog/7734/auto-play-policy-changes-for-macos/), using the `autoplay` attribute on the player will often not behave as expected. The recommended [best practice](https://developers.google.com/web/updates/2017/09/autoplay-policy-changes#best-practices) is to use the `player.play()` method to autoplay when autoplay without user interaction is not restricted and have access to the [play promise](https://developer.mozilla.org/en-US/docs/Web/API/HTMLMediaElement/play) if it is available on that browser. +Using the `autoplay` attribute on the video element is not supported. Due to Autoplay Restrictions introduced by browsers, such as [Safari](https://webkit.org/blog/7734/auto-play-policy-changes-for-macos/) and [Chrome](https://developers.google.com/web/updates/2017/09/autoplay-policy-changes), using the `autoplay` attribute on the player will often not behave as expected. The recommended [best practice](https://developers.google.com/web/updates/2017/09/autoplay-policy-changes#best-practices) is to use the `player.play()` method to autoplay when autoplay without user interaction is not restricted and have access to the [play promise](https://developer.mozilla.org/en-US/docs/Web/API/HTMLMediaElement/play) if it is available on that browser. ### Public Methods