The element to embed the player in is effectively replaced for a few
days already but on my side (not sure on Jeffrey's side), i have an </
div> element also appearing after the iframe (using "new YT.Player()"
to insert the player).
This is quite an issue for me right now as i am using CSS transitions
for the player to resize smoothly and it stopped working due to this
/div issue. I also saw an empty <head></head> being added after the
existing <head></head>. Not sure this is coming from you as i am using
other APIs in the middle but that was not there yesterday.
The player still behaves normally besides that but everything was
working perfectly yesterday.
Thanks.
On Jan 19, 9:28 am, Bruce <bruce.schwa...@gmail.com> wrote:
> Thanks for the heads-up! We were seeing some odd problems this afternoon
> and your post provided the fix.
>
> However, its seems that, at least on an iPad, this new player doesn't start
> to play until the entire video is buffered. Is that the expected new
> behavior? Can it be overridden to get the prior behavior in which the
> player started playing much sooner?
--
You received this message because you are subscribed to the Google Groups "YouTube APIs Developer Forum" group.
To post to this group, send email to youtube-api-gdata@googlegroups.com.
To unsubscribe from this group, send email to youtube-api-gdata+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/youtube-api-gdata?hl=en.
No comments:
Post a Comment