[Prev] Thread [Next]  |  [Prev] Date [Next]

[YouTube-API] Re: Accessing YouTube API through a deployed Google Chrome Extension - Adobe Flash Player has stopped a potentially unsafe operation. Jeffrey Posnick Tue Feb 21 15:00:58 2012

Hello Sean,

 No, I am not aware of any way to work around the built-in security
restrictions in the Flash runtime. You could ask your users to
manually change their Flash security settings, but I doubt too many of
them would want to do that (and it's not really a recommend practice).
This has nothing to do with whether swfobject is used to construct
your embed tags.

 HTML5 <video> can also be used for YouTube playback when you use the
<iframe> embed method. I don't think you'd have the same issues with
that (though I haven't tried using the <iframe> embed in a Chrome
extension). Give it a try:


-Jeff Posnick, YouTube API Team
groups.google.com/group/youtube-api-gdata | apiblog.youtube.com |

On Feb 20, 5:27 pm, Sean Anderson <[EMAIL PROTECTED]> wrote:
> Hi all,
> I am aware of the security measures in place for SWF. I had taken steps to
> address this issue during development. Namely, I went to the Adobe Flash
> Security Settings Manager and added the folder housing my Google Chrome
> Extension to white list. This worked great for development, but in testing
> it was shown that users experience the same issue with a packaged app.
> I am wondering a few things:
>    - Do many people experience this issue, or is it an issue I am creating?
>    - What are my options for working around this issue?
> One of my main concerns is that I am not using swfobject.js. I did a bit of
> reading, but could not find any material stating that using swfobject would
> address security concerns. I was unable to get the "onYouTubePlayerReady"
> event to fire when using this code:http://pastebin.com/J0qmJXg3. Yet, with
> this more bare-bones code,http://pastebin.com/mA18PX03, I was able to
> load the player directly into a div. It was not my intent to introduce any
> security issues, if I did so, merely to get the player running.
> Does anyone have any advice as to how to best alleviate this issue? Thanks.

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 [EMAIL PROTECTED]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at