Nothing has changed since then. Please don't overlay your own event
handlers on top of the YouTube Player.
If the default behavior of the AS3 chromeless player doesn't meet
your requirements, another option is using the AS3 embedded player
with the controls=0 parameter set. That version of the embedded player
is similar to the chromeless player in appearance (though there are
some subtle differences), but more importantly to your use case, it
supports click to play/pause natively.
Cheers,
-Jeff Posnick, YouTube API Team
groups.google.com/group/youtube-api-gdata | apiblog.youtube.com |
@YouTubeDev
On Mar 6, 11:20 pm, Joshua Alltop <plystiregrya...@hotmail.com> wrote:
> Hello,
>
> I've been working to implement YouTube functionality on my site via AS3. I
> have thus far enjoyed using the API. It's fast, it's robust in many ways,
> and it tends to work with very little need to coerce it. That is, until I
> come to install player controls for the chromeless player.
>
> A basic function, that many are familiar with, appreciate, and find to be
> intuitive; is the "click to pause" function. I thought this would be
> relatively simple to get going. Add a listener for CLICK, pause/play the
> video. Not so much. While this did work, it also encompasses any ads
> displayed in the player. Well, like most any dev would, I meddled around
> with the player until I was able to achieve the desired outcome. But, I
> needed to be sure I wasn't in violation of anything, so I came to check the
> knowledge base and forums on the matter.
>
> I came across a few threads posted a year or so ago on roughly the same
> topic. I came across a post from Jeff Posnick:
> "Please don't attempt to gain access to the ads container or
> manipulate ads that are shown in any way. I understand the desire to
> achieve click to pause behavior for your player, and the fact that
> you've asked in the past for a way to interact with/be notified about
> ad events in a programmatic manner, but that doesn't change the fact
> that what you're attempting to do is not supported.
> Cheers,
> -Jeff Posnick, YouTube API Team"
>
> If the simple act of gaining access to the ads container isn't supported,
> is it then "wrong" for us to force access ourselves? It seems that gaining
> access to the ad container in a brute force manner might be against the
> TOS, and this bothers me. For what reason are we disallowed to implement *proper
> *click to pause behavior? The only reason I am accessing the ad container
> is not to manipulate it in any way, but to simply prevent an event listener
> from being added to it.
>
> Is this not allowed? Is this against the TOS?
>
> I do not want to violate any terms, but I am very confused on this topic.
> It's hard for someone to be creative with the API (as the devs have
> expressed they wished to see) when something as simple as this is not
> supported.
>
> I don't mind YouTube ads showing up. I know they need to show ads, just as
> we do. I would just like to place my event listeners onto the player
> explicitly, not onto the ads that will be shown.
>
> ~Joshua Alltop
--
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