I am currently using the vimeo embed code for iframe and all has been working fine until recently. All of the sudden the fullscreen button on the player no longer works. Same thing is occurring on Windows with FireFox version 41.0.2, but conversely works on Mac OSX. Chrome fails to go fullscreen on both Windows and OSX.
Try adding the html5 fullscreen attributes to your iframe:
<iframe src="//player.vimeo.com/video/VIDEO_ID" width="WIDTH" height="HEIGHT" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowfullscreen="true"></iframe>
Related
I want my embed Youtube default resolution to be 1080p. Here is the iframe code:
<iframe width="1050" height="591" src="//www.youtube.com/embed/GjsBjsWXgsA?rel=0&vq=hd1080" frameborder="0" allowfullscreen></iframe>
The HD1080 works fine on Mozilla Firefox but not on Chrome.
Can anybody suggest other option?
The following parameters are supported in the AS2 player but have been deprecated for the newer AS3 and HTML5 players: border, color1, color2, egm, hd, and showsearch.
I'm unsure as to why I'm unable to see the full screen button when viewing an embedded youtube video through an iframe in chrome. This only occurs in chrome (tested with Firefox, IE, Safari, Chrome).
You can see what I mean with the below fiddle as it renders through an iframe.
<iframe width="560" height="315" src="//www.youtube.com/embed/BKorP55Aqvg" frameborder="0" allowfullscreen></iframe>
http://jsfiddle.net/9sgng/
Is this a bug/google preference or is there a way around it?
I worked out that I only had allowfullscreen on the youtube iframe, but you also need it on the iframe that is holding the youtube iframe.
Im trying to play vimeo video in samsung smart TV app from specified time using iframe.Im just appending the video url with ?#t=0m50s.This works fine in browser like chrome and safari which support webkit, but in smart TV it starts from beginning.
<iframe src="http://player.vimeo.com/video/86874445?autoplay=1?#t=0m50s" width="900" height="460" frameborder="0" ></iframe>
It is given that samsung smart TV has also started using webkit browser engine and hence supports HTML5.If that is the case it should work.where I am going wrong..
I am using following code to embed a Youtube video with HTML5 player. It is working fine in Chrome and IE but failing in Firefox.
<iframe width="560" height="315" src="http://www.youtube.com/embed/mwG7z_aowKw?html5=1" ></iframe>
Version of Firefox is 26.0
Is there any error in the iframe code?
Is there any work-around possible?
update - Working in safe mode with addons disabled.
But Problem still persist when disabled all addons in normal mode.
How to debug this problem?
Works for me - FF 27. There is no error in iframe I would say there is something wrong with yours FF.
I ran into a problem with a Youtube video not running on my Wordpress site, www.marcoislandscene.tv. It works fine on Chrome and IE.
YouTube generated the following code:
<iframe width="640" height="360" src="https://www.youtube-nocookie.com/embed/afOCUx-xnsw?rel=0" frameborder="0" allowfullscreen></iframe>
This code would display the preview but the video wouldn't run. I removed "-nocookie" from the code and it runs fine on FF, IE and Chrome.
I am using a web based html5 mobile app builder (tiggzi). I am using the youtube iframe api. When I install my app on my android devices the embedded video displays the placeholder image just fine. On my nexus 7 with android 4.2.2 if I hit play I hear the sound but do not see the video (black). If I hit the full screen I see the video play ok. On my android 4.0.4 bionic phone I see the video placeholder image but play just shows black and full screen does not respond (ultimately app crashes). On my desktop machine testing my app in chrome video plays fine.
my html:
<iframe class="youtube-player" type="text/html" width="640" height="385" src="http://www.youtube.com/embed/u1zgFlCw8Aw" frameborder="0">
</iframe>
Question is, how do I get video to play correctly as embedded in and html5 mobile app for both android 2+ and iphone/ipad? I thought the iframe api would work but it still falls back to flash which appears to be the problem in my case.