Controller Doesn't Work After Url Change

In short: I have a controller that triggers some jQuery in my AngularJS web page to fade out a play button and a corresponding image. But, when the URL changes, the controller fai

Solution 1:

A couple things...

1) You don't need $.noConflict(). Angular and jQuery play nice.

2) You should should put DOM scripting within an Angular Directive rather than a controller. Here's an example...

Directive*:

(function() {

    functionpersonPlayerDirective() {
        returnfunction(scope, $element, attr) {
            $element.find('.play-btn').click(function() {
                $element.find(".img-person").fadeOut('9000');
                $element.find(".play-btn").fadeOut('9000');
                $element.find(".player").fadeIn('9000');
            });
        };
    }

    angular.module('app', [])
        .directive('personPlayer', [personPlayerDirective]);
}());

Assuming your template is*:

<divperson-player><imgclass="img-polaroid img-person"ng-src="{{person.imgUrl}}"><divclass="player">
        I'm a player.
    </div><divclass="btn-group"><buttonclass="btn play-btn"><iclass="icon-play"></i> Play
        </button><buttonclass="btn pause-btn"><iclass="icon-pause"></i> Pause
        </button><buttonclass="btn stop-btn"><iclass="icon-stop"></i> Stop
        </button></div></div>

3) You could use CSS3 transitions with ng-click to achieve the same behavior without any jQuery DOM scripting...

New Template*:

<style>/* Twitter Bootstrap fade */.fade {
        opacity: 0;
        -webkit-transition: opacity 0.15s linear;
        -moz-transition: opacity 0.15s linear;
        -o-transition: opacity 0.15s linear;
        transition: opacity 0.15s linear;
    }
    .fade.in {
        opacity: 1;
    }
</style><divclass="person-player"><imgclass="img-polaroid img-person fade {{imgPersonFade}}"ng-src="{{person.imgUrl}}"><divclass="player fade {{playerFade}}">
        I'm a player.
    </div><divclass="btn-group"><buttonclass="btn play-btn fade {{playBtnFade}}"ng-click="playing=true"><iclass="icon-play"></i> Play
        </button><buttonclass="btn pause-btn"><iclass="icon-pause"></i> Pause
        </button><buttonclass="btn stop-btn"><iclass="icon-stop"></i> Stop
        </button></div></div>

Controller*:

functionDetailCtrl($scope, $routeParams, $http) {

    $scope.playing = false;

    // Update the *Fade scope attributes whenever the `playing` scope attribute changes$scope.$watch('playing', function (playing) {
        $scope.playerFade = playing ? 'in' : '';
        $scope.imgPersonFade = playing ? '' : 'in';
        $scope.playBtnFade = playing ? '' : 'in';
    });

    // Pull down a JSON file with my data to populate Angular template// ...

}

Anyway, like many of the new JS MV* application frameworks, Angular encourages you to "watch" for data/model changes rather than "listen" for DOM events. In fact, I recommend trying to use as little jQuery as possible until you've got the hang of this new paradigm shift.

* Code not tested :)