I couldn't resist butting in here... apologies in advance.
Stating that the iframe embed (developed by YouTube) is the default option for embeds generated on YouTube.com is misleading because YouTube is in direct control of both and can quickly (and easily) change them both in the event that YouTube decides to change the experimental iframe embed API again.
We developers, on the other hand, need to scramble to avoid leaving our users stuck waiting for the effects of a change to the experimental iframe embed API to propagate through the development and deployment (and often third-party - e.g. Apple - approval) processes required to replace our existing solutions in the field.
Cheers,
Bert
-- On Thu, Jan 12, 2012 at 5:44 PM, Jeffrey Posnick <jeffy@google.com> wrote:
Hello Zdravko,
Well, as you know, everything having to do with YouTube tends to
change over time.
The <iframe> embed is currently the default option for embeds
generate on YouTube.com. I haven't seen the phrase "experimental" used
to describe the <iframe> embed in some time. The associated API for
controlling the <iframe> embed is still "experimental", and the
implications of that have been discussed in a number of other threads
in this Google Group over the past months.
I really don't have any idea what the source of your second quote is,
or in what way HTML5 <video> playback could be considered "broken".
The current recommended (and only) way of getting HTML5 <video>
playback of YouTube content is to use the <iframe> embed, and I don't
see that changing any time soon.
The <iframe> embed is flexible enough to support hypothetical
playback stack XYZ 5 years down the line, and that's something that
makes it nicer than a rigid <object>/<embed> tag used in the
ActionScript 3 embed. If you're currently developing code against the
<iframe> API and you're concerned that there are plans to abandon it—
well, I obviously can't make 100% guarantees, but I can tell you that
there are no plans that I'm aware of to move everyone to something
brand new.
Cheers,
-Jeff Posnick, YouTube API Team
groups.google.com/group/youtube-api-gdata | apiblog.youtube.com |
@YouTubeDev
On Jan 11, 1:25 pm, zdravko <email.workbe...@gmail.com> wrote:
> Hi Folks,
>
> Elsewhere, somebody wrote ... "YouTube offers an HTML5 player inside
> an iframe with API access ... But as YouTube claims, "This is an
> experimental feature, which means that it might change unexpectedly."
>
> So, just how experimental is the YT iFrame API or is that just your
> regular corporate legalese disclaimer?
>
> The he wrote ... "There is a plan to make Popcorn support YouTube's
> HTML5 player, but the player is broken right now, so that's on hold:"
>
> The whole purpose for my posting is to clear up this YouTube & HTML5
> landscape. Is there a true HTML5 video player and is then the YT
> iFrame API just an interim thing or as I thought, the YT iFrame API is
> the longer term solution which will encapsulate whatever YT is using
> at whatever point in time?
>
> Regards,
> Zdravko
--
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.
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