How to dynamically change header based on AngularJS partial view?

How to dynamically change header based on AngularJS partial view?

I am using ng-view to include AngularJS partial views, and I want to update the page title and h1 header tags based on the included view. These are out of scope of the partial view controllers though, and so I can’t figure out how to bind them to data set in the controllers.
If it was ASP.NET MVC you could use @ViewBag to do this, but I don’t know the equivalent in AngularJS. I’ve searched about shared services, events etc but still can’t get it working. Any way to modify my example so it works would be much appreciated.

<!-- should changed when ng-view changes -->

My JavaScript:
var myModule = angular.module(‘myModule’, []);
myModule.config([‘$routeProvider’, function($routeProvider) {
when(‘/test1’, {templateUrl: ‘test1.html’, controller: Test1Ctrl}).
when(‘/test2’, {templateUrl: ‘test2.html’, controller: Test2Ctrl}).
otherwise({redirectTo: ‘/test1’});

function Test1Ctrl($scope, $http) { $scope.header = “Test 1”;
/* ^ how can I put this in title and h1 */ }
function Test2Ctrl($scope, $http) { $scope.header = “Test 2”; }


Solution 1:

You could define controller at the <html> level.

 <html ng-app="app" ng-controller="titleCtrl">
     <title>{{ Page.title() }}</title>

You create service: Page and modify from controllers.

myModule.factory('Page', function() {
   var title = 'default';
   return {
     title: function() { return title; },
     setTitle: function(newTitle) { title = newTitle }

Inject Page and Call ‘Page.setTitle()’ from controllers.

Here is the concrete example:

Solution 2:

I just discovered a nice way to set your page title if you’re using routing:


var myApp = angular.module('myApp', ['ngResource'])

    ['$routeProvider', function($routeProvider) {
        $routeProvider.when('/', {
            title: 'Home',
            templateUrl: '/Assets/Views/Home.html',
            controller: 'HomeController'
        $routeProvider.when('/Product/:id', {
            title: 'Product',
            templateUrl: '/Assets/Views/Product.html',
            controller: 'ProductController'
    }]);['$rootScope', function($rootScope) {
    $rootScope.$on('$routeChangeSuccess', function (event, current, previous) {
        $rootScope.title = current.$$route.title;


<!DOCTYPE html>
<html ng-app="myApp">
    <title ng-bind="'myApp &mdash; ' + title">myApp</title>

Edit: using the ng-bind attribute instead of curlies {{}} so they don’t show on load

Solution 3:

Note that you can also set the title directly with javascript, i.e.,

$window.document.title = someTitleYouCreated;

This does not have data binding, but it suffices when putting ng-app in the <html> tag is problematic. (For example, using JSP templates where <head> is defined in exactly one place, yet you have more than one app.)

Solution 4:

Declaring ng-app on the html element provides root scope for both the head and body.

Therefore in your controller inject $rootScope and set a header property on this:

function Test1Ctrl($rootScope, $scope, $http) { $rootScope.header = "Test 1"; }

function Test2Ctrl($rootScope, $scope, $http) { $rootScope.header = "Test 2"; }

and in your page:

<title ng-bind="header"></title>

Solution 5:

The module angularjs-viewhead shows a mechanism to set the title on a per-view basis using only a custom directive.

It can either be applied to an existing view element whose content is already the view title:

<h2 view-title>About This Site</h2>

…or it can be used as a standalone element, in which case the element will be invisible in the rendered document and will only be used to set the view title:

<view-title>About This Site</view-title>

The content of this directive is made available in the root scope as viewTitle, so it can be used on the title element just like any other variable:

<title ng-bind-template="{{viewTitle}} - My Site">My Site</title>

It can also be used in any other spot that can “see” the root scope. For example:


This solution allows the title to be set via the same mechanism that is used to control the rest of the presentation: AngularJS templates. This avoids the need to clutter controllers with this presentational logic. The controller needs to make available any data that will be used to inform the title, but the template makes the final determination on how to present it, and can use expression interpolation and filters to bind to scope data as normal.

(Disclaimer: I am the author of this module, but I’m referencing it here only in the hope that it will help someone else to solve this problem.)

Solution 6:

Here is an adapted solution that works for me which doesn’t require injection of $rootScope into controllers for setting resource specific page titles.

In the master template:

<html data-ng-app="myApp">
    <title data-ng-bind="page.title"></title>

In the routing config:

$routeProvider.when('/products', {
    title: 'Products',
    templateUrl: '/partials/products.list.html',
    controller: 'ProductsController'

$routeProvider.when('/products/:id', {
    templateUrl: '/partials/products.detail.html',
    controller: 'ProductController'

And in the run block:['$rootScope', function($rootScope) {
    $ = {
        setTitle: function(title) {
            this.title = title + ' | Site Name';

    $rootScope.$on('$routeChangeSuccess', function(event, current, previous) {
        $$$route.title || 'Default Title');

Finally in the controller:

function ProductController($scope) {
    //Load product or use resolve in routing