10-11-2019 03:07 PM
10-11-2019 03:07 PM
There are some upcoming changes being rolled out to chrome in Jan 2020 involving default behavior of the samesite property in cookies, effectively making 3rd party cookies disabled by default.
This can be tested now in chrome 76/77 by enabling the feature flags:
I've tested this with the microsoft streaming content iframes and found that this does indeed break the playability of thes iframes. When i click the iframe and load the content in its own browser tab it works. Is there anyone working on a fix for this yet?
For those that aren't aware of this change here is a brief summary:
12-11-2019 01:57 PM
@iabowers I think this might be similar to an existing problem where you cannot play Microsoft Stream embedded videos on iOS Safari. That also seems to involve 3rd party cookies and cross site tracking settings. Hopefully the Stream team can solve this quickly without asking iOS users to change their cookie settings. Getting non-technical users to do that is difficult!
We embed Stream videos and when you view the page on iOS the videos show an error "Your browser does not support playback inline. Please open a new window to play this video." When you do that it has the same error. When you click learn more the message talks about changing your 3rd party cookie settings.
12-16-2019 07:52 PM
@Victor_98029 Hi, I have the same problem "Your browser does not support playback inline. Please open a new window to play this video." with embedded video from ms stream. It happened on Safari Ios version 13.1.2, changing the cookie settings won't help to address the issue, however it can address the cookie issue with Safari. The only thing i can do to resolved the problem is to update to the newer ios version 13.2 then the error will be replace by the login screen.
Ios version 13 playback error:
01-02-2020 11:52 AM
Hi there, the next Stream update will include the right flags to ensure that the February Chrome update does not break playback, thanks for reaching out. We appreciate the vigilance :)
01-02-2020 11:54 AM
@notstormns That is correct, that specific version of safari had a giant regression that Apple patched soon after. You need to update your version if you wish for the browser to respect your cross-site tracking settings.
01-15-2020 01:53 AM
01-19-2020 03:42 AM
01-29-2020 05:24 PM - edited 01-29-2020 05:26 PM