Bugs with limited reproducibility are always difficult for the
engineering team to track down. Is there a particular reason that you
need to keep creating and destroying the player, by the way? What
about just hiding it from the visible area on the page?
Cheers,
-Jeff Posnick, YouTube API Team
groups.google.com/group/youtube-api-gdata | apiblog.youtube.com |
@YouTubeDev
On Mar 15, 5:30 pm, Braden Snell <bhs...@gmail.com> wrote:
> I am having the same problem as Mike - except I am having problems with IE9
> (Safari seems to be fine). I am still having this issue and unfortunately I
> can't seem to reliably reproduce it. After destroying the player and
> creating it again a few times (i.e. removing the iframe and putting on the
> page again) with javascript the problem manifests itself with this error
> from IE console:
>
> SCRIPT5022: DOM Exception: INDEX_SIZE_ERR (1)
> html5player-vflyo4mMZ.js, line 402 character 81
> LOG:  [  1.610s] [yt.debug] yt.tracking.VideoStatsPing: Attempted to
> construct a VideoStatsPing for a video that has no format or videoSize.
>
> Sometimes I also get the error:
>
> SCRIPT5007: Unable to get value of the property 'width': object is null or
> undefined
> html5player-vflyo4mMZ.js, line 369 character 131
>
> Thanks,
>
> Braden
-- 
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