Chrome Policy Update - MOTD
 

Hi there,

As you may or may not know, the upcoming Chrome policy update, will have autoplay (audio & video) disabled if the window is not interacted (user gesture) by the user.

AFAIK, Steam uses Chromium for their overlay and in-game browser, will this affect hidden & shown MOTDs (ads, music, etc)?

Reference: https://goo.gl/7K7WLu

Thanks

Re: Chrome Policy Update - MOTD
 

Based off of the current CEF builds, it looks like they will be affected by default.

Re: Chrome Policy Update - MOTD
 

Isn't those changes to Chrome specifically?

Re: Chrome Policy Update - MOTD
 

I'm not sure. I've had 1-2 players using the new version and receiving error to my dashboard related to the new policy update.

https://i.gyazo.com/cdd100ff5f426457...9adf543f6b.png

Re: Chrome Policy Update - MOTD
 

The Chromium Embedded Framework (CEF) sample application build download from the site I posted above displays the same NotAllowedError on a page with autoplaying audio. The Chromium site also mentions the enforcement of policies in the latest stable release, so it's not just mainline Chrome.

Steam and its embedded browser uses the CEF; you can see those files in Windows under Steam\bin\cef\. Unless Valve rolls their own configuration, this policy is likely going to affect the Steam in-game browser once the client gets an update based off of Chromium 66+.

Which is a shame if players can't add exceptions; I'm using hidden MOTDs for optional streaming background audio. Would have to go back to sending music downloads or some other suboptimal approach.

Re: Chrome Policy Update - MOTD
 

As of today, the latest Steam client release has Chromium 65, so we should be okay for a few months. I've verified that autoplay works as expected.

Additionally, Chrome 66 reverted their autoplay policy for the Web Audio API. Audio and video elements are still blocked, so you may need to port your code to that API for the time being.

For reference, here's an example for setting up web audio.

Re: Chrome Policy Update - MOTD
 

Actually Chrome 66 has been reverted for now until Chrome 70 comes out. So as for now valve client's update is fine. Chrome 70 plan to be release around October so in valve time give or take that might be around march of 2019. After that yea,

https://www.engadget.com/2018/05/16/...play-rollback/

Re: Chrome Policy Update - MOTD
 

Applies for Chrome variant 64 or later on Windows. Applies for Chrome form 66 or later on Mac. As a Chrome Enterprise director, you can constrain clients to sign in to their Chrome profile before they utilize Chrome Browser on an oversaw PC.