player before getting published, but I understand the thinking.
Thanks for your responses and more generally, for monitoring this
forum. It's very useful and much appreciated!
Caleb
On Jan 9, 12:08 pm, Jeffrey Posnick <je...@google.com> wrote:
> Hello,
>
> I think that's unavoidable, though. The <iframe> API is reported back
> events that originate in the HTML5 <video> element, and the behavior
> of that element is browser-specific in many cases. I'm really not sure
> that you'd see the same sequence of events across different browsers,
> let alone between Flash and HTML5.
>
> The important thing is that the states reported correspond to reality
> (i.e. you're not getting a PAUSED event thrown in there for no
> reason), and it's up to you to handle those events as best makes sense
> in your code.
>
> Cheers,
> -Jeff Posnick, YouTube API Team
> groups.google.com/group/youtube-api-gdata | apiblog.youtube.com |
> @YouTubeDev
>
> On Jan 7, 1:20 pm, Kleb <calebo...@hotmail.com> wrote:
>
>
>
>
>
>
>
> > That in particular isn't an issue, but it does strike me as a bug that the
> > HTML5 and Flash Youtube players report status differently.
--
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