Raised This Month: $181 Target: $400
 45% 

Chrome Policy Update - MOTD


Post New Thread Reply   
 
Thread Tools Display Modes
Author Message
morpig
New Member
Join Date: Apr 2017
Old 05-01-2018 , 07:03   Chrome Policy Update - MOTD
Reply With Quote #1

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
morpig is offline
nosoop
Senior Member
Join Date: Aug 2014
Old 05-01-2018 , 09:47   Re: Chrome Policy Update - MOTD
Reply With Quote #2

Based off of the current CEF builds, it looks like they will be affected by default.
__________________
I do TF2, TF2 servers, and TF2 plugins.
AlliedModders Releases / Github / TF2 Server / Donate (BTC / BCH)
nosoop is offline
Mitchell
~lick~
Join Date: Mar 2010
Old 05-01-2018 , 09:52   Re: Chrome Policy Update - MOTD
Reply With Quote #3

Isn't those changes to Chrome specifically?
__________________
Mitchell is offline
morpig
New Member
Join Date: Apr 2017
Old 05-01-2018 , 11:17   Re: Chrome Policy Update - MOTD
Reply With Quote #4

Quote:
Originally Posted by Mitchell View Post
Isn't those changes to Chrome specifically?
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.


Last edited by morpig; 05-01-2018 at 11:17.
morpig is offline
nosoop
Senior Member
Join Date: Aug 2014
Old 05-01-2018 , 12:05   Re: Chrome Policy Update - MOTD
Reply With Quote #5

Quote:
Originally Posted by Mitchell View Post
Isn't those changes to Chrome specifically?
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.
__________________
I do TF2, TF2 servers, and TF2 plugins.
AlliedModders Releases / Github / TF2 Server / Donate (BTC / BCH)

Last edited by nosoop; 05-03-2018 at 14:08.
nosoop is offline
nosoop
Senior Member
Join Date: Aug 2014
Old 05-17-2018 , 10:06   Re: Chrome Policy Update - MOTD
Reply With Quote #6

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.
__________________
I do TF2, TF2 servers, and TF2 plugins.
AlliedModders Releases / Github / TF2 Server / Donate (BTC / BCH)
nosoop is offline
VPPGamingNetwork
Veteran Member
Join Date: Sep 2012
Location: Japan
Old 05-17-2018 , 11:14   Re: Chrome Policy Update - MOTD
Reply With Quote #7

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/
__________________

We provide MOTD Ads
Net 1 payments
Visit us
VPPGamingNetwork is offline
Trumbauer
New Member
Join Date: Mar 2018
Location: 1827 Big Indian Kenner,
Old 05-21-2018 , 14:03   Re: Chrome Policy Update - MOTD
Reply With Quote #8

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.
Trumbauer is offline
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -4. The time now is 15:55.


Powered by vBulletin®
Copyright ©2000 - 2018, vBulletin Solutions, Inc.
Theme made by Freecode