-
-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Youtube do not autoplay anymore on Google Chrome #149
Comments
Just checked if the error was coming from Playemjs' Youtube player (adrienjoly/playemjs#18): it's not. => The problem must be coming from Openwhyd's patched version of the Youtube player ( => Running Openwhyd's automated tests to see if they pass. |
All automated tests pass. My hypothesis is that Webdriver is using an old version of Google Chrome on which the bug was not happening. => Next check: manually test playback of youtube tracks from my local openwhyd instance, on the latest version of Chrome. |
=> Let's investigate what |
Playback also works from localhost, when forcing => let's now pretend that we're running from production => have EDIT: dumb idea, because doing that uses the CDN-cached version of |
Found in javascript logs when trying to play the youtube track from https://openwhyd.org/yt/aZT8VlTV1YY:
|
While debugging the JSON parse error from playem-youtube-iframe-patch.js, I found that I also found that this parse error and the "violation" warning are happening on the local instance as well, and does not prevent the video from starting. |
Hypothesis: the bug happens only thru HTTPS (SSL). Test: Try to play the youtube track from http://openwhyd.org/yt/aZT8VlTV1YY a new chrome incognito window, after disabling the "Protect you and your device from dangerous sites" setting. (to prevent the automatic HTTP-->HTTPS redirection) Result: the track also does not play when using HTTP. |
Hypothesis:
1. attach openwhyd.org to localhostcf https://www.imore.com/how-edit-your-macs-hosts-file-and-why-you-would-want
... and then open a new incognito chrome window => 2. port forwarding 8080->80cf https://serverfault.com/a/787565/284330 2.1. check current rules
2.2. try the restore command
2.3. add the port forwarding
2.4. check current rules again
=> it's working: I can access my localhost:8080 server from openwhyd.org (port 80) 🎉 3. try playing the youtube track from the fake openwhyd.org
|
Now that I'm able to test the real youtube playback behavior from my local openwhyd instance, let's try to apply playemjs' PR: https://github.com/adrienjoly/playemjs/pull/16/files, to see if it fixes the issue. => Plan:
=> still does not play |
Found the fix (at least working when testing locally): https://stackoverflow.com/a/48747474/592254 Google Chrome now requires to use a Let's commit the fix and test it in production! |
Fixed! 🍾 => release and deploy v1.1.4 (https://github.com/openwhyd/openwhyd/releases/tag/v1.1.4) |
Situation, when clicking on a Youtube track, on Google Chrome:
=> The Youtube wrapper of Playemjs (the track player used by Openwhyd) may need a quick fix, e.g. by calling the
playVideo()
function instead of relying on the embed'sautoplay
setting.Read more on how to do that: https://github.com/openwhyd/openwhyd/blob/96370c5c0dcfd198cc84909032ac0f13fd8ff3ed/docs/playemjs-fix-procedure.md
The text was updated successfully, but these errors were encountered: