Not clear why do we expose player to the scope about angular-youtube-embed HOT 1 CLOSED

the directive has its own scope, so that we don't break any behavior on the parent scope.

when we create the player, we add it to the scope. internally, this is convenient since we can make calls on scope.player without having to pass a player into every function that needs it.

the real benefit is that, from the parent scope, you're able to pass in a variable to hold onto the player, allowing to parent scope to directly manipulate the video. here's an example:

when adding the youtube-video to your template, define a player attribute on it.

<youtube-video video-id="someVideo" player="myPlayer"></youtube-video>

from within your controller, $scope.myPlayer is the player that is handling that specific video. doing something like

$scope.myPlayer.playVideo();

will make that video start playing.

be aware though that when you controller is first created, $scope.myPlayer won't be defined, since it needs to wait until the YouTube library has loaded and created the player.

if you check out the advanced demo, the video that loops is handled like this. let me know if anything doesn't make sense.

from angular-youtube-embed.