still stuck in the gutter ;)
I do get that part about how the iframe api presents both formats in a
common way as far as javascript coding is concerned. However, what I
am most curious about is whether the youtube api player appears to
html5 to be a native video - the same way that other "html5 video
formats" would appear to it ? Because if it did then instead of the
yt api , we would do whatever others would do when hosting non youtube
videos. ?!?
Thanks again.
On Dec 28, 10:12 pm, Tim Wintle <timwin...@gmail.com> wrote:
> On Wed, 2011-12-28 at 14:51 -0800, zdravko wrote:
> > So, when one has properly opted in and where html4 videos are being
> > streamed, there are some cases where specific videos could be streamed
> > in flash? So, in that "mixed" environment where some videos are
> > <video> and some are _flash_ do flash videos "mascarade" as html5
> > video. In other words, did YT build a wrapper that somehow makes the
> > flash video appear to be html5 video - at least from the javascript
> > perspective?
>
> Yes.
>
> The iframe API *should*[0] behave in the same way regardless of if the
> underlying playback is via <video> or flash.
>
> The Developer using the api shouldn't have access to the actual <video>
> anyway, so all communication is via the javascript YT.Player instance
> which abstracts all that away.
>
> Tim
>
> [0] There are some complications - like needing to set wmode in some
> situations where flash may be displayed.
--
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