[YouTube-API] Re: Change to <iframe> player insertion

Hi, I just read this and realised it answered this question I just
posted about my site cueyoutube.com sorry about that. Fixed now :)

I guess I had better stay subscribed to this group then hey?

Cheers,
Iain

On Jan 19, 9:48 am, Jeffrey Posnick <je...@google.com> wrote:
> I wanted to give folks a quick heads-up regarding a change to the way
> <iframe> player insertion (i.e. loading in the <iframe> player via the
> YT.Player API) behaves.
>
> Previously, when inserting a new <iframe> player into a page, the
> <iframe> element was added as a child of a parent element, whose id
> was passed in as the first parameter to the YT.Player constructor.
>
> Starting tonight, when a new <iframe> is inserted onto a page via the
> YT.Player constructor, the <iframe> element will replace in the DOM
> whichever element whose id was passed in as the first parameter. It
> will no longer be that element's child.
>
> If you have CSS selectors or JavaScript code that depends on the new
> <iframe> being a child of that element, you will want to check its
> functionality after tonight's server-side push and adjust as needed.
>
> If you explicitly include an <iframe> tag in your page's HTML, rather
> than inserting it dynamically using the API, then nothing should be
> changing for you.
>
> Cheers,
> -Jeff Posnick, YouTube API Team
> groups.google.com/group/youtube-api-gdata | apiblog.youtube.com |
> @YouTubeDev

--
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.