-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Dailymotion embed doesn't work in Chrome using amp-iframe #1585
Comments
Let's use this issue to track the FF/Chrome inconsistency. amp-iframe should work in this context. Opened #1588 for tracking a new DailyMotion component. |
I'm all for a dedicated dailymotion embed. |
Thanks for your quick answer ! @cramforce : You're almost right, there is a problem with https & dailymotion. It works in http but not in https : |
So currently there is no solution for Dailymotion, as HTTPS is unreliable as a I also could not get an iframe to work over HTTPS with dailymotion nor amp-iframe. |
Looks to me like it's an issue with Flash inside of the iframe. Because the iframe is sandboxed, we cannot execute Flash within the iframe. On my mobile device it seems to be working because it's forcing an HTML5 fallback player instead of the flash player. Anyone else see this happening? |
@johnnyshankman : That can be right, it's the same for me. It works on my mobile with Dailymotion & https (AMP & no-AMP). Android 6.0.1 / Chrome 47 |
Yes, flash will not work inside A specific amp embed for dailymotion or AOL would not have this limitation. |
Could somebody contact dailymotion and/or AOL whether they e.g. support a URL param to opt out of the flash player? |
I tried to reach the technical support of Dailymotion. I haven't received any responses yet. |
Hi guys, we are in contact with Google and working on a specific |
See #2017. |
Currently it's not possible to show Dailymotion video in Chrome but it works in Firefox.
Example : http://codepen.io/okeul/pen/YwZmgo
Chrome 47.0.2526
Firefox 41.0.2 & 43.0.4
OSX 10.8.5 & 10.10.4
The text was updated successfully, but these errors were encountered: