inherit
58740
0
Aug 20, 2024 7:29:21 GMT -8
®i©hie
I'm not very active here anymore thanks to my full-time job. - 12/27/23
14,036
September 2005
soe
|
Post by ®i©hie on Aug 21, 2013 16:50:24 GMT -8
|
|
inherit
256325
0
Jun 16, 2019 3:37:21 GMT -8
jeroenvu
9
September 2018
jeroenvu
|
Post by jeroenvu on Jun 9, 2019 16:31:30 GMT -8
doesn't work anymore
|
|
inherit
58740
0
Aug 20, 2024 7:29:21 GMT -8
®i©hie
I'm not very active here anymore thanks to my full-time job. - 12/27/23
14,036
September 2005
soe
|
Post by ®i©hie on Jun 10, 2019 11:30:25 GMT -8
I'll try to get to this by wed. Or thur.
|
|
inherit
Official Code Helper
65613
0
1
Oct 22, 2024 1:56:19 GMT -8
Chris
"'Oops' is the sound we make when we improve"
9,018
December 2005
horace
RedBassett's Mini-Profile
|
Post by Chris on Jun 10, 2019 13:28:08 GMT -8
Basically type chrome://media-engagement in your chrome web browser (desktop) to see if your forum is recognized as an allowed site for autoplaying videos (due to prior playback history) Google starts blocking annoying autoplay videos in ChromeBy Tom Warren
Google started rolling out a new version of Chrome last month that further addresses autoplay videos. The latest update, version 66, includes autoplay video changes that stop Chrome from automatically playing videos if the sound is on by default. Google is gradually rolling these changes out in a personalized way, so that Chrome learns user preferences of which sites should and should not be blocked. This should prevent audio randomly blasting out of your speakers when visiting a new site... READ MOREAutoplay Policy ChangesNote: The Autoplay Policy launched in M66 Stable for audio and video elements and is effectively blocking roughly half of unwanted media autoplays in Chrome. For the Web Audio API, the autoplay policy will launch in M71. This affects web games, some WebRTC applications, and other web pages using audio features. Developers will need to update their code to take advantage of the policy. More details can be found in the Web Audio API section below.
Chrome's autoplay policies will change in April of 2018 and I'm here to tell you why and how this is going to affect video playback with sound. Spoiler alert: users are going to love it! Figure 1. Internet memes tagged "autoplay" found on Imgflip and ImgurNew behaviorsAs you may have noticed, web browsers are moving towards stricter autoplay policies in order to improve the user experience, minimize incentives to install ad blockers, and reduce data consumption on expensive and/or constrained networks. These changes are intended to give greater control of playback to users and to benefit publishers with legitimate use cases. Chrome's autoplay policies are simple: - Muted autoplay is always allowed.
- Autoplay with sound is allowed if:
- User has interacted with the domain (click, tap, etc.).
- On desktop, the user's Media Engagement Index threshold has been crossed, meaning the user has previously play video with sound.
- On mobile, the user has [added the site to their home screen].
- Top frames can delegate autoplay permission to their iframes to allow autoplay with sound.
READ MORE
|
|