Permalink
13717 lines (10798 sloc) 745 KB

1.6.0-rc.2 safety-insurance (2016-11-24)

Security Fixes

  • bootstrap: explicitly whitelist URL schemes for bootstrap. (#15427) (7f1b8b)

Bug Fixes

  • $sce: fix adjustMatcher to replace multiple '' and '*' (#7897) (991a2b)

Performance Improvements

  • **:* don't trigger digests after enter/leave of structural directives (f4fb6e #15322)

1.5.9 timeturning-lockdown (2016-11-24)

This is an interim release primarily to publish some security fixes, in particular a modification to ensure that Angular 1 can pass the linter checks for Mozilla add-ons.

Security Fixes

  • bootstrap:
    • do not auto-bootstrap when loaded from an extension (6ce291)
    • explicitly whitelist URL schemes for bootstrap (#15427) (4edd2d)
  • $location: throw if the path starts with double (back)slashes (353e3a)
  • $sniffer: don't use history.pushState in sandboxed Chrome Packaged Apps (367da5)
  • $parse:
    • block assigning to fields of a constructor prototype (d7e31b #14939)
    • correctly escape unsafe identifier characters (b01460)
  • $compile:
    • ensure that hidden input values are correct after history.back (6a2488)
    • lower the $sce context for src on video, audio, source, track (68fb70)

New Features

  • input:
    • add support for binding to input[range] (2e7121)
    • make support for input[range] opt-in (07b876)
    • fix step validation for input[number][ng-range-input] (64f6a6 #15257)
  • ngMock/$httpBackend: flush requests in any order (098b6f)

Bug Fixes

  • $httpBackend: complete the request on timeout (549edc #14969)
  • ngOptions: remove selected attribute from unselected options (d31b3a #14892)

Performance Improvements

  • $parse: improve performance of assignment expressions (f83c3d)
  • $compile: add provider option to turn off compilation of css class and comment directives (775c24)

1.6.0-rc.1 proximity-warning (2016-11-21)

New Features

  • ngModelOptions: allow options to be inherited from ancestor ngModelOptions (296cfc #10922)
  • $compile: set preAssignBindingsEnabled to false by default (bcd0d4 #15352)

Bug Fixes

  • ngModelOptions: handle debounce of updateOn triggers that are not in debounce list (789790)
  • ngMock/$controller: respect $compileProvider.preAssignBindingsEnabled() (7d9a79)
  • $location: throw if the path starts with double (back)slashes (4aa953)
  • core: do not auto-bootstrap when loaded from an extension. (0ff10e)
  • input[radio]: use strict comparison when evaluating checked-ness (5ac7da #15288)

Reverts

  • ngModelOptions: allow options to be inherited from ancestor ngModelOptions (fb0225)

Performance Improvements

  • ngOptions: avoid calls to element.value (3b7f29)

Breaking Changes

  • feat($compile): set preAssignBindingsEnabled to false by default (bcd0d4):

Previously, $compileProvider.preAssignBindingsEnabled was set to true by default. This means bindings were pre-assigned in component constructors. In Angular 1.5+ the place to put the initialization logic relying on bindings being present is the controller $onInit method.

To migrate follow the example below:

Before:

angular.module('myApp', [])
  .component('myComponent', {
    bindings: {value: '<'},
    controller: function() {
      this.doubleValue = this.value * 2;
    }
  });

After:

angular.module('myApp', [])
  .component('myComponent', {
    bindings: {value: '<'},
    controller: function() {
      this.$onInit = function() {
        this.doubleValue = this.value * 2;
      };
    }
  });

If you don't have time to migrate the code at the moment, you can flip the setting back to true:

angular.module('myApp', [])
  .config(function($compileProvider) {
    $compileProvider.preAssignBindingsEnabled(true);
  })
  .component('myComponent', {
    bindings: {value: '<'},
    controller: function() {
      this.doubleValue = this.value * 2;
    }
  });

Don't do this if you're writing a library, though, as you shouldn't change global configuration then.

  • fix(input[radio]): use strict comparison when evaluating checked-ness (5ac7da):

When using input[radio], the checked status is now determined by doing a strict comparison between the value of the input and the ngModel.$viewValue. Previously, this was a non-strict comparison (==).

This means in the following examples the radio is no longer checked:

  <!-- this.selected = 0 -->
  <input type="radio" ng-model="$ctrl.selected" value="0" >

  <!-- this.selected = 0; this.value = false; -->
  <input type="radio" ng-model="$ctrl.selected" ng-value="$ctrl.value" >

The migration strategy is to convert values that matched with non-strict conversion so that they will match with strict conversion.

  • feat(ngModelOptions): allow options to be inherited from ancestor ngModelOptions (296cfc):

The programmatic API for ngModelOptions has changed. You must now read options via the ngModelController.$options.getOption(name) method, rather than accessing the option directly as a property of the ngModelContoller.$options object. This does not affect the usage in templates and only affects custom directives that might have been reading options for their own purposes.

One benefit of these changes, though, is that the ngModelControler.$options property is now guaranteed to be defined so there is no need to check before accessing.

So, previously:

var myOption = ngModelController.$options && ngModelController.$options['my-option'];

and now:

var myOption = ngModelController.$options.getOption('my-option');

1.6.0-rc.0 bracing-vortex (2016-10-26)

Major notes

Please read the Sandbox Removal Blog Post.

Bug Fixes

  • input: fix step validation for input[type=number]/input[type=range] (081d06 #15257)
  • jqLite:
  • $parse:
    • treat falsy values as defined in assignment expressions (4f44e0)
    • call once stable bind-once expressions with filter (3b5751)
    • Handle sign of -undefined consistently (c1eaf3)
  • ngModel: treat synchronous validators as boolean always (7bc71a #14734)
  • $q: treat thrown errors as regular rejections (e13eea #3174 #15213)
  • ngTransclude: use fallback content if only whitespace is provided (32aa7e #15077)
  • $compile:
    • don't throw tplrt error when there is a whitespace around a top-level comment (76d3da #15108)
    • disallow linking the same element more than once (1e1fbc)
    • lower the $sce context for src on video, audio, and track. (ad9a99)
    • correctly merge consecutive text nodes on IE11 (13c252 #14924)
    • secure link[href] as a RESOURCE_URLs in $sce. (04cad4 #14687)
    • don't add leading white-space in attributes for a specific merge case (305ba1)
    • don't trim white-space in attributes (97bbf8 #5513 #5597)
    • move check for interpolation of on-event attributes to compile time (b89c21 #13267)
  • select:
    • add/remove selected attribute for selected/unselected options (c75698)
    • don't register options when select has no ngModel (e8c2e1)
    • handle model updates when options are manipulated (47c15f)
    • remove workaround for Chrome bug (87eff2)
  • select, ngOptions: make the handling of unknown / empty options consistent (2785ad)
  • ngValue: set the element's value property in addition to the value attribute (e6afca #14031)
  • aria/ngModel: do not overwrite the default $isEmpty() method for checkboxes (975a61 #14621)
  • $resource:
    • fulfill promise with the correct value on error (5f6949 #14837)
    • pass all extra, owned properties as params (acb545 #14866)
    • add semicolon to whitelist of delimiters to unencode in URL params (2456ab)
  • $http:
    • avoid Possibly Unhandled Rejection error when the request fails (47583d #13869)
    • properly increment/decrement $browser.outstandingRequestCount (4f6f2b #13782 #14921)
  • ngMock: trigger digest in $httpBackend.verifyNoOutstandingRequest() (267ee9 #13506)
  • ngAria:
    • bind to keydown instead of keypress in ngClick (ad41ba #14063)
    • don't add roles to native control elements (9978de #14076)
  • ngBind: use same string representation as $interpolate (fa80a6)
  • ngMock/$httpBackend: fail if a url is provided but is undefined (7551b8 #8442 #10934)
  • $route: don't process route change controllers and templates for redirectTo routes (7f4b35 #3332)
  • loader: module.decorator order of operations is now irrelevant (6a2ebd #12382)
  • ngAnimate: make svg elements work with classNameFilter (81bf7e)

New Features

  • jqLite:
    • implement jqLite(f) as alias to jqLite(document).ready(f) (369fb7)
    • don't throw for elements with missing getAttribute (4e6c14)
    • don't remove a boolean attribute for .attr(attrName, '') (3faf45)
    • remove the attribute for .attr(attribute, null) (4e3624)
    • return [] for .val() on <select multiple> with no selection (d882fd)
  • $http:
    • remove deprecated callback methods: success()/error() (b54a39)
    • JSONP callback must be specified by jsonpCallbackParam config (fb6634 #15161 #11352)
    • JSONP requests now require a trusted resource URL (6476af #11352)
  • ngModelOptions: allow options to be inherited from ancestor ngModelOptions (87a2ff #10922)
  • input:
    • add support for binding to input[type=range] (913016 #5892 #14870)
    • add support for step to input[type=number] (e1da4be #10597)
    • allow ngTrim to work for input[type=radio] (47724b)
  • ngRoute: allow ngView to be included in an asynchronously loaded template (c13c66 #1213)
  • select: support values of any type added with ngValue (f02b70 #9842)
  • $interpolate: use custom toString() function if present (a5fd2e #7317 #11406)
  • $route: implement resolveRedirectTo (e98656 #5150)
  • $q: report promises with non rejection callback (c9dffd #13653 #7992)
  • $location: default hashPrefix to '!' (aa077e #13812)

Performance Improvements

  • form, ngModel: change controllers to use prototype methods (9e24e7)
  • select: don't prepend unknown option if already prepended (ba36bd)
  • $animate: listen for document visibility changes (d71dc2)
  • injector: cache the results of the native class detection check (5ceb5d)
  • $parse: Inline constants (bd7d5f)
  • $compile: use strict comparison for controller === '@' (bbd3db)
  • $parse: remove Angular expression sandbox (1547c7 #15094)

Breaking Changes

jqLite due to:

  • fc0c11: camelCase keys in jqLite#data

Previously, keys passed to the data method were left untouched. Now they are internally camelCased similarly to how jQuery handles it, i.e. only single (!) hyphens followed by a lowercase letter get converted to an uppercase letter. This means keys a-b and aB represent the same data piece; writing to one of them will also be reflected if you ask for the other one.

If you use Angular with jQuery, it already behaved in this way so no changes are required on your part.

To migrate the code follow the examples below:

BEFORE:

/* 1 */
elem.data('my-key', 2);
elem.data('myKey', 3);

/* 2 */
elem.data('foo-bar', 42);
elem.data()['foo-bar']; // 42
elem.data()['fooBar']; // undefined

/* 3 */
elem.data()['foo-bar'] = 1;
elem.data()['fooBar'] = 2;
elem.data('foo-bar'); // 1

AFTER:

/* 1 */
// Rename one of the keys as they would now map to the same data slot.
elem.data('my-key', 2);
elem.data('my-key2', 3);

/* 2 */
elem.data('foo-bar', 42);
elem.data()['foo-bar']; // undefined
elem.data()['fooBar']; // 42

/* 3 */
elem.data()['foo-bar'] = 1;
elem.data()['fooBar'] = 2;
elem.data('foo-bar'); // 2
  • 73050c: align jqLite camelCasing logic with JQuery

Before, when Angular was used without jQuery, the key passed to the css method was more heavily camelCased; now only a single (!) hyphen followed by a lowercase letter is getting transformed. This also affects APIs that rely on the css method, like ngStyle.

If you use Angular with jQuery, it already behaved in this way so no changes are needed on your part.

To migrate the code follow the example below:

Before:

HTML:

// All five versions used to be equivalent.
<div ng-style={background_color: 'blue'}></div>
<div ng-style={'background:color': 'blue'}></div>
<div ng-style={'background-color': 'blue'}></div>
<div ng-style={'background--color': 'blue'}></div>
<div ng-style={backgroundColor: 'blue'}></div>

JS:

// All five versions used to be equivalent.
elem.css('background_color', 'blue');
elem.css('background:color', 'blue');
elem.css('background-color', 'blue');
elem.css('background--color', 'blue');
elem.css('backgroundColor', 'blue');

// All five versions used to be equivalent.
var bgColor = elem.css('background_color');
var bgColor = elem.css('background:color');
var bgColor = elem.css('background-color');
var bgColor = elem.css('background--color');
var bgColor = elem.css('backgroundColor');

After:

HTML:

// Previous five versions are no longer equivalent but these two still are.
<div ng-style={'background-color': 'blue'}></div>
<div ng-style={backgroundColor: 'blue'}></div>

JS:

// Previous five versions are no longer equivalent but these two still are.
elem.css('background-color', 'blue');
elem.css('backgroundColor', 'blue');

// Previous five versions are no longer equivalent but these two still are.
var bgColor = elem.css('background-color');
var bgColor = elem.css('backgroundColor');
  • 3faf45: don't remove a boolean attribute for .attr(attrName, '')

Before, using the attr method with an empty string as a value would remove the boolean attribute. Now it sets it to its lowercase name as was happening for every non-empty string so far. The only two values that remove the boolean attribute are now null & false, just like in jQuery.

To migrate the code follow the example below:

Before:

elem.attr(booleanAttrName, '');

After:

elem.attr(booleanAttrName, false);

or:

elem.attr(booleanAttrName, null);
  • 4e3624: remove the attribute for .attr(attribute, null)

Invoking elem.attr(attributeName, null) would set the attributeName attribute value to a string "null", now it removes the attribute instead.

To migrate the code follow the example below:

Before:

elem.attr(attributeName, null);

After:

elem.attr(attributeName, "null");
  • d882fd: return [] for .val() on <select multiple> with no selection

For the jqLite element representing a select element in the multiple variant with no options chosen the .val() getter used to return null and now returns an empty array.

To migrate the code follow the example below:

Before:

HTML:

    <select multiple>
        <option>value 1</option>
        <option>value 2</option>
    </select>

JavaScript:

    var value = $element.val();
    if (value) {
        /* do something */
    }

After:

HTML:

    <select multiple>
        <option>value 1</option>
        <option>value 2</option>
    </select>

JavaScript:

    var value = $element.val();
    if (value.length > 0) {
        /* do something */
    }

ngModel due to:

  • 7bc71a: treat synchronous validators as boolean always

Previously, only a literal false return would resolve as the synchronous validator failing. Now, all falsy JavaScript values are treated as failing the validator, as one would naturally expect.

Specifically, the values 0 (the number zero), null, NaN and '' (the empty string) used to be considered valid (passing) and they are now considered invalid (failing). The value undefined was treated similarly to a pending asynchronous validator, causing the validation to be pending. undefined is also now considered invalid.

To migrate, make sure your synchronous validators are returning either a literal true or a literal false value. For most code, we expect this to already be the case. Only a very small subset of projects will be affected.

Namely, anyone using undefined or any falsy value as a return will now see their validation failing, whereas previously falsy values other than undefined would have been seen as passing and undefined would have been seen as pending.

  • 9e24e7: change controllers to use prototype methods

The use of prototype methods instead of new methods per instance removes the ability to pass NgModelController and FormController methods without context.

For example

$scope.$watch('something', myNgModelCtrl.$render)

will no longer work because the $render method is passed without any context. This must now be replaced with

$scope.$watch('something', function() {
  myNgModelCtrl.$render();
})

or possibly by using Function.prototype.bind or angular.bind.

aria/ngModel due to:

  • 975a61: do not overwrite the default $isEmpty() method for checkboxes

Custom checkbox-shaped controls (e.g. checkboxes, menuitemcheckboxes), no longer have a custom $isEmpty() method on their NgModelController that checks for value === false. Unless overwritten, the default $isEmpty() method will be used, which treats undefined, null, NaN and '' as "empty".

Note: The $isEmpty() method is used to determine if the checkbox is checked ("not empty" means "checked") and thus it can indirectly affect other things, such as the control's validity with respect to the required validator (e.g. "empty" + "required" --> "invalid").

Before:

var template = '<my-checkbox role="checkbox" ng-model="value"></my-checkbox>';
var customCheckbox = $compile(template)(scope);
var ctrl = customCheckbox.controller('ngModel');

scope.$apply('value = false');
console.log(ctrl.$isEmpty());   //--> true

scope.$apply('value = true');
console.log(ctrl.$isEmpty());   //--> false

scope.$apply('value = undefined'/* or null or NaN or '' */);
console.log(ctrl.$isEmpty());   //--> false

After:

var template = '<my-checkbox role="checkbox" ng-model="value"></my-checkbox>';
var customCheckbox = $compile(template)(scope);
var ctrl = customCheckbox.controller('ngModel');

scope.$apply('value = false');
console.log(ctrl.$isEmpty());   //--> false

scope.$apply('value = true');
console.log(ctrl.$isEmpty());   //--> false

scope.$apply('value = undefined'/* or null or NaN or '' */);
console.log(ctrl.$isEmpty());   //--> true

If you want to have a custom $isEmpty() method, you need to overwrite the default. For example:

.directive('myCheckbox', function myCheckboxDirective() {
  return {
    require: 'ngModel',
    link: function myCheckboxPostLink(scope, elem, attrs, ngModelCtrl) {
      ngModelCtrl.$isEmpty = function myCheckboxIsEmpty(value) {
        return !value;   // Any falsy value means "empty"

        // Or to restore the previous behavior:
        // return value === false;
      };
    }
  };
})

$http due to:

  • b54a39: remove deprecated callback methods: success()/error()

$http's deprecated custom callback methods - success() and error() - have been removed. You can use the standard then()/catch() promise methods instead, but note that the method signatures and return values are different.

success(fn) can be replaced with then(fn), and error(fn) can be replaced with either then(null, fn) or catch(fn).

Before:

$http(...).
  success(function onSuccess(data, status, headers, config) {
    // Handle success
    ...
  }).
  error(function onError(data, status, headers, config) {
    // Handle error
    ...
  });

After:

$http(...).
  then(function onSuccess(response) {
    // Handle success
    var data = response.data;
    var status = response.status;
    var statusText = response.statusText;
    var headers = response.headers;
    var config = response.config;
    ...
  }, function onError(response) {
    // Handle error
    var data = response.data;
    var status = response.status;
    var statusText = response.statusText;
    var headers = response.headers;
    var config = response.config;
    ...
  });

// or

$http(...).
  then(function onSuccess(response) {
    // Handle success
    var data = response.data;
    var status = response.status;
    var statusText = response.statusText;
    var headers = response.headers;
    var config = response.config;
    ...
  }).
  catch(function onError(response) {
    // Handle error
    var data = response.data;
    var status = response.status;
    var statusText = response.statusText;
    var headers = response.headers;
    var config = response.config;
    ...
  });

Note: There is a subtle difference between the variations showed above. When using $http(...).success(onSuccess).error(onError) or $http(...).then(onSuccess, onError), the onError() callback will only handle errors/rejections produced by the $http() call. If the onSuccess() callback produces an error/rejection, it won't be handled by onError() and might go unnoticed. In contrast, when using $http(...).then(onSuccess).catch(onError), onError() will handle errors/rejections produced by both $http() and onSuccess().

  • fb6634: JSONP callback must be specified by jsonpCallbackParam config

You can no longer use the JSON_CALLBACK placeholder in your JSONP requests. Instead you must provide the name of the query parameter that will pass the callback via the jsonpCallbackParam property of the config object, or app-wide via the $http.defaults.jsonpCallbackParam property, which is "callback" by default.

Before this change:

$http.json('trusted/url?callback=JSON_CALLBACK');
$http.json('other/trusted/url', {params: {cb:'JSON_CALLBACK'}});

After this change:

$http.json('trusted/url');
$http.json('other/trusted/url', {jsonpCallbackParam:'cb'});
  • 6476af: JSONP requests now require a trusted resource URL

All JSONP requests now require the URL to be trusted as resource URLs. There are two approaches to trust a URL:

Whitelisting with the $sceDelegateProvider.resourceUrlWhitelist() method.

You configure this list in a module configuration block:

appModule.config(['$sceDelegateProvider', function($sceDelegateProvider) {
  $sceDelegateProvider.resourceUrlWhiteList([
    // Allow same origin resource loads.
    'self',
    // Allow JSONP calls that match this pattern
    'https://some.dataserver.com/**.jsonp?**'
  ]);
}]);

Explicitly trusting the URL via the $sce.trustAsResourceUrl(url) method.

You can pass a trusted object instead of a string as a URL to the $http service:

var promise = $http.jsonp($sce.trustAsResourceUrl(url));
  • 4f6f2b: properly increment/decrement $browser.outstandingRequestCount

HTTP requests now update the outstanding request count synchronously. Previously the request count would not have been updated until the request to the server is actually in flight. Now the request count is updated before the async interceptor is called.

The new behaviour is correct but it may change the expected behaviour in a small number of e2e test cases where an async request interceptor is being used.

$q due to:

  • e13eea: treat thrown errors as regular rejections

Previously, throwing an error from a promise's onFulfilled or onRejection handlers, would result in passing the error to the $exceptionHandler() (in addition to rejecting the promise with the error as reason).

Now, a thrown error is treated exactly the same as a regular rejection. This applies to all services/controllers/filters etc that rely on $q (including built-in services, such as $http and $route). For example, $http's transformRequest/Response functions or a route's redirectTo function as well as functions specified in a route's resolve object, will no longer result in a call to $exceptionHandler() if they throw an error. Other than that, everything will continue to behave in the same way; i.e. the promises will be rejected, route transition will be cancelled, $routeChangeError events will be broadcasted etc.

  • c9dffd: report promises with non rejection callback

Unhandled rejected promises will be logged to $exceptionHandler.

Tests that depend on specific order or number of messages in $exceptionHandler will need to handle rejected promises report.

ngTransclude due to:

  • 32aa7e: use fallback content if only whitespace is provided

Previously whitespace only transclusion would be treated as the transclusion being "not empty", which meant that fallback content was not used in that case.

Now if you only provide whitespace as the transclusion content, it will be assumed to be empty and the fallback content will be used instead.

If you really do want whitespace then you can force it to be used by adding a comment to the whitespace.

ngModelOptions due to:

  • 87a2ff: allow options to be inherited from ancestor ngModelOptions

Previously, if a setting was not applied on ngModelOptions, then it would default to undefined. Now the setting will be inherited from the nearest ngModelOptions ancestor.

It is possible that an ngModelOptions directive that does not set a property, has an ancestor ngModelOptions that does set this property to a value other than undefined. This would cause the ngModel and input controls below this ngModelOptions directive to display different behaviour. This is fixed by explicitly setting the property in the ngModelOptions to prevent it from inheriting from the ancestor.

For example if you had the following HTML:

<form ng-model-options="{updateOn: 'blur'}">
  <input ng-model="..." ng-model-options="{allowInvalid: true}">
</form>

Then before this change the input would update on the default event not blur. After this change the input will inherit the option to update on blur. If you want the original behaviour then you will need to specify the option on the input as well:

<form ng-model-options="{updateOn: 'blur'}">
  <input ng-model="..." ng-model-options="{updateOn: 'default', allowInvalid: true}">
</form>

The programmatic API for ngModelOptions has changed. You must now read options via the getOption method, rather than accessing the option directly as a property of the options object. This does not affect the usage in templates and only affects custom directives that might have been reading options for their own purposes.

$compile due to:

  • 13c252: correctly merge consecutive text nodes on IE11

Note: Everything described below affects IE11 only.

Previously, consecutive text nodes would not get merged if they had no parent. They will now, which might have unexpectd side effects in the following cases:

  1. Passing an array or jqLite/jQuery collection of parent-less text nodes to $compile directly:

    // Assuming:
    var textNodes = [
      document.createTextNode('{{'),
      document.createTextNode('"foo:"'),
      document.createTextNode('}}')
    ];
    var compiledNodes = $compile(textNodes)($rootScope);
    
    // Before:
    console.log(compiledNodes.length);   // 3
    console.log(compiledNodes.text());   // {{'foo'}}
    
    // After:
    console.log(compiledNodes.length);   // 1
    console.log(compiledNodes.text());   // foo
    
    // To get the old behavior, compile each node separately:
    var textNodes = [
      document.createTextNode('{{'),
      document.createTextNode('"foo"'),
      document.createTextNode('}}')
    ];
    var compiledNodes = angular.element(textNodes.map(function (node) {
      return $compile(node)($rootScope)[0];
    }));
  2. Using multi-slot transclusion with non-consecutive, default-content text nodes (that form interpolated expressions when merged):

    // Assuming the following component:
    .component('someThing', {
     template: '<ng-transclude><!-- Default content goes here --></ng-transclude>'
     transclude: {
       ignored: 'veryImportantContent'
     }
    })
    <!-- And assuming the following view: -->
    <some-thing>
     {{
     <very-important-content>Nooot</very-important-content>
     'foo'}}
    </some-thing>
    
    <!-- Before: -->
    <some-thing>
     <ng-transclude>
       {{       <-- Two separate
       'foo'}}  <-- text nodes
     </ng-transclude>
    </some-thing>
    
    <!-- After: -->
    <some-thing>
     <ng-transclude>
       foo  <-- The text nodes were merged into `{{'foo'}}`, which was then interpolated
     </ng-transclude>
    </some-thing>
    
    <!-- To (visually) get the old behavior, wrap top-level text nodes on -->
    <!-- multi-slot transclusion directives into `<span>` elements; e.g.: -->
    <some-thing>
     <span>{{</span>
     <very-important-content>Nooot</very-important-content>
     <span>'foo'}}</span>
    </some-thing>
    
    <!-- Result: -->
    <some-thing>
     <ng-transclude>
       <span>{{</span>       <-- Two separate
       <span>'foo'}}</span>  <-- nodes
     </ng-transclude>
    </some-thing>
  • b89c21: move check for interpolation of on-event attributes to compile time

Using interpolation in any on* event attributes (e.g. <button onclick="{{myVar}}">) will now throw the "nodomevents" error at compile time. Previously the nodomevents was thrown at link time. The new behavior makes it consistent with the "selmulti" error. The breaking change should be rare, as it relates to incorrect API use that should not make it to production apps in the first place.

  • 04cad4: secure link[href] as a RESOURCE_URL in $sce

link[href] attributes are now protected via $sce, which prevents interpolated values that fail the RESOURCE_URL context tests from being used in interpolation.

For example if the application is running at https://docs.angularjs.org then the following will fail:

<link href="{{ 'http://mydomain.org/unsafe.css' }}" rel="stylesheet">

By default, RESOURCE_URL safe URLs are only allowed from the same domain and protocol as the application document.

To use URLs from other domains and/or protocols, you may either whitelist them or wrap it into a trusted value by calling $sce.trustAsResourceUrl(url).

  • 97bbf8: don't trim white-space in attributes

White-space in attributes is no longer trimmed automatically. This includes leading and trailing white-space, and attributes that are purely white-space.

To migrate, attributes that require trimming must now be trimmed manually.

A common cases where stray white-space can cause problems is when attribute values are compared, for example in an $observer:

Before:

$attrs.$observe('myAttr', function(newVal) {
  if (newVal === 'false') ...
});

To migrate, the attribute value should be trimmed manually:

$attrs.$observe('myAttr', function(newVal) {
  if (newVal.trim() === 'false') ...
});

Note that $parse trims expressions automatically, so attributes with expressions (e.g. directive bindings) are unlikely to be affected by stray white-space.

ngRoute due to:

  • c13c66: allow ngView to be included in an asynchronously loaded template

In cases where ngView was loaded asynchronously, $route (and its dependencies; e.g. $location) might also have been instantiated asynchronously. After this change, $route (and its dependencies) will - by default - be instantiated early on.

Although this is not expected to have unwanted side-effects in normal application bebavior, it may affect your unit tests: When testing a module that (directly or indirectly) depends on ngRoute, a request will be made for the default route's template. If not properly "trained", $httpBackend will complain about this unexpected request.

You can restore the previous behavior (and avoid unexpected requests in tests), by using $routeProvider.eagerInstantiationEnabled(false).

  • 7f4b35: don't process route change controllers and templates for redirectTo routes

The $route service no longer instantiates controllers nor calls resolves or template functions for routes that have a redirectTo unless the redirectTo is a function that returns undefined.

  • e98656: implement resolveRedirectTo

Previously, if redirectTo was a function that threw an Error, execution was aborted without firing a $routeChangeError event. Now, if a redirectTo function throws an Error, a $routeChangeError event will be fired.

ngMock due to:

  • 267ee9: trigger digest in $httpBackend.verifyNoOutstandingRequest()

Calling $httpBackend.verifyNoOutstandingRequest() will trigger a digest. This will ensure that requests fired asynchronously will also be detected (without the need to manually trigger a digest). This is not expected to affect the majority of test-suites. Most of the time, a digest is (directly or indirectly) triggered anyway, before calling verifyNoOutstandingRequest(). In the unlikely case that a test needs to verify the timing of a request with respect to the digest cycle, you should rely on other means, such as mocking and/or spying.

  • 7551b8: fail if a url is provided but is undefined

It is no longer valid to explicitly pass undefined as the url argument to any of the $httpBackend.when...() and $httpBackend.expect...() methods.

While this argument is optional, it must have a defined value if it is provided.

Previously passing an explicit undefined value was ignored but this lead to invalid tests passing unexpectedly.

ngAria due to:

  • ad41ba: bind to keydown instead of keypress in ngClick

If you were explicitly setting the value of the bindKeypress flag, you need to change your code to use bindKeydown instead.

Before: $ariaProvider.config({bindKeypress: xyz}) After: $ariaProvider.config({bindKeydown: xyz})

Note: If the element already has any of the ngKeydown/ngKeyup/ngKeypress directives, ngAria will not bind to the keydown event, since it assumes that the developer has already taken care of keyboard interaction for that element.

Although it is not expected to affect many applications, it might be desirable to keep the previous behavior of binding to the keypress event instead of the keydown. In that case, you need to manually use the ngKeypress directive (in addition to ngClick).

Before:

<div ng-click="onClick()">
  I respond to `click` and `keypress` (not `keydown`)
</div>

After:

<div ng-click="onClick()" ng-keypress="onClick()">
  I respond to `click` and `keypress` (not `keydown`)
</div>
<!-- OR -->
<div ng-click="onClick()">
  I respond to `click` and `keydown` (not `keypress`)
</div>

Finally, it is possible that this change affects your unit or end-to-end tests. If you are currently expecting your custom buttons to automatically respond to the keypress event (due to ngAria), you need to change the tests to trigger keydown events instead.

  • 9978de: don't add roles to native control elements

ngAria will no longer add the "role" attribute to native control elements (textarea, button, select, summary, details, a, and input). Previously, "role" was not added to input, but all others in the list.

This should not affect accessibility, because native inputs are accessible by default, but it might affect applications that relied on the "role" attribute being present (e.g. for styling or as directive attributes).

$resource due to:

  • acb545: pass all extra, owned properties as params

All owned properties of the params object that are not used to replace URL params, will be passed to $http as config.params (to be used as query parameters in the URL), even if Object.prototype has a property with the same name. E.g.:

Before:

var Foo = $resource('/foo/:id');
Foo.get({id: 42, bar: 'baz', toString: 'hmm'});
    // URL: /foo/42?bar=baz
    // Note that `toString` is _not_ included in the query,
    // because `Object.prototype.toString` is defined :(

After:

var Foo = $resource('/foo/:id');
Foo.get({id: 42, bar: 'baz', toString: 'hmm'});
    // URL: /foo/42?bar=baz&toString=hmm
    // Note that `toString` _is_ included in the query, as expected :)
  • 2456ab: add semicolon to whitelist of delimiters to unencode in URL params

Although it shouldn't matter in practice (since both the encoded and the unencoded ; character would be interpreted identically by the server), this change could break some tests: For example, where $httpBackend was set up to expect an encoded ; character, but the request is made to the URL with an unencoded ; character.

select due to:

  • f02b70: support values of any type added with ngValue

<option> elements added to <select ng-model> via ngValue now add their values in hash form, i.e. <option ng-value="myString"> becomes <option ng-value="myString" value="string:myString">.

This is done to support binding options with values of any type to selects.

This should rarely affect applications, as the values of options are usually not relevant to the application logic, but it's possible that option values are checked in tests.

  • e8c2e1: don't register options when select has no ngModel

Option elements will no longer set their value attribute from their text value when their select element has no ngModel associated. Setting the value is only needed for the select directive to match model values and options. If no ngModel is present, the select directive doesn't need it.

This should not affect many applications as the behavior was undocumented and not part of a public API. It also has no effect on the usual HTML5 behavior that sets the select value to the option text if the option does not provide a value attribute.

ngBind due to:

  • fa80a6: use same string representation as $interpolate

ngBind now uses the same logic as $interpolate (i.e. {{myString}}) when binding, which means values other than strings are now transformed as following:

  • null / undefined become empty string
  • with an object's custom toString() function, except if the object is a Date, Array, or Number
  • otherwise with JSON.stringify

Previously, ngBind would always use toString().

The following examples show the different output:

$scope.myPlainObject = {a: 1, b: 2};
$scope.myCustomObject = {a: 1, b: 2, toString: function() {return 'a+b';}};

Plain Object:

<!-- Before: -->
<span ng-bind="myPlainObject">[object Object]</span>

<!-- After: -->
<span ng-bind="myPlainObject">{'a':1,'b':2}</span>

Object with custom toString():

<!-- Before: -->
<span ng-bind="myCustomObject">[object Object]</span>

<!-- After: -->
<span ng-bind="myCustomObject">a+b</span>

If you want the output of toString(), you can use it directly on the value in ngBind:

<span ng-bind="myObject.toString()">[object Object]</span>

$interpolate due to:

  • a5fd2e: use custom toString() function if present

When converting values to strings, interpolation now uses a custom toString() function on objects that are not Number, Array or Date (custom means that the toString function is not the same as Object.prototype.toString). Otherwise, interpolation uses JSON.stringify() as usual.

Should you have a custom toString() function but still want the output of JSON.stringify(), migrate as shown in the following examples:

Before:

<span>{{myObject}}</span>

After - use the json filter to stringify the object:

<span>{{myObject | json}}</span>

loader due to:

  • 6a2ebd: module.decorator order of operations is now irrelevant

module.decorator declarations are now processed as part of the module.config queue and may result in providers being decorated in a different order if module.config blocks are also used to decorate providers via $provide.decorator.

For example, consider the following declaration order in which 'theFactory' is decorated by both a module.decorator and a $provide.decorator:

angular
  .module('theApp', [])
  .factory('theFactory', theFactoryFn)
  .config(function($provide) {
    $provide.decorator('theFactory', provideDecoratorFn);
  })
  .decorator('theFactory', moduleDecoratorFn);

Prior to this fix, 'theFactory' provider would be decorated in the following order:

  1. moduleDecoratorFn
  2. provideDecoratorFn

The result of this fix changes the order in which 'theFactory' is decorated because now module.decorator declarations are processed in the same order as module.config declarations:

  1. provideDecoratorFn
  2. moduleDecoratorFn

$location due to:

  • aa077e: default hashPrefix to '!'

The hash-prefix for $location hash-bang URLs has changed from the empty string "" to the bang "!". If your application does not use HTML5 mode or is being run on browsers that do not support HTML5 mode, and you have not specified your own hash-prefix then client side URLs will now contain a "!" prefix. For example, rather than mydomain.com/#/a/b/c will become mydomain.com/#!/a/b/c.

If you actually wanted to have no hash-prefix then you should configure this by adding a configuration block to you application:

appModule.config(['$locationProvider', function($locationProvider) {
  $locationProvider.hashPrefix('');
}]);

input[type=range] due to:

  • 913016: add support for binding to input[type=range]

Due to the way that input[type=range] elements behave this feature modifies the behavior of such elements when bound to ngModel:

  • Like input[type=number], it requires the model to be a Number, and will set the model to a Number
  • it supports setting the min/max values only via the min/max attributes
  • it follows the browser behavior of never allowing an invalid value. That means, when the browser converts an invalid value (empty: null, undefined, false ..., out of bounds: greater than max, less than min) to a valid value, the input will in turn set the model to this new valid value via $setViewValue.
    • this means a range input will never be required and never have a non-Number model value, once the ngModel directive is initialized.
    • this behavior is supported when the model changes and when the min/max attributes change in a way that prompts the browser to update the input value.
  • browsers that do not support input[type=range] (IE9) handle the input like a number input (with validation etc.)

input[type=number] due to:

  • e1da4be: add support for step to input[type=number]

Number inputs that use ngModel and specify a step constraint (via step/ngStep attributes) will now have a new validator (step), which will verify that the current value is valid under the step constraint (according to the spec). Previously, the step constraint was ignored by ngModel, treating values as valid even when there was a step-mismatch.

If you want to restore the previous behavior (use the step attribute while disabling step validation), you can overwrite the built-in step validator with a custom directive. For example:

// For all `input` elements...
.directive('input', function() {
  return {
    restrict: 'E',
    require: '?ngModel',
    link: function (scope, elem, attrs, ngModelCtrl) {
      // ...that are of type "number" and have `ngModel`...
      if ((attrs.type === 'number') && ngModelCtrl) {
        // ...remove the `step` validator.
        delete ngModelCtrl.$validators.step;
      }
    }
  };
})

1.4.13 croaking-elderweed (2016-10-10)

Bug Fixes

  • input: ensure that hidden input values are correct after history back (693d1334

1.2.31 barking-moustache (2016-10-10)

Bug Fixes

  • input: ensure that hidden input values are correct after history back (7ec663fc

1.4.12

Invalid release

1.5.8 arbitrary-fallbacks (2016-07-22)

Bug Fixes

  • $animate: do not get affected by custom, enumerable properties on Object.prototype (181e4401, #14804, #14830)
  • $compile: ensure $doCheck hooks can be defined in the controller constructor (3010ed4e, #14811)
  • $injector: fix class detection RegExp (4724d56c, #14533)
  • $jsonpCallbacks: do not overwrite callbacks added by other apps (1778d347, #14824)
  • $timeout: make $flush handle new $timeouts added in $timeout callbacks (1a387ba5, #5420, #14686)
  • copy: fix handling of typed subarrays (1645924d, #14842, #14845)
  • modules: allow modules to be loaded in any order when using angular-loader (98e4a220, #9140, #14794)
  • ngAnimate: allow removal of class that is scheduled to be added with requestAnimationFrame (7ccfe92b, #14582)
  • ngMocks: allow ErrorAddingDeclarationLocationStack to be recognized as an Error (c6074dc3, #13821, #14344)
  • ngOptions: don't duplicate groups with falsy values (c3bfd7f5)
  • ngTransclude:

Features

Performance Improvements

  • $compile: wrap try/catch of collect comment directives into a function to avoid V8 deopt (acd45518, #14848)

1.2.30 patronal-resurrection (2016-07-21)

Note: This release contains some security fixes that required breaking changes. Since the legacy 1.2.x branch is the only version branch that supports IE8, it was necessary to introduce a couple of low-impact breaking changes in a patch release - something we generally avoid - in order to make the fixes available to people that still need IE8 support.

Bug Fixes

  • $compile:
  • ngSanitize: blacklist the attribute usemap as it can be used as a security exploit (ac0d5286, #14903)
  • ngAnimate: do not use event.timeStamp anymore for time tracking (8d83b563, #13494, #13495)

Breaking Changes

link[href] attributes are now protected via $sce, which prevents interpolated values that fail the RESOURCE_URL context tests from being used in interpolation. For example if the application is running at https://mydomain.org/ then the following will fail:

<link rel="stylesheet" href="{{ 'https://otherdomain.org/unsafe.css' }}" />

By default, RESOURCE_URL safe URLs are only allowed from the same domain and protocol as the application document. To use URLs from other domains and/or protocols, you may either whitelist them using $sceDelegateProvider.resourceUrlWhitelist(...) or wrap them into a trusted value by calling $sce.trustAsResourceUrl(url).

The $sanitize service will now remove instances of the usemap attribute from any elements passed to it.

This attribute is used to reference another element by name or id. Since the name and id attributes are already blacklisted, a sanitized usemap attribute could only reference unsanitized content, which is a security risk.

1.5.7 hexagonal-circumvolution (2016-06-15)

Bug Fixes

Features

1.4.12 cultural-conservation (2016-06-15)

This release contains only documentation updates. Specifically, it restores the old (deprecated) version of the tutorial on the 1.4.x branch. If someone needs a version of the tutorial that is compatible with v1.4, they can find it at https://code.angularjs.org/1.4.12/docs/tutorial/.

As always, the latest and greatest version of the tutorial can be found on the master branch (at https://docs.angularjs.org/tutorial/). We strongly recommend using this version as it is kept up-to-date, showcases several new features introduced in v1.5 or later and follows modern best practices.

1.5.6 arrow-stringification (2016-05-27)

Bug Fixes

Features

  • $compile: support omitting required controller name if same as the local name (8965d57a, #14513)
  • $parse: Add support for ES6 object initializers (1c9b9e24)

Performance Improvements

1.4.11 relentless-syncomania (2016-05-27)

Bug Fixes

Performance Improvements

  • $compile: use createMap() for directive bindings to allow fast forEach (832b383c, #12529)

1.5.5 material-conspiration (2016-04-18)

Reverts

  • $compile: move setting of controller data to single location Reverted commit 21d148ae since it caused the Angular Material tabs directive to fail.

  • ngRoute: allow ngView to be included in an asynchronously loaded template Eagerly loading $route, could break tests, because it might request the root or default route template (something $httpBackend would know nothing about).

    It will be re-applied for v1.6.x, with a breaking change notice and possibly a way to disable the feature in tests.

    (8237482d, #1213, #6812, #14088)

Bug Fixes

  • $compile:
  • $injector: ensure functions with overridden toString() are annotated properly (d384834f, #14361)
  • ngAnimate:
    • remove event listeners only after all listeners have been called (79604f46, #14321)
    • fire callbacks when document is hidden (c7a92d2a, #14120)
    • fire callbacks in the correct order for certain skipped animations (90da3059)
  • ngClass: fix watching of an array expression containing an object (f975d8d4, #14405)
  • ngMock: fix collecting stack trace in inject() on IE10+, PhantomJS (e9c718a4, #13591, #13592, #13593)
  • ngOptions: set select value when model matches disabled option (832eba5f, #12756)
  • $http: pass event object to eventHandlers/uploadEventHandlers (25d4e5cc, #14436)

Features

Performance Improvements

1.5.4 graduated-sophistry (2016-04-14)

This was a partially published release that you should ignore.

1.5.3 diplohaplontic-meiosis (2016-03-25)

Bug Fixes

Features

1.5.2 differential-recovery (2016-03-18)

This release reverts a breaking change that accidentally made it into the 1.5.1 release. See fee7bac3 for more info.

Bug Fixes

  • ngAnimate.$animate: remove animation callbacks when the element is removed (ce7f4000)

1.5.1 equivocal-sophistication (2016-03-16)

Bug Fixes

Features

Performance Improvements

  • ngRepeat: avoid duplicate jqLite wrappers (632e15a3)
  • ngAnimate:
    • avoid jqLite/jQuery for upward DOM traversal (35251bd4)
    • avoid $.fn.data overhead with jQuery (15915e60)

1.4.10 benignant-oscillation (2016-03-16)

Bug Fixes

  • core: only call console.log when window.console exists (beb00e44, #14006, #14007, #14047)
  • $animateCss: cancel fallback timeout when animation ends normally (a60bbc12, #13787)
  • $compile:
    • allow directives to have decorators (77cdc37c)
    • properly denormalize templates when only one of the start/end symbols is different (2d44a681, #13848)
    • handle boolean attributes in @ bindings (2ffbfb0a, #13767, #13769)
  • $parse:
    • prevent assignment on constructor properties (f47e2180, #13417)
    • preserve expensive checks when running $eval inside an expression (96d62cc0)
    • copy inputs for expressions with expensive checks (0b7fff30)
  • $rootScope: set no context when calling helper functions for $watch (ab5c7698)
  • $route: allow preventing a route reload (4bc30314, #9824, #13894)
  • $routeProvider: properly handle optional eager path named groups (6a4403a1, #14011)
  • copy: add support for copying Blob objects (863a4232, #9669, #14064)
  • dateFilter: follow the CLDR on pattern escape sequences (f476060d, #12839)
  • dateFilter, input: fix Date parsing in IE/Edge when timezone offset contains : (571afd65, #13880, #13887)
  • input: re-validate when partially editing date-family inputs (02929f82, #12207, #13886)
  • select: handle corner case of adding options via a custom directive (df6e7315, #13874, #13878)
  • ngOptions: always set the 'selected' attribute for selected options (f87e8288, #14115)
  • ngAnimate: properly cancel previously running class-based animations (3b27dd37, #10156, #13822)
  • ngAnimateChildren: make it compatible with ngIf (dc158e7e, #13865, #13876)
  • ngMockE2E: pass responseType to $delegate when using passThrough (947cb4d1, #5415, #5783)

Features

  • $locale: Include original locale ID in $locale (e69f3550, #13390)
  • ngAnimate: provide ng-[event]-prepare class for structural animations (796f7ab4)

Performance Improvements

  • $compile: avoid needless overhead when wrapping text nodes (946d9ae9)
  • ngRepeat: avoid duplicate jqLite wrappers (d04c38c4)
  • ngAnimate:
    • avoid jqLite/jQuery for upward DOM traversal (ab95ba65)
    • avoid $.fn.data overhead with jQuery (86416bcb)

1.5.0 ennoblement-facilitation (2016-02-05)

Bug Fixes

Features

Breaking Changes

Upgrade to 1.5.1

This version of AngularJS is problematic due to a issue during its release. Please upgrade to version 1.5.2.

  • ngAria: due to d06431e5, Where appropriate, ngAria now applies ARIA to custom controls only, not native inputs. Because of this, support for aria-multiline on textareas has been removed.

1.5.0-rc.2 controller-requisition (2016-01-28)

Deprecation Warning

  • The ngTouch module's ngClick directive has been deprecated and disabled by default. See the breaking changes section for more information
  • The angular.lowercase and angular.uppercase functions have been deprecated and will be removed in version 1.7.0. It is recommended to use String.prototype.toLowerCase and String.prototype.toUpperCase functions instead.

Bug Fixes

Features

  • $compile:
    • allow required controllers to be bound to the directive controller (56c3666f, #6040, #5893, #13763)
    • allow directive definition property require to be an object (cd21216f, #8401, #13763)
    • call $onInit on directive controllers after all sibling controllers have been constructed (3ffdf380, #13763)
  • $locale: include original locale ID in $locale (63492a02, #13390)
  • $resource: add support for timeout in cancellable actions (d641901b, #13824)

Performance Improvements

  • $compile: avoid needless overhead when wrapping text nodes (92e4801d)
  • ngAnimate: speed up areAnimationsAllowed check (683bd92f)

Breaking Changes

The $sanitize service will now remove instances of the usemap attribute from any elements passed to it.

This attribute is used to reference another element by name or id. Since the name and id attributes are already blacklisted, a sanitized usemap attribute could only reference unsanitized content, which is a security risk.

The ngClick override directive from the ngTouch module is deprecated and disabled by default. This means that on touch-based devices, users might now experience a 300ms delay before a click event is fired.

If you rely on this directive, you can still enable it with the $touchProvider.ngClickOverrideEnabled()method:

angular.module('myApp').config(function($touchProvider) {
  $touchProvider.ngClickOverrideEnabled(true);
});

Going forward, we recommend using FastClick or perhaps one of the Angular 3rd party touch-related modules that provide similar functionality.

Also note that modern browsers already remove the 300ms delay under some circumstances:

  • Chrome and Firefox for Android remove the 300ms delay when the well-known <meta name="viewport" content="width=device-width"> is set
  • Internet Explorer removes the delay when touch-action css property is set to none or manipulation
  • Since iOs 8, Safari removes the delay on so-called "slow taps"

See this article by Telerik for more info on the topic.

Note that this change does not affect the ngSwipe directive.

1.4.9 implicit-superannuation (2016-01-21)

Bug Fixes

Minor Features

Performance Improvements

  • ngAnimate: speed up areAnimationsAllowed check (2d3303dd)

Breaking Changes

While we do not deem the following to be a real breaking change we are highlighting it here in the changelog to ensure that it does not surprise anyone.

Possible breaking change for users who updated their code to provide a timeout promise for a $resource request in version v1.4.8.

Up to v1.4.7 (included), using a promise as a timeout in $resource, would silently fail (i.e. have no effect).

In v1.4.8, using a promise as timeout would have the (buggy) behaviour described in https://github.com/angular/angular.js/pull/12657#issuecomment-152108887. (I.e. it will work as expected for the first time you resolve the promise and will cancel all subsequent requests after that - one has to re-create the resource class. This was not documented.)

With this change, using a promise as timeout in v1.4.9 onwards is not allowed. It will log a warning and ignore the timeout value.

If you need support for cancellable $resource actions, you should upgrade to version 1.5 or higher.

1.5.0-rc.1 quantum-fermentation (2016-01-15)

Features

Bug Fixes

Breaking Changes

  • $component: These breaking changes affect only applications updating from previous 1.5 beta / rc versions

    • Due to d91cf167, the default controllerAs value for components is now $ctrl (previously the name of the component was used). To migrate, either set controllerAs to the component name, or change the property name in your templates to $ctrl

    • Due to 25bc5318, it is no longer possible to set the restrict option on directives created via the module.component() helper. All components are now element directives (restrict: 'E'). If you need a directive that is not an element then you must use the module.directive() helper instead.

    • Due to f31c5a39, components are now always created with scope: {} (isolate scope). Previously, it was also possible to create components with scope: true or scope: false. If your components rely on this scope configuration, you will have to create a regular directive instead.

    • Due to 6a47c0d7, the transclude property is now false by default (previously true). If you created components that expected transclusion then you must change your code to specify transclude: true.

  • linky: due to 98c2db7f,

Before this change, the filter assumed that the input (if not undefined/null) was of type 'string' and that certain methods (such as .match()) would be available on it. Passing a non-string value would most likely result in a not-very-useful error being thrown (trying to call a method that does not exist) or in unexpected behavior (if the input happened to have the assumed methods).

After this change, a proper (informative) error will be thrown. If you want to pass non-string values through linky, you need to explicitly convert them to strings first. Since input values could be initialized asynchronously, undefined or null will still be returned unchanged (without throwing an error).

1.5.0-rc.0 oblong-panoptikum (2015-12-09)

This is the first Release Candidate for AngularJS 1.5.0. Please try upgrading your applications and report any regressions or other issues you find as soon as possible.

Features

Bug Fixes

Breaking Changes

This is only a breaking change to a feature that was added in beta 2. If you have not started using multi-slot transclusion then this will not affect you.

The keys and values for the transclude map of the directive definition have been swapped around to be more consistent with the other maps, such as scope and bindToController.

Now the key is the slot name and the value is a normalized element selector.

Using a promise as timeout is no longer supported and will log a warning. It never worked the way it was supposed to anyway.

Before:

var deferred = $q.defer();
var User = $resource('/api/user/:id', {id: '@id'}, {
  get: {method: 'GET', timeout: deferred.promise}
});

var user = User.get({id: 1});   // sends a request
deferred.resolve();             // aborts the request

// Now, we need to re-define `User` passing a new promise as `timeout`
// or else all subsequent requests from `someAction` will be aborted
User = $resource(...);
user = User.get({id: 2});

After:

var User = $resource('/api/user/:id', {id: '@id'}, {
  get: {method: 'GET', cancellable: true}
});

var user = User.get({id: 1});   // sends a request
user.$cancelRequest();      // aborts the request

user = User.get({id: 2});

The $sanitize service will now remove instances of the <use> tag from the content passed to it.

This element is used to import external SVG resources, which is a security risk as the $sanitize service does not have access to the resource in order to sanitize it.

A new property to access route resolves is now available on the scope of the route. The default name for this property is $resolve. If your scope already contains a property with this name then it will be hidden or overwritten.

In this case, you should choose a custom name for this property, that does not collide with other properties on the scope, by specifying the resolveAs property on the route.

A new property to access all the locals for an expression is now available on the scope. This property is $locals.

  • If scope.$locals already exists, the way to reference this property is now this.$locals.
  • If the locals themselves include a property $locals then the way to reference that is now $locals.$locals.

1.4.8 ice-manipulation (2015-11-19)

Bug Fixes

Performance Improvements

  • $compile: use static jquery data method to avoid creating new instances (55ad192e)
  • copy:
    • avoid regex in isTypedArray (19fab4a1)
    • only validate/clear if the user specifies a destination (d1293540, #12068)
  • merge: remove unnecessary wrapping of jqLite element (ce6a96b0, #13236)

1.5.0-beta.2 effective-delegation (2015-11-17)

Bug Fixes

Features

Performance Improvements

  • $compile: use static jquery data method to avoid creating new instances (9b90c32f)
  • $interpolate: provide a simplified result for constant expressions (cf83b4f4)
  • copy:
    • avoid regex in isTypedArray (c8768d12)
    • only validate/clear if the user specifies a destination (33c67ce7, #12068)
  • merge: remove unnecessary wrapping of jqLite element (4daafd3d, #13236)

Breaking Changes

ngMessage is now compiled with a priority of 1, which means directives on the same element as ngMessage with a priority lower than 1 will be applied when ngMessage calls the $transclude function. Previously, they were applied during the initial compile phase and were passed the comment element created by the transclusion of ngMessage. To restore this behavior, custom directives need to have their priority increased to at least "1".

Previously, an non array-like input would pass through the orderBy filter unchanged. Now, an error is thrown. This can be worked around by converting an object to an array, either manually or using a filter such as https://github.com/petebacondarwin/angular-toArrayFilter. (null and undefined still pass through without an error, in order to support asynchronous loading of resources.)

1.5.0-beta.1 dense-dispersion (2015-09-29)

Bug Fixes

Features

Performance Improvements

  • $compile: Lazily compile the transclude function (652b83eb)

Breaking Changes

  • $sanitize: due to 181fc567, The svg support in is now an opt-in option

Applications that depend on this option can use to turn the option back on, but while doing so, please read the warning provided in the documentation for information on preventing click-hijacking attacks when this option is turned on.

If your data contains falsy values ('', 0, false and null) for option groups, then these options will now be placed into option groups. Previously all of these falsy values were treated as the option not being a member of a group.

Only option groups that are undefined will result in the option being put in no group. If you have data that contains falsy values that should not be used as groups then you must filter the values before passing them to ngOptions converting falsy values to undefined.

ngOptions will now throw if ngModel is not present on the select element. Previously, having no ngModel let ngOptions silently fail, which could lead to hard to debug errors. The change should therefore not affect any applications, as it simply makes the requirement more strict and alerts the developer explicitly.

1.4.7 dark-luminescence (2015-09-29)

Bug Fixes

  • $compile: use createMap() for $$observe listeners when initialized from attr interpolation (5a98e806, #10446)
  • $parse:
    • block assigning to fields of a constructor (a7f3761e, #12860)
    • do not convert to string computed properties multiple times (698af191)
  • filters: ensure formatNumber observes i18n decimal separators (4994acd2, #10342, #12850)
  • jqLite: properly handle dash-delimited node names in jqLiteBuildFragment (cdd1227a, #10617, #12759)
  • ngAnimate:
    • ensure anchoring uses body as a container when needed (9d3704ca, #12872)
    • callback detection should only use RAF when necessary (fa8c399f)
  • ngMessages: prevent race condition with ngAnimate (7295c60f, #12856, #12903)
  • ngOptions:

Features

1.3.20 shallow-translucence (2015-09-29)

Bug Fixes

  • $parse: do not convert to string computed properties multiple times (d434f3db)

1.2.29 ultimate-deprecation (2015-09-29)

Bug Fixes

1.5.0-beta.0 intialization-processation (2015-09-17)

Bug Fixes

  • jqLite:: properly handle dash-delimited node names in jqLiteBuildFragment (cdd1227a3, #10617)

1.4.6 multiplicative-elevation (2015-09-17)

Bug Fixes

Performance Improvements

  • Angular: only create new collection in getBlockNodes if the block has changed (0202663e, #9899)

1.3.19 glutinous-shriek (2015-09-15)

Bug Fixes

  • $http: propagate status -1 for timed out requests (f13055a0, #4491, #8756)
  • $location: don't crash if navigating outside the app base (623ce1ad, #11667)
  • $parse: throw error when accessing a restricted property indirectly (ec98c94c, #12833)
  • ngModel: validate pattern against the viewValue (274e9353, #12344)

Features

  • ngAnimate: introduce $animate.flush for unit testing (f98e0384)

Possible Breaking Changes

The ngPattern and pattern directives will validate the regex against the viewValue of ngModel, i.e. the value of the model before the $parsers are applied. Previously, the modelValue (the result of the $parsers) was validated.

This fixes issues where input[date] and input[number] cannot be validated because the viewValue string is parsed into Date and Number respectively (starting with Angular 1.3). It also brings the directives in line with HTML5 constraint validation, which validates against the input value.

This change is unlikely to cause applications to fail, because even in Angular 1.2, the value that was validated by pattern could have been manipulated by the $parsers, as all validation was done inside this pipeline.

If you rely on the pattern being validated against the modelValue, you must create your own validator directive that overwrites the built-in pattern validator:

.directive('patternModelOverwrite', function patternModelOverwriteDirective() {
  return {
    restrict: 'A',
    require: '?ngModel',
    priority: 1,
    compile: function() {
      var regexp, patternExp;

      return {
        pre: function(scope, elm, attr, ctrl) {
          if (!ctrl) return;

          attr.$observe('pattern', function(regex) {
            /**
             * The built-in directive will call our overwritten validator
             * (see below). We just need to update the regex.
             * The preLink fn guarantees our observer is called first.
             */
            if (isString(regex) && regex.length > 0) {
              regex = new RegExp('^' + regex + '$');
            }

            if (regex && !regex.test) {
              //The built-in validator will throw at this point
              return;
            }

            regexp = regex || undefined;
          });

        },
        post: function(scope, elm, attr, ctrl) {
          if (!ctrl) return;

          regexp, patternExp = attr.ngPattern || attr.pattern;

          //The postLink fn guarantees we overwrite the built-in pattern validator
          ctrl.$validators.pattern = function(value) {
            return ctrl.$isEmpty(value) ||
              isUndefined(regexp) ||
              regexp.test(value);
          };
        }
      };
    }
  };
});

1.4.5 permanent-internship (2015-08-28)

Bug Fixes

Breaking Changes

The ngPattern and pattern directives will validate the regex against the viewValue of ngModel, i.e. the value of the model before the $parsers are applied. Previously, the modelValue (the result of the $parsers) was validated.

This fixes issues where input[date] and input[number] cannot be validated because the viewValue string is parsed into Date and Number respectively (starting with Angular 1.3). It also brings the directives in line with HTML5 constraint validation, which validates against the input value.

This change is unlikely to cause applications to fail, because even in Angular 1.2, the value that was validated by pattern could have been manipulated by the $parsers, as all validation was done inside this pipeline.

If you rely on the pattern being validated against the modelValue, you must create your own validator directive that overwrites the built-in pattern validator:

.directive('patternModelOverwrite', function patternModelOverwriteDirective() {
  return {
    restrict: 'A',
    require: '?ngModel',
    priority: 1,
    compile: function() {
      var regexp, patternExp;

      return {
        pre: function(scope, elm, attr, ctrl) {
          if (!ctrl) return;

          attr.$observe('pattern', function(regex) {
            /**
             * The built-in directive will call our overwritten validator
             * (see below). We just need to update the regex.
             * The preLink fn guarantees our observer is called first.
             */
            if (isString(regex) && regex.length > 0) {
              regex = new RegExp('^' + regex + '$');
            }

            if (regex && !regex.test) {
              //The built-in validator will throw at this point
              return;
            }

            regexp = regex || undefined;
          });

        },
        post: function(scope, elm, attr, ctrl) {
          if (!ctrl) return;

          regexp, patternExp = attr.ngPattern || attr.pattern;

          //The postLink fn guarantees we overwrite the built-in pattern validator
          ctrl.$validators.pattern = function(value) {
            return ctrl.$isEmpty(value) ||
              isUndefined(regexp) ||
              regexp.test(value);
          };
        }
      };
    }
  };
});

1.3.18 collective-penmanship (2015-08-18)

Bug Fixes

1.4.4 pylon-requirement (2015-08-13)

Bug Fixes

Features

Performance Improvements

Breaking Changes

  • ngAnimate: due to 32d3cbb3, CSS classes added/removed by ngAnimate are now applied synchronously once the first digest has passed.

The previous behavior involved ngAnimate having to wait for one requestAnimationFrame before CSS classes were added/removed. The CSS classes are now applied directly after the first digest that is triggered after $animate.addClass, $animate.removeClass or $animate.setClass is called. If any of your code relies on waiting for one frame before checking for CSS classes on the element then please change this behavior. If a parent class-based animation, however, is run through a JavaScript animation which triggers an animation for beforeAddClass and/or beforeRemoveClass then the CSS classes will not be applied in time for the children (and the parent class-based animation will not be cancelled by any child animations).

  • $q due to 6838c979, When writing tests, there is no need to call $timeout.flush() to resolve a call to $q.when with a value.

The previous behavior involved creating an extra promise that needed to be resolved. This is no longer needed when $q.when is called with a value. In the case that the test is not aware if $q.when is called with a value or another promise, it is possible to replace $timeout.flush(); with $timeout.flush(0);.

describe('$q.when', function() {
  it('should not need a call to $timeout.flush() to resolve already resolved promises',
      inject(function($q, $timeout) {
    $q.when('foo');
    // In Angular 1.4.3 a call to `$timeout.flush();` was needed
    $timeout.verifyNoPendingTasks();
  }));

  it('should accept $timeout.flush(0) when not sure if $q.when was called with a value or a promise',
      inject(function($q, $timeout) {
    $q.when('foo');
    $timeout.flush(0);
    $timeout.verifyNoPendingTasks();
  }));

  it('should need a call to $timeout.flush() to resolve $q.when when called with a promise',
        inject(function($q, $timeout) {
    $q.when($q.when('foo'));
    $timeout.flush();
    $timeout.verifyNoPendingTasks();
  }));
});
  • form: Due to 94533e57, the name attribute of form elements can now only contain characters that can be evaluated as part of an Angular expression. This is because Angular uses the value of name as an assignable expression to set the form on the $scope. For example, name="myForm" assigns the form to $scope.myForm and name="myObj.myForm" assigns it to $scope.myObj.myForm.

    Previously, it was possible to also use names such name="my:name", because Angular used a special setter function for the form name. Now the general, more robust $parse setter is used.

    The easiest way to migrate your code is therefore to remove all special characters from the name attribute.

    If you need to keep the special characters, you can use the following directive, which will replace the name with a value that can be evaluated as an expression in the compile function, and then re-set the original name in the postLink function. This ensures that (1), the form is published on the scope, and (2), the form has the original name, which might be important if you are doing server-side form submission.

    angular.module('myApp').directive('form', function() {
      return {
        restrict: 'E',
        priority: 1000,
        compile: function(element, attrs) {
          var unsupportedCharacter = ':'; // change accordingly
          var originalName = attrs.name;
          if (attrs.name && attrs.name.indexOf(unsupportedCharacter) > 0) {
            attrs.$set('name', 'this["' + originalName + '"]');
          }
    
          return postLinkFunction(scope, element) {
            // Don't trigger $observers
            element.setAttribute('name', originalName);
          }
        }
      };
    });

1.4.3 foam-acceleration (2015-07-15)

Bug Fixes

  • $animateCss: ensure animations execute if only a keyframeStyle is provided (97d79eec, #12124, #12340)
  • loader: define isFunction (9ea52d81)
  • ngAnimate: ensure that orphaned elements do not throw errors when animated (e4aeae0c, #11975, #12338)

1.4.2 nebular-readjustment (2015-07-06)

Bug Fixes

Features

Breaking Changes

  • ngInclude: due to 3c6e8ce044446735eb2e70d0061db8c6db050289, the src attribute of ngInclude no longer accepts an expression that returns the result of $sce.trustAsResourceUrl. This will now cause an infinite digest:

Before:

<div ng-include="findTemplate('https://example.com/myTemplate.html')"></div>
$scope.findTemplate = function(templateName) {
  return $sce.trustAsResourceUrl(templateName);
};

To migrate, either cache the result of trustAsResourceUrl(), or put the template url in the resource whitelist in the config() function:

After:

var templateCache = {};
$scope.findTemplate = function(templateName) {
  if (!templateCache[templateName]) {
    templateCache[templateName] = $sce.trustAsResourceUrl(templateName);
  }

  return  templateCache[templateName];
};

// Alternatively, use `$sceDelegateProvider.resourceUrlWhitelist()`:

angular.module('myApp', []).config(function($sceDelegateProvider) {
  $sceDelegateProvider.resourceUrlWhitelist(['self', 'https://example.com/**'])
});

1.3.17 tsktskskly-euouae (2015-07-06)

Bug Fixes

1.4.1 hyperionic-illumination (2015-06-16)

Bug Fixes

Features

Performance Improvements

  • $compile: avoid jquery data calls when there is no data (9efb0d5e)

1.3.16 cookie-oatmealification (2015-06-05)

Bug Fixes

  • $compile: throw error on invalid directive name (634e4671, #11281, #11109)
  • $cookies: update $cookies to prevent duplicate cookie writes and play nice with external code (706a93ab, #11490, #11515)
  • $http: throw error if success and error methods do not receive a function (731e1f65, #11330, #11333)
  • core: ensure that multiple requests to requestAnimationFrame are buffered (0adc0364, #11791)
  • filterFilter: fix matching against null/undefined (9dd0fe35, #11573, #11617)
  • jqLite:
    • check for "length" in obj in isArrayLike to prevent iOS8 JIT bug from surfacing (647f3f55, #11508)
    • attr should ignore comment, text and attribute nodes (181e5ebc)
  • ngAnimate:
    • ensure that minified repaint code isn't removed (d5c99ea4, #9936)
  • ngAria: handle elements with role="checkbox/menuitemcheckbox" (1c282af5, #11317, #11321)
  • ngModel: allow setting model to NaN when asyncValidator is present (b64519fe, #11315, #11411)
  • ngTouch:
  • select: prevent unknown option being added to select when bound to null property (9e3f82bb, #11872, #11875)

Features

1.4.0 jaracimrman-existence (2015-05-26)

Bug Fixes

  • $animate:
  • $animateCss: ensure that custom durations do not confuse the gcs cache (e0e1b520, #11723, #11852)
  • $http: do not modify the config object passed into $http short methods (f7a4b481)
  • ngAnimate:
    • close follow-up class-based animations when the same class is added/removed when removed/added (db246eb7, #11717)
    • ensure nested class-based animations are spaced out with a RAF (213c2a70, #11812)
    • class-based animations must not set addClass/removeClass CSS classes on the element (3a3db690, #11810)
    • ensure that repeated structural calls during pre-digest function (2327f5a0, #11867)
    • ensure that cancelled class-based animations are properly cleaned up (718ff844, #11652)
    • throw an error if a callback is passed to animate methods (9bb4d6cc, #11826, #11713)
    • ensure anchored animations remove the leave element at correct time (64c66d0e, #11850)
  • select: prevent unknown option being added to select when bound to null property (4090491c, #11872, #11875)

Features

1.4.0-rc.2 rocket-zambonimation (2015-05-12)

Bug Fixes

  • $compile: ensure directive names have no leading or trailing whitespace (bab474aa, #11397, #11772)
  • $httpParamSerializerJQLike: follow jQuery logic for nested params (2420a0a7, #11551, #11635)
  • jqLite: check for "length" in obj in isArrayLike to prevent iOS8 JIT bug from surfacing (426a5ac0, #11508)
  • ngAnimate:
    • ensure that multiple requests to requestAnimationFrame are buffered (db20b830, #11791)
    • ensure that an object is always returned even when no animation is set to run (d5683d21)
    • force use of ng-anchor instead of a suffixed -anchor CSS class when triggering anchor animations (df24410c)
    • rename ng-animate-anchor to ng-anchor (e6d053de)
    • ensure that shared CSS classes between anchor nodes are retained (e0014002, #11681)
    • prohibit usage of the ng-animate class with classNameFilter (1002b80a, #11431, #11807)
    • ensure that the temporary CSS classes are applied before detection (f7e9ff1a, #11769, #11804)
    • ensure that all jqLite elements are deconstructed properly (64d05180, #11658)
    • ensure animations are not attempted on text nodes (2aacc2d6, #11703)
    • ensure JS animations recognize $animateCss directly (0681a540)
  • ngClass: add/remove classes which are properties of Object.prototype (f7b99970, #11813, #11814)
  • ngOptions:
  • ngTouch:
    • check undefined tagName for SVG event target (74eb17d7)
    • don't prevent click event after a touchmove (95521876, #10985)

Features

  • $resource: include request context in error message (266bc652, #11363)

Breaking Changes

  • ngAnimate - $animateCss: due to d5683d21, The $animateCss service will now always return an object even if the animation is not set to run. If your code is using $animateCss then please consider the following code change:
// before
var animator = $animateCss(element, { ... });
if (!animator) {
  continueApp();
  return;
}
var runner = animator.start();
runner.done(continueApp);
runner.then(continueApp);

// now
var animator = $animateCss(element, { ... });
var runner = animator.start();
runner.done(continueApp);
runner.then(continueApp);
  • due to df24410c, Prior to this fix there were to ways to apply CSS animation code to an anchor animation. With this fix, the suffixed CSS -anchor classes are now not used anymore for CSS anchor animations.

Instead just use the ng-anchor CSS class like so:

<div class="container-animation" ng-if="on">
   <div ng-animate-ref="1" class="my-anchor-element"></div>
</div>

<div class="container-animation" ng-if="!on">
   <div ng-animate-ref="1" class="my-anchor-element"></div>
</div>

before:

/* before (notice the container-animation CSS class) */
.container-animation-anchor {
  transition:0.5s linear all;
}

now:

/* now (just use `ng-anchor` on a class that both the
   elements that contain `ng-animate-ref` share) */
.my-anchor-element.ng-anchor {
  transition:0.5s linear all;
}
  • due to e6d053de, if your CSS code made use of the ng-animate-anchor CSS class for referencing the anchored animation element then your code must now use ng-anchor instead.

  • due to 1002b80a, partially or fully using a regex value containing ng-animate as a token is not allowed anymore. Doing so will trigger a minErr exception to be thrown.

So don't do this:

// only animate elements that contain the `ng-animate` CSS class
$animateProvider.classNameFilter(/ng-animate/);

// or partially contain it
$animateProvider.classNameFilter(/some-class ng-animate another-class/);

but this is OK:

$animateProvider.classNameFilter(/ng-animate-special/);

Although it is unlikely that anyone is using it in this way, this change does change the behavior of ngOptions in the following case:

  • you are iterating over an array-like object, using the array form of the ngOptions syntax (item.label for item in items) and that object contains non-numeric property keys.

In this case these properties with non-numeric keys will be ignored.

** Here array-like is defined by the result of a call to this internal function: https://github.com/angular/angular.js/blob/v1.4.0-rc.1/src/Angular.js#L198-L211 **

To get the desired behavior you need to iterate using the object form of the ngOptions syntax (value.label for (key, value) in items)`).

v1.4.0-rc.1 sartorial-chronography (2015-04-24)

Bug Fixes

  • $animate:
    • ensure that from styles are applied for class-based animations (8f819d2c)
    • make sure the JS animation lookup is an object lookup (103a39ca, #11619)
  • $animateCss: ensure that rAF waiting loop doesn't ignore pending items during a flush (90e424b2)
  • $http: stop coercing falsy HTTP request bodies to null / empty body (e04a887c, #11552, #11593)
  • ngAnimate:
    • close parent animations only when there are classes to resolve (1459be17)
    • ensure ngClass-based classes are always resolved for CSS-enabled animations (89f081e4)
    • do not abort animation if only ng-anchor-in is used (3333a5c3)
    • ensure that a filtered-out leave animation always runs its DOM operation (6dd64ab5, #11555)
    • ensure that animations work when the app is bootstrapped on the document node (bee14ed1, #11574)
    • ensure SVG classes are properly removed (fa0bbded)
  • ngAria: change accessibility keypress event to use event.which if it is provided (249f9b81, #11340)
  • ngMessageFormat:
  • select: allow empty option to be added dynamically by ng-repeat (abf59c28, #11470, #11512)

Features

  • $animate: provide support for animations on elements outside of $rootElement (e41faaa2)

v1.4.0-rc.0 smooth-unwinding (2015-04-10)

Bug Fixes

Features

Performance Improvements

Breaking Changes

  • $animate: due to c8700f04, JavaScript and CSS animations can no longer be run in parallel. With earlier versions of ngAnimate, both CSS and JS animations would be run together when multiple animations were detected. This feature has now been removed, however, the same effect, with even more possibilities, can be achieved by injecting $animateCss into a JavaScript-defined animation and creating custom CSS-based animations from there. Read the ngAnimate docs for more info.

  • $animate: due to c8700f04, The function params for $animate.enabled() when an element is used are now flipped. This fix allows the function to act as a getter when a single element param is provided.

// < 1.4
$animate.enabled(false, element);

// 1.4+
$animate.enabled(element, false);
  • $animate: due to c8700f04, In addition to disabling the children of the element, $animate.enabled(element, false) will now also disable animations on the element itself.

  • $animate: due to c8700f04, Animation-related callbacks are now fired on $animate.on instead of directly being on the element.

// < 1.4
element.on('$animate:before', function(e, data) {
  if (data.event === 'enter') { ... }
});
element.off('$animate:before', fn);

// 1.4+
$animate.on(element, 'enter', function(data) {
  //...
});
$animate.off(element, 'enter', fn);
  • $animate: due to c8700f04, There is no need to call $scope.$apply or $scope.$digest inside of an animation promise callback anymore since the promise is resolved within a digest automatically (but a digest is not run unless the promise is chained).
// < 1.4
$animate.enter(element).then(function() {
  $scope.$apply(function() {
    $scope.explode = true;
  });
});

// 1.4+
$animate.enter(element).then(function() {
  $scope.explode = true;
});
  • $animate: due to c8700f04, When an enter, leave or move animation is triggered then it will always end any pending or active parent class based animations (animations triggered via ngClass) in order to ensure that any CSS styles are resolved in time.

1.4.0-beta.6 cookie-liberation (2015-03-17)

Bug Fixes

  • $animate: call applyStyles from options on leave (4374f892, #10068)
  • $browser: don't crash if history.state access causes error in IE (3b8163b7, #10367, #10369)
  • $sanitize: disallow unsafe svg animation tags (67688d5c, #11290)
  • Angular: properly compare RegExp with other objects for equality (f22e1fc9, #11204, #11205)
  • date filter: display localized era for G format codes (2b4dfa9e, #10503, #11266)
  • filterFilter:
  • form: allow dynamic form names which initially evaluate to blank (410f7c68)
  • jqLite: attr should ignore comment, text and attribute nodes (bb5bf7f8)
  • ng/$locale: add ERA info in generic locale (4acb0af2)
  • ngJq: don't rely on existence of jqlite (342e5f3c, #11044)
  • ngMessages: ensure that multi-level transclusion works with ngMessagesInclude (d7ec5f39, #11196)
  • ngOptions: fix model<->option interaction when using track by (6a03ca27, #10869, #10893)
  • rootScope: prevent memory leak when destroying scopes (fb7db4a0, #11173, #11169)

Features

Breaking Changes

$cookies no longer exposes properties that represent the current browser cookie values. Now you must explicitly the methods described above to access the cookie values. This also means that you can no longer watch the $cookies properties for changes to the browser's cookies.

This feature is generally only needed if a 3rd party library was programmatically changing the cookies at runtime. If you rely on this then you must either write code that can react to the 3rd party library making the changes to cookies or implement your own polling mechanism.

1.3.15 locality-filtration (2015-03-17)

Bug Fixes

Features

1.4.0-beta.5 karmic-stabilization (2015-02-24)

Bug Fixes

Features

  • CommonJS: - angular modules are now packaged for npm with helpful exports

  • limitTo: extend the filter to take a beginning index argument (aaae3cc4, #5355, #10899)

  • ngMessages: provide support for dynamic message resolution (c9a4421f, #10036, #9338)
  • ngOptions: add support for disabling an option (da9eac86, #638, #11017)

Performance Improvements

  • $compile:
    • replace forEach(controller) with plain loops (5b522867, #11084)
    • avoid .data when fetching required controllers (fa0aa839)
  • ngOptions: only watch labels if a display expression is specified (51faaffd)

Breaking Changes

The ngMessagesInclude attribute is now its own directive and that must be placed as a child element within the element with the ngMessages directive. (Keep in mind that the former behavior of the ngMessageInclude attribute was that all included ngMessage template code was placed at the bottom of the element containing the ngMessages directive; therefore to make this behave in the same way, place the element containing the ngMessagesInclude directive at the end of the container containing the ngMessages directive).

<!-- AngularJS 1.3.x -->
<div ng-messages="model.$error" ng-messages-include="remote.html">
  <div ng-message="required">Your message is required</div>
</div>

<!-- AngularJS 1.4.x -->
<div ng-messages="model.$error">
  <div ng-message="required">Your message is required</div>
  <div ng-messages-include="remote.html"></div>
</div>

it is no longer possible to use interpolation inside the ngMessages attribute expression. This technique is generally not recommended, and can easily break when a directive implementation changes. In cases where a simple expression is not possible, you can delegate accessing the object to a function:

<div ng-messages="ctrl.form['field_{{$index}}'].$error">...</div>

would become

<div ng-messages="ctrl.getMessages($index)">...</div>

where ctrl.getMessages()

ctrl.getMessages = function($index) {
  return ctrl.form['field_' + $index].$error;
}

transformRequest functions can no longer modify request headers.

Before this commit transformRequest could modify request headers, ex.:

function requestTransform(data, headers) {
    headers = angular.extend(headers(), {
      'X-MY_HEADER': 'abcd'
    });
  }
  return angular.toJson(data);
}

This behavior was unintended and undocumented, so the change should affect very few applications. If one needs to dynamically add / remove headers it should be done in a header function, for example:

$http.get(url, {
  headers: {
    'X-MY_HEADER': function(config) {
      return 'abcd'; //you've got access to a request config object to specify header value dynamically
    }
  }
})

1.3.14 instantaneous-browserification (2015-02-24)

Features

  • CommonJS: - angular modules are now packaged for npm with helpful exports

Bug Fixes

1.4.0-beta.4 overlyexplosive-poprocks (2015-02-09)

Bug Fixes

Features

  • ng-jq: adds the ability to force jqLite or a specific jQuery version (09ee82d8)

1.3.13 meticulous-riffleshuffle (2015-02-09)

Bug Fixes

1.4.0-beta.3 substance-mimicry (2015-02-02)

Bug Fixes

  • $compile:
    • do not initialize optional '&' binding if attribute not specified (6a38dbfd, #6404, #9216)
    • respect return value from controller constructor (62d514b0)
  • $controller: throw better error when controller expression is bad (dda65e99, #10875, #10910)
  • $parse:
    • handle null targets at assign (2e5a7e52)
    • remove references to last arguments to a fn call (e61eae1b, #10894)
  • a: don't reload if there is only a name attribute (d729fcf0, #6273, #10880)
  • angular.copy: support copying TypedArrays (aa0f6449, #10745)
  • filter: format timezone correctly in the case that UTC timezone is used (8c469191, #9359)
  • ngRoute: don't duplicate optional params into query (27bf2ce4, #10689)
  • ngScenario: allow ngScenario to handle lazy-loaded and manually bootstrapped applications (c69caa7b, #10723)
  • validators: maxlength should use viewValue for $isEmpty (bfcf9946, #10898)

Features

  • $compile: allow using bindToController as object, support both new/isolate scopes (35498d70, #10420, #10467)
  • filter: support conversion to timezone other than UTC (c6d8512a, #10858)
  • ngMocks: cleanup $inject annotations after each test (0baa17a3)

Performance Improvements

  • $scope: Add a property $$watchersCount to scope (c1500ea7)
  • $parse new and more performant parser (0d42426)

Breaking Changes

  • $compile: due to 6a38dbfd, Previously, '&' expressions would always set up a function in the isolate scope. Now, if the binding is marked as optional and the attribute is not specified, no function will be added to the isolate scope.

1.3.12 outlandish-knitting (2015-02-02)

Bug Fixes

  • $controller: throw better error when controller expression is bad (632b2ddd, #10875, #10910)
  • $parse: remove references to last arguments to a fn call (7caad220, #10894)
  • ngRoute: don't duplicate optional params into query (f41ca4a5, #10689)
  • ngScenario: Allow ngScenario to handle lazy-loaded and manually bootstrapped applications (0bcd0872, #10723)
  • validators: maxlength should use viewValue for $isEmpty (abd8e2a9, #10898)

Features

  • ngMocks: cleanup $inject annotations after each test (6ec59460)

1.4.0-beta.2 holographic-rooster (2015-01-26)

Bug Fixes

Breaking Changes

Closes #9992 Closes #10352

1.3.11 spiffy-manatee (2015-01-26)

Bug Fixes

  • $location: don't rewrite when link is shift-clicked (939ca37c, #9904, #9906)
  • htmlAnchorDirective:
    • remove "element !== target element" check (779e3f6b, #10866)
    • don't add event listener if replaced, ignore event if target is different element (837a0775, #4262, #10849)

1.4.0-beta.1 trepidatious-salamander (2015-01-20)

Bug Fixes

Features

Breaking Changes

Previously, the order of items when using ngRepeat to iterate over object properties was guaranteed to be consistent by sorting the keys into alphabetic order.

Now, the order of the items is browser dependent based on the order returned from iterating over the object using the for key in obj syntax.

It seems that browsers generally follow the strategy of providing keys in the order in which they were defined, although there are exceptions when keys are deleted and reinstated. See https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/delete#Cross-browser_issues

The best approach is to convert Objects into Arrays by a filter such as https://github.com/petebacondarwin/angular-toArrayFilter or some other mechanism, and then sort them manually in the order you need.

Closes #6210 Closes #10538

1.3.10 heliotropic-sundial (2015-01-20)

Bug Fixes

1.4.0-beta.0 photonic-umbrakinesis (2015-01-13)

Bug Fixes

Features

Performance Improvements

Breaking Changes

  • limitTo: due to a3c3bf33, limitTo changed behavior when limit value is invalid. Instead of returning empty object/array it returns unchanged input.

  • ngOptions: due to 7fda214c,

When using ngOptions: the directive applies a surrogate key as the value of the <option> element. This commit changes the actual string used as the surrogate key. We now store a string that is computed by calling hashKey on the item in the options collection; previously it was the index or key of the item in the collection.

(This is in keeping with the way that the unknown option value is represented in the select directive.)

Before you might have seen:

<select ng-model="x" ng-option="i in items">
  <option value="1">a</option>
  <option value="2">b</option>
  <option value="3">c</option>
  <option value="4">d</option>
</select>

Now it will be something like:

<select ng-model="x" ng-option="i in items">
  <option value="string:a">a</option>
  <option value="string:b">b</option>
  <option value="string:c">c</option>
  <option value="string:d">d</option>
</select>

If your application code relied on this value, which it shouldn't, then you will need to modify your application to accommodate this. You may find that you can use the track by feature of ngOptions as this provides the ability to specify the key that is stored.

When iterating over an object's properties using the (key, value) in obj syntax the order of the elements used to be sorted alphabetically. This was an artificial attempt to create a deterministic ordering since browsers don't guarantee the order. But in practice this is not what people want and so this change iterates over properties in the order they are returned by Object.keys(obj), which is almost always the order in which the properties were defined.

setting the ngOptions attribute expression after the element is compiled, will no longer trigger the ngOptions behavior. This worked previously because the ngOptions logic was part of the select directive, while it is now implemented in the ngOptions directive itself.

the select directive will now use strict comparison of the ngModel scope value against option values to determine which option is selected. This means Number scope values will not be matched against numeric option strings. In Angular 1.3.x, setting scope.x = 200 would select the option with the value 200 in the following select:

<select ng-model="x">
  <option value="100">100</option>
  <option value="200">200</option>
</select>

In Angular 1.4.x, the 'unknown option' will be selected. To remedy this, you can simply initialize the model as a string: scope.x = '200', or if you want to keep the model as a Number, you can do the conversion via $formatters and $parsers on ngModel:

ngModelCtrl.$parsers.push(function(value) {
  return parseInt(value, 10); // Convert option value to number
});

ngModelCtrl.$formatters.push(function(value) {
  return value.toString(); // Convert scope value to string
});

1.3.9 multidimensional-awareness (2015-01-13)

Bug Fixes

  • $parse: allow use of locals in assignments (86900814)
  • filterFilter: use isArray() to determine array type (d4b60ada, #10621)

Features

Performance Improvements

1.3.8 prophetic-narwhal (2014-12-19)

Bug Fixes

Performance Improvements

  • limitTo: replace for loop with slice (cd77c089)

1.3.7 leaky-obstruction (2014-12-15)

Bug Fixes

  • $compile: use createMap() for $$observe listeners when initialized from attr interpolation (8e28bb4c)
  • $http:
  • $parse: a chain of field accessors should use a single getterFn (c90ad968)
  • ngRepeat: allow extra whitespaces in (key,value) part of micro-syntax (ef640cbc, #6827, #6833)
  • orderBy: do not try to call valueOf/toString on null (a097aa95, #10385, #10386)

Features

Performance Improvements

  • $compile: only re-$interpolate attribute values at link time if changed since compile (9ae0c01c)

Breaking Changes

Previously, if either value being compared in the orderBy comparator was null or undefined, the order would, incorrectly, not change. Now, this order behaves more like Array.prototype.sort, which by default pushes null behind objects, due to n occurring after [ (the first characters of their stringified forms) in ASCII / Unicode. If toString is customized, or does not exist, the behavior is undefined.

1.2.28 finnish-disembarkation (2014-12-15)

Bug Fixes

1.3.6 robofunky-danceblaster (2014-12-08)

Bug Fixes

  • $browser: prevent infinite digests when clearing the hash of a url (10ac5948, #9629, #9635, #10228, #10308)
  • $http: preserve config object when resolving from cache (facfec98, #9004, #9030)
  • $location:
  • $parse:
    • fix operators associativity (ed1243ff)
    • follow JavaScript context for unbound functions (429938da)
  • filterFilter:
    • don't match primitive sub-expressions against any prop (a75537d4)
    • ignore function properties and account for inherited properties (5ced914c, #9984)
    • correctly handle deep expression objects (f7cf8460, #7323, #9698, #9757)
  • inputs: ignoring input events in IE caused by placeholder changes or focus/blur on inputs with placeholders (55d9db56, #9265)
  • linky: make urls starting with www. links, like markdown (915a891a, #10290)
  • ngAnimate: do not use jQuery class API (40a537c2, #10024, #10329)
  • ngMock: allow numeric timeouts in $httpBackend mock (acb066e8, #4891)
  • ngModel:
    • always use the most recent viewValue for validation (2d6a0a1d, #10126, #10299)
    • fixing many keys incorrectly marking inputs as dirty (d21dff21)
  • ngSanitize: exclude smart quotes at the end of the link (7c6be43e, #7307)
  • numberFilter: numbers rounding to zero shouldn't be negative (96c61fe7, #10278)
  • orderBy:
    • make object-to-primitive behavior work for objects with null prototype (3aa57528)
    • maintain order in array of objects when predicate is not provided (8bfeddb5, #9566, #9747, #10311)

Features

  • $$jqLite: export jqLite as a private service (f2e7f875)
  • $injector: print caller name in "unknown provider" errors (when available) (013b522c, #8135, #9721)
  • jsonFilter: add optional arg to define custom indentation (1191edba, #9771)
  • ngAria: bind keypress on ng-click w/ option (5481e2cf, #10288)

Breaking Changes

We no longer throw an ihshprfx error if the URL after the base path contains only a hash fragment. Previously, if the base URL was http://abc.com/base/ and the hashPrefix is ! then trying to parse http://abc.com/base/#some-fragment would have thrown an error. Now we simply assume it is a normal fragment and that the path is empty, resulting $location.absUrl() === "http://abc.com/base/#!/#some-fragment".

This should not break any applications, but you can no longer rely on receiving the ihshprfx error for paths that have the syntax above. It is actually more similar to what currently happens for invalid extra paths anyway: If the base URL and hashPrfix are set up as above, then http://abc.com/base/other/path does not throw an error but just ignores the extra path: http://abc.com/base.

  • filterFilter: due to a75537d4,

    Named properties in the expression object will only match against properties on the same level. Previously, named string properties would match against properties on the same level or deeper.

    Before:

      arr = filterFilter([{level1: {level2: 'test'}}], {level1: 'test'});   // arr.length -> 1

    After:

      arr = filterFilter([{level1: {level2: 'test'}}], {level1: 'test'});   // arr.length -> 0

    In order to match deeper nested properties, you have to either match the depth level of the property or use the special $ key (which still matches properties on the same level or deeper). E.g.:

      // Both examples below have `arr.length === 1`
      arr = filterFilter([{level1: {level2: 'test'}}], {level1: {level2: 'test'}});
      arr = filterFilter([{level1: {level2: 'test'}}], {$: 'test'});

1.3.5 cybernetic-mercantilism (2014-12-01)

Bug Fixes

1.3.4 highfalutin-petroglyph (2014-11-24)

Bug Fixes

Features

Performance Improvements

  • use Object.create instead of creating temporary constructors (bf6a79c3, #10058)

Breaking Changes

  • ngModelOptions: due to bb4d3b73, previously, ngModel invoked getter/setters in the global context.

For example:

<input ng-model="model.value" ng-model-options="{ getterSetter: true }">

would previously invoke model.value() in the global context.

Now, ngModel invokes value with model as the context.

It's unlikely that real apps relied on this behavior. If they did they can use .bind to explicitly bind a getter/getter to the global context, or just reference globals normally without this.

1.2.27 prime-factorization (2014-11-20)

Bug Fixes

  • $animate: clear the GCS cache even when no animation is detected (f619d032, #8813)
  • $browser:
  • $http: add missing shortcut methods and missing docs (ec4fe1bc, #9180, #9321)
  • $location:
    • revert erroneous logic and backport refactorings from master (1ee9b4ef, #8492)
    • allow 0 in path() and hash() (f807d7ab)
  • $parse: add quick check for Function constructor in fast path (756640f5)
  • $parse, events: prevent accidental misuse of properties on $event (4d0614fd, #9969)
  • ngMock: $httpBackend should match data containing Date objects correctly (1426b029, #5127)
  • orderBy: sort by identity if no predicate is given (45b896a1, #5847, #4579, #9403)
  • select: ensure the label attribute is updated in Internet Explorer (16833d0f, #9621, #10042)

Performance Improvements

  • orderBy: copy array with slice instead of for loop (409bcb38, #9942)

1.3.3 undersea-arithmetic (2014-11-17)

Bug Fixes

  • $http: don't parse single space responses as JSON (6f19a6fd, #9907)
  • minErr: stringify non-JSON compatible objects in error messages (cf43ccdf, #10085)
  • $rootScope: handle cyclic references in scopes when creating error messages (e80053d9, #10085)
  • ngRepeat: support cyclic object references in error messages (fa12c3c8, #9838, #10065, #10085)
  • ngMock: call $interval callbacks even when invokeApply is false (d81ff888, #10032)
  • ngPattern: match behavior of native HTML pattern attribute (85eb9660, #9881, #9888)
  • select: ensure the label attribute is updated in Internet Explorer (6604c236, #9621, #10042)

Features

  • $location: allow to location to be changed during $locationChangeStart (a9352c19, #9607, #9678)
  • $routeProvider: allow setting caseInsensitiveMatch on the provider (0db573b7, #6477, #9873)

Performance Improvements

  • orderBy: copy array with slice instead of for loop (8eabc546, #9942)

Breaking Changes

  • $parse: due to fbad2805, you can't use characters that have special meaning in AngularJS expressions (ex.: . or -) as part of filter's name. Before this commit custom filters could contain special characters (like a dot) in their name but this wasn't intentional.

1.3.2 cardiovasculatory-magnification (2014-11-07)

Bug Fixes

  • $compile: do not rebind parent bound transclude functions (841c0907, #9413)
  • $parse:
    • stateful interceptors override an undefined expression (ed99821e, #9821, #9825)
    • add quick check for Function constructor in fast path (e676d642)
  • $parse, events: prevent accidental misuse of properties on $event (e057a9aa)
  • ngRoute: allow proto inherited properties in route params object (b4770582, #8181, #9731)
  • select: use strict comparison for isSelected with selectAs (9e305948, #9639, #9949)

Features

  • ngAria: announce ngMessages with aria-live (187e4318, #9834)
  • ngMock: decorator that adds Scope#$countChildScopes and Scope#$countWatchers (74981c9f, #9926, #9871)

Security Note

This release also contains security fixes for expression sandbox bypasses.

These issues affect only applications with known server-side XSS holes that are also using CSP to secure their client-side code. If your application falls into this rare category, we recommend updating your version of Angular.

We'd like to thank security researches Sebastian Lekies, Jann Horn, and Gábor Molnár for reporting these issues to us.

We also added a documentation page focused on security, which contains some of the best practices, DOs and DON'Ts. Please check out https://docs.angularjs.org/guide/security.

1.3.1 spectral-lobster (2014-10-31)

Bug Fixes

  • $compile: returning null when an optional controller is not found (2cd5b4ec, #9404, #9392)
  • $observe: check if the attribute is undefined (531a8de7, #9707, #9720)
  • $parse: support dirty-checking objects with null prototype (28661d1a, #9568)
  • $sce: use msie instead of $document[0].documentMode (45252c3a, #9661)
  • $templateRequest: ignore JSON Content-Type header and content (1bd473eb, #5756, #9619)
  • i18n: rename datetimeSymbols to be camelCase (94f5a285)
  • loader: fix double spaces (8b2f1a47, #9630)
  • ngMock: $httpBackend should match data containing Date objects correctly (1025f6eb, #5127)
  • ngSanitize: attribute name: xmlns:href -> xlink:href (4cccf0f2, #9769)
  • select: assign result of track exp to element value (4b4098bf, #9718, #9592)
  • templateRequest: allow empty html template (52ceec22, #9581)
  • testability: escape regex chars in findBindings if using exactMatch (02aa4f4b, #9595, #9600)

Features

  • $compile: allow $watchCollection to be used in bi-directional bindings (40bbc981, #9725)
  • ngSanitize: accept SVG elements and attributes (a54b25d7, #9578, #9751)

Breaking Changes

  • $observe: Due to 531a8de7, observers no longer register on undefined attributes. For example, if you were using $observe on an absent optional attribute to set a default value, the following would not work anymore:
<my-dir></my-dir>
// link function for directive myDir
link: function(scope, element, attr) {
  attr.$observe('myAttr', function(newVal) {
    scope.myValue = newVal ? newVal : 'myDefaultValue';
  })
}

Instead, check if the attribute is set before registering the observer:

link: function(scope, element, attr) {
  if (attr.myAttr) {
    // register the observer
  } else {
    // set the default
  }
}

1.3.0 superluminal-nudge (2014-10-13)

Bug Fixes

Features

Breaking Changes

  • $animate: due to e5f4d7b1, staggering animations that use transitions will now always block the transition from starting (via transition: 0s none) up until the stagger step kicks in. The former behavior was that the block was removed as soon as the pending class was added. This fix allows for styles to be applied in the pending class without causing an animation to trigger prematurely.

1.3.0-rc.5 impossible-choreography (2014-10-08)

Bug Fixes

Features

Performance Improvements

  • $animate:
    • access DOM less in resolveElementClasses (22358cf9)
    • don't join classes before it's necessary in resolveElementClasses (003c44ec)
  • ngBind: set textContent rather than using element.text() (074a146d, #9369, #9396)

Breaking Changes

If a template contains directives within comment nodes, and there is more than a single node in the template, those comment nodes are removed. The impact of this breaking change is expected to be quite low.

Closes #9212 Closes #9215

The $animate CSS class API will always defer changes until the end of the next digest. This allows ngAnimate to coalesce class changes which occur over a short period of time into 1 or 2 DOM writes, rather than many. This prevents jank in browsers such as IE, and is generally a good thing.

If you find that your classes are not being immediately applied, be sure to invoke $digest().

Closes #8234 Closes #9263

ngOptions will now throw an error when the comprehension expressions contains both a select as and track by expression.

These expressions are fundamentally incompatible because it is not possible to reliably and consistently determine the parent object of a model, since select as can assign any child of a value as the model value.

Prior to refactorings in this release, neither of these expressions worked correctly independently, and did not work at all when combined.

See #6564

Order of events has changed. Previously: $locationChangeStart -> $locationChangeSuccess -> $routeChangeStart -> $routeChangeSuccess

Now: $locationChangeStart -> $routeChangeStart -> $locationChangeSuccess -> -> $routeChangeSuccess

Fixes #5581 Closes #5714 Closes #9502

1.3.0-rc.4 unicorn-hydrafication (2014-10-01)

Bug Fixes

Features

Performance Improvements

  • $rootScope: moving internal queues out of the Scope instances (b1192518, #9071)
  • benchmark: add ngBindOnce benchmarks to largetable-bp (2c8b4648)
  • ngForm,ngModel: move initial addClass to the compile phase (b1ee5386, #8268)

Breaking Changes

$transclude functions no longer attach $destroy event handlers to the transcluded content, and so the associated transclude scope will not automatically be destroyed if you remove a transcluded element from the DOM using direct DOM manipulation such as the jquery remove() method.

If you want to explicitly remove DOM elements inside your directive that have been compiled, and so potentially contain child (and transcluded) scopes, then it is your responsibility to get hold of the scope and destroy it at the same time.

The suggested approach is to create a new child scope of your own around any DOM elements that you wish to manipulate in this way and destroy those scopes if you remove their contents - any child scopes will then be destroyed and cleaned up automatically.

Note that all the built-in directives that manipulate the DOM (ngIf, ngRepeat, ngSwitch, etc) already follow this best practice, so if you only use these for manipulating the DOM then you do not have to worry about this change.

Closes #9095 Closes #9281

  • $parse: due to 5572b40b,

  • $scope['this'] no longer exits on the $scope object

  • $parse-ed expressions no longer allow chaining 'this' such as this['this'] or $parent['this']
  • 'this' in $parse-ed expressions can no longer be overridden, if a variable named 'this' is put on the scope it must be accessed using this['this']

Closes #9105

(Note: this change landed in 1.3.0-rc.3, but was not considered a breaking change at the time).

For text based inputs (text, email, url), the $viewValue will now always be converted to a string, regardless of what type the value is on the model.

To migrate, any code or expressions that expect the $viewValue to be anything other than string should be updated to expect a string.

  • input: due to a0bfdd0d60882125f614a91c321f12f730735e7b (see #8949),

Similar to input[number] Angular will now throw if the model value for a input[date] is not a Date object. Previously, Angular only showed an empty string instead. Angular does not set validation errors on the <input> in this case as those errors are shown to the user, but the erroneous state was caused by incorrect application logic and not by the user.

1.2.26 captivating-disinterest (2014-10-01)

Bug Fixes

  • select: make ctrl.hasOption method consistent (11d2242d, #8761)

1.3.0-rc.3 aggressive-pacification (2014-09-23)

Bug Fixes

  • ngModel: support milliseconds in time and datetime (4b83f6ca, #8874)

Features

  • $location: add ability to opt-out of <base> tag requirement in html5Mode (dc3de7fb, #8934)
  • formController: add $setUntouched to propagate untouched state (fd899755, #9050)
  • input: support dynamic element validation (729c238e, #4791, #1404)
  • ngAria: add an ngAria module to make a11y easier (d1434c99, #5486)

Performance Improvements

  • map: use Array.prototype.map (a591e8b8)

Breaking Changes

  • $location: due to dc3de7fb, The $location.html5Mode API has changed to allow enabling html5Mode by passing an object (as well as still supporting passing a boolean). Symmetrically, the method now returns an object instead of a boolean value.

    To migrate, follow the code example below:

    Before:

    var mode = $locationProvider.html5Mode();

    After:

    var mode = $locationProvider.html5Mode().enabled;

Fixes #8934

1.2.25 hypnotic-gesticulation (2014-09-16)

Bug Fixes

  • i18n: fix typo at i18n generation code (1b6d74cc)
  • ngLocale: Regenerate Locale Files (06c76694)
  • select: update option labels when model changes (d89d59f4, #9025)

1.3.0-rc.2 tactile-perception (2014-09-16)

Bug Fixes

Features

Performance Improvements

  • $compile: move $$isolateBinding creation to directive factory instead of on each link (56f09f0b)
  • $parse:
    • execute watched expressions only when the inputs change (fca6be71, #9006, #9082)
    • remove binaryFn and valueFn wrappers from filter expressions (67919c80)

Breaking Changes

  • $parse: due to fca6be71, all filters are assumed to be stateless functions

Previously it was just a good practice to make all filters stateless. Now it's a requirement in order for the model change-observation to pick up all changes.

If an existing filter is stateful, it can be flagged as such but keep in mind that this will result in a significant performance-penalty (or rather lost opportunity to benefit from a major perf improvement) that will affect the $digest duration.

To flag a filter as stateful do the following:

myApp.filter('myFilter', function() {
  function myFilter(input) { ... };
  myFilter.$stateful = true;
  return myFilter;
});

1.3.0-rc.1 backyard-atomicity (2014-09-09)

Bug Fixes

  • $location:
  • $parse: disallow passing Function to Array.sort (bd8ad0fb)
  • input: check scope.$$phase only on $rootScope (bf59d727)
  • ngAnimate: support removing classes from SVG elements when using jQuery (b3b67213, #8872, #8893)
  • ngEventDirs: check scope.$$phase only on $rootScope (203ea10f, #8891)
  • ngForm: don't clear validity of whole form when removing control (953ee22f, #8863)
  • ngInclude: correctly add svg-namespaced template content (6639ca9d, #7538, #8981, #8997)
  • ngModel:
    • update model value with async validators correctly (64c3b745)
    • render immediately also with async validators (f94d5515)
    • properly parse min/max date values as strings for date inputs (088545c1, #6755)
    • revalidate the model when min/max expression values change for date inputs (b3502835, #6755)
    • consider ngMin/ngMax values when validating number input types (25541c1f)
    • revalidate the model when min/max expression values change for number inputs (7b273a2c, #2404)
  • ngModelOptions: do not trigger digest on setViewValue if debouncing (e322cd9b, #8814, #8850, #8911)
  • ngRepeat: preserve original position of elements that are being animated away (ed637330, #8918, #8994)
  • ngSwitch: ensure correct iterator is passed to async function (712299c2, #8833)
  • numberFilter: format numbers that round to zero as nonnegative (ae952fbf, #8489)
  • orderBy: allow arrayLike objects to be ordered (cbdaabfb, #8944)

Features

  • angular.forEach: add the array/object as the 3rd param like the native array forEach (df9e60c8, #7902)
  • ngModelOptions: add allowInvalid option (3c538c1d, #8290, #8313)

Performance Improvements

  • $parse:
    • remove getterFn wrapper for internal use (b3b476db, #8901)
    • removing references to Parser/Lexer from parsed expressions (43c67ccd)
    • calculate array lengths once at start of loop (907b8c16)
  • extend: remove use of forEach to remove calls/closures/passing arguments (9bedeb33, #8898)
  • jQuery: only trigger $destroy if a handler exists (f6aa1c55, #8859)

Breaking Changes

  • ngModelController,formController: due to 6046e14b,

  • ctrl.$error no longer contains entries for validators that were successful.

  • ctrl.$setValidity now differentiates between true, false, undefined and null, instead of previously only truthy vs falsy.

Closes #8941- ngSwitch: due to 0f806d96,

Ever since 0df93fd, tagged in v1.0.0rc1, the ngSwitch directive has had an undocumented change attribute, used for evaluating a scope expression when the switch value changes.

While it's unlikely, applications which may be using this feature should work around the removal by adding a custom directive which will perform the eval instead. Directive controllers are re-instantiated when being transcluded, so by putting the attribute on each item that you want to be notified of a change to, you can more or less emulate the old behavior.

Example:

angular.module("switchChangeWorkaround", []).
  directive("onSwitchChanged", function() {
    return {
      link: function($scope, $element, $attrs) {
        $scope.$parent.$eval($attrs.onSwitchChanged);
      }
    };
  });
<div ng-switch="switcher">
  <div ng-switch-when="a" on-switch-changed="doSomethingInParentScope()"></div>
  <div ng-switch-when="b" on-switch-changed="doSomethingInParentScope()"></div>
</div>

Closes #8858 Closes #8822

1.2.24 static-levitation (2014-09-09)

Bug Fixes

  • $browser: detect changes to the browser url that happened in sync (2ece4d03, #6976)
  • $compile:
  • $location:
    • don't call toString on null values (c12e8d46)
    • remove an unused parameter of $location.url (c65796d4)
    • allow numeric location setter arguments (68a09ba7, #7054)
  • $parse: disallow passing Function to Array.sort (b39e1d47)
  • form: ensure concurrent animations use setClass (d7548fdf, #8166)
  • input: check scope.$$phase only on $rootScope (36e6de1d)
  • ngEventDirs:
  • ngRepeat: improve errors for duplicate items (1812af58)
  • numberFilter: format numbers that round to zero as nonnegative (7e02fa07, #8489)
  • orderBy: allow arrayLike objects to be ordered (94b0f2d3, #8944)

Breaking Changes

The blur and focus event fire synchronously, also during DOM operations that remove elements. This lead to errors as the Angular model was not in a consistent state. See this fiddle for a demo.

This change executes the expression of those events using scope.$evalAsync if an $apply is in progress, otherwise keeps the old behavior.

Fixes #4979 Fixes #5945 Closes #8803 Closes #6910 Closes #5402

1.3.0-RC.0 sonic-boltification (2014-08-29)

Bug Fixes

  • $animate:
  • $browser: detect changes to the browser url that happened in sync (3be00df4, #6976)
  • $compile: use the correct namespace for transcluded svg elements (cb73a37c, #8808, #8816)
  • $location: always resolve relative links in html5mode to <base> url (22948807, #8492, #8172)
  • $parse: properly handle dots at the end of identifiers (8ac90357, #4613, #4912, #8559)
  • Angular: remove duplicate nodeName_ references (a4520a74)
  • currencyFilter: pass through null and undefined values (c2aaddbe, #8605)
  • docs: don't throw exception on the 404 page (550ba01b, #8518)
  • input:
    • validate minlength/maxlength for non-string values (77ce5b89, #7967, #8811)
    • allow to use seconds in input[time] and input[datetime-local] (5f90340a)
    • use year 1970 instead of 1900 for input[time] (29f0b568)
  • ngBindHtml: throw error if interpolation is used in expression (cd21602d, #8824)
  • ngEventDirs: execute blur and focus expression using scope.$evalAsync (719c747c, #4979, #5945, #8803, #6910, #5402)
  • ngModel:
    • always format the viewValue as a string for text, url and email types (1eda1836)
    • allow non-assignable binding when getterSetter is used (ab878a6c, #8704)
    • treat undefined parse responses as parse errors (db044c40)
  • ngRepeat: improve errors for duplicate items (0604bb7b)
  • ngSwitch: avoid removing DOM nodes twice within watch operation (c9b0bfec, #8662)
  • numberFilter: pass through null and undefined values (2ae10f67, #8605, #8842)

Features

  • core:
    • add angular.reloadWithDebugInfo() (41c1b88)
  • $animate:
    • use promises instead of callbacks for animations (bf0f5502)
    • coalesce concurrent class-based animations within a digest loop (2f4437b3)
  • $compile:
  • $compile/ngBind: allow disabling binding info (3660fd09)
  • $http: implement mechanism for coalescing calls to $apply in $http (ea6fc6e6, #8736, #7634, #5297)
  • $rootScope: implement $applyAsync to support combining calls to $apply into a single digest. (e94d454b)
  • $templateRequest: introduce the $templateRequest service (a70e2833)
  • filter: allow to define the timezone for formatting dates (4739b1d9)
  • filterFilter: pass index to function predicate (46343c60, #654)
  • input: allow to define the timezone for parsing dates (cc6fc199, #8447)
  • minErr: allow specifying ErrorConstructor in minErr constructor (a6bd4bc8)
  • ngModel: provide validation API functions for sync and async validations (2ae4f40b)
  • ngRoute: alias string as redirectTo property in .otherwise() (3b5d75c0, #7794)
  • testability: add $$testability service (85880a64)

Performance Improvements

  • $compile:
    • add debug classes in compile phase (e0489abd)
    • only iterate over elements with link functions (fdf9989f, #8741)
  • nodeName_: simplify the code and reduce the number of DOM calls (5a1a0c96)
  • select: execute render after $digest cycle (6f7018d5, #8825)

Breaking Changes

since 1.2.0 and 1.3.0-beta.1

Angular now requires a <base> tag when html5 mode of $location is enabled. Reasoning: Using html5 mode without a <base href="..."> tag makes relative links for images, links, ... relative to the current url if the browser supports the history API. However, if the browser does not support the history API Angular falls back to using the #, and then all those relative links would be broken.

The <base> tag is also needed when a deep url is loaded from the server, e.g. http://server/some/page/url. In that case, Angular needs to decide which part of the url is the base of the application, and which part is path inside of the application.

To summarize: Now all relative links are always relative to the <base> tag.

Exception (also a breaking change): Link tags whose href attribute starts with a # will only change the hash of the url, but nothing else (e.g. <a href="#someAnchor">). This is to make it easy to scroll to anchors inside a document.

Related to #6162 Closes #8492

since 1.2.17 and 1.3.0-beta.10

In html5 mode without a <base> tag on older browser that don't support the history API relative paths were adding up. E.g. clicking on <a href="page1"> and then on <a href="page2"> would produce $location.path()==='/page1/page2'. The code that introduced this behavior was removed and Angular now also requires a <base> tag to be present when using html5 mode.

Closes #8172, #8233

  • ngInclude, ngMessage, ngView and directives that load templates: due to a70e2833

Angular will now throw a $compile minErr each a template fails to download for ngView, directives and ngMessage template requests. This changes the former behavior of silently ignoring failed HTTP requests--or when the template itself is empty. Please ensure that all directive, ngView and ngMessage code now properly addresses this scenario. NgInclude is unaffected from this change.

If any stagger code consisted of having BOTH transition staggers and delay staggers together then that will not work the same way. Angular will now instead choose the highest stagger delay value and set the timeout to wait for that before applying the active CSS class.

Both the API for the cancelation method and the done callback for $animate animations is different. Instead of using a callback function for each of the $animate animation methods, a promise is used instead.

//before
$animate.enter(element, container, null, callbackFn);

//after
$animate.enter(element, container).then(callbackFn);

The animation can now be cancelled via $animate.cancel(promise).

//before
var cancelFn = $animate.enter(element, container);
cancelFn(); //cancels the animation

//after
var promise = $animate.enter(element, container);
$animate.cancel(promise); //cancels the animation

keep in mind that you will still need to run $scope.$apply inside of the then callback to trigger a digest.

$animate.addClass, $animate.removeClass and $animate.setClass will no longer start the animation right after being called in the directive code. The animation will only commence once a digest has passed. This means that all animation-related testing code requires an extra digest to kick off the animation.

//before this fix
$animate.addClass(element, 'super');
expect(element).toHaveClass('super');

//now
$animate.addClass(element, 'super');
$rootScope.$digest();
expect(element).toHaveClass('super');

$animate will also tally the amount of times classes are added and removed and only animate the left over classes once the digest kicks in. This means that for any directive code that adds and removes the same CSS class on the same element then this may result in no animation being triggered at all.

$animate.addClass(element, 'klass');
$animate.removeClass(element, 'klass');

$rootScope.$digest();

//nothing happens...

The value of $binding data property on an element is always an array now and the expressions do not include the curly braces {{ ... }}.

  • currencyFilter: due to c2aaddbe, previously the currency filter would convert null and undefined values into empty string, after this change these values will be passed through.

Only cases when the currency filter is chained with another filter that doesn't expect null/undefined will be affected. This should be very rare.

This change will not change the visual output of the filter because the interpolation will convert the null/undefined to an empty string.

Closes #8605

  • numberFilter: due to 2ae10f67, previously the number filter would convert null and undefined values into empty string, after this change these values will be passed through.

Only cases when the number filter is chained with another filter that doesn't expect null/undefined will be affected. This should be very rare.

This change will not change the visual output of the filter because the interpolation will convert the null/undefined to an empty string.

Closes #8605 Closes #8842

NgModel.viewValue will always be used when rendering validations for minlength and maxlength.

Closes #7967 Closes #8811

According to the HTML5 spec input[time] should create dates based on the year 1970 (used to be based on the year 1900).

Related to #8447.

Any parser code from before that returned an undefined value (or nothing at all) will now cause a parser failure. When this occurs none of the validators present in $validators will run until the parser error is gone. The error will be stored on ngModel.$error.

The blur and focus event fire synchronously, also during DOM operations that remove elements. This lead to errors as the Angular model was not in a consistent state. See this fiddle for a demo.

This change executes the expression of those events using scope.$evalAsync if an $apply is in progress, otherwise keeps the old behavior.

Fixes #4979 Fixes #5945 Closes #8803 Closes #6910 Closes #5402

The returned value from directive controller constructors are now ignored, and only the constructed instance itself will be attached to the node's expando. This change is necessary in order to ensure that it's possible to bind properties to the controller's instance before the actual constructor is invoked, as a convenience to developers.

In the past, the following would have worked:

angular.module("myApp", []).
    directive("myDirective", function() {
        return {
            controller: function($scope) {
                return {
                    doAThing: function() { $scope.thingDone = true; },
                    undoAThing: function() { $scope.thingDone = false; }
                };
            },
            link: function(scope, element, attrs, ctrl) {
                ctrl.doAThing();
            }
        };
    });

However now, the reference to doAThing() will be undefined, because the return value of the controller's constructor is ignored. In order to work around this, one can opt for several strategies, including the use of _.extend() or merge() like routines, like so:

angular.module("myApp", []).
    directive("myDirective", function() {
        return {
            controller: function($scope) {
                _.extend(this, {
                    doAThing: function() { $scope.thingDone = true; },
                    undoAThing: function() { $scope.thingDone = false; }
                });
            },
            link: function(scope, element, attrs, ctrl) {
                ctrl.doAThing();
            }
        };
    });

1.2.23 superficial-malady (2014-08-22)

Bug Fixes

  • $location:
    • rewrite relative URI correctly if path==='/' in legacy html5Mode (c6e4defc, #8684)
    • don't call indexOf() of undefined href attribute (74a7afcb, #7721, #8681)
  • $sanitize: sanitize javascript urls with comments (4f387050, #8274)
  • Angular: make Date comparison in equals() NaN-aware (98f60372, #8650, #8715)
  • copy: clear array destinations correctly for non-array sources (888b0f54, #8610, #8702)
  • input:
    • use lowercase method to account for undefined type (456026ef)
    • by default, do not trim input[type=password] values (ebece0bc, #8250, #8230)
  • linky: handle quotes around email addresses (effc98fd, #8520)
  • minErr: encode btstrpd error input to strip angle brackets (aaf9c5e5, #8683)
  • ngHref: remove attribute when empty value instead of ignoring (ed56872b, #2755)

Breaking Changes

Previously, input[type=password] would trim values by default, and would require an explicit ng-trim="false" to disable the trimming behavior. After this CL, ng-trim no longer affects input[type=password], and will never trim the password value.

Closes #8250 Closes #8230

1.3.0-beta.19 rafter-ascension (2014-08-22)

Bug Fixes

  • $compile:
    • use the correct namespace for transcluded SVG elements (ffbd276d, #8716)
    • update the jQuery .context when an element is replaced by replace:true directive (f02f7d9c, #8253, #7900)
  • $location:
    • rewrite relative URI correctly if path==='/' in legacy html5Mode (d18b2819, #8684)
    • don't call indexOf() of undefined href attribute (5b77e30c, #7721, #8681)
  • $parse: remove unused variable declaration in generated getters (6acea115)
  • $sanitize: sanitize javascript urls with comments (b7e82a33, #8274)
  • $watchGroup: call listener once when the watchExpressions array is empty (bf0e8373)
  • Angular: make Date comparison in equals() NaN-aware (693e846a, #8650, #8715)
  • Scope: don't clear the phase when an exception is thrown from asyncQueue or watch (bf1a57ad)
  • copy: clear array destinations correctly for non-array sources (a603e202, #8610, #8702)
  • forEach: match behavior of Array.prototype.forEach (ignore missing properties) (36230194, #8510, #8522, #8525)
  • input:
    • use lowercase method to account for undefined type (066c0499)
    • by default, do not trim input[type=password] values (a7fb357f, #8250, #8230)
  • jQuery: cooperate with other libraries monkey-patching jQuery.cleanData (b9389b26, #8471)
  • jqLite:
  • linky: handle quotes around email addresses (a9d22712, #8520)
  • minErr: encode btstrpd error input to strip angle brackets (0872388a, #8683)
  • ngRepeat:
    • allow aliasAs identifiers which contain but do not match reserved words (d713ad1b, #8729)
    • make allowed aliasAs expressions more strict (09b29870, #8438, #8440)

Features

  • $compile:
  • benchpress: configure benchpress grunt task (6bdaa4bc)
  • jqLite: implement the detach method (1a05daf5, #5461)
  • ngRoute: add method for changing url params (77a1acc7)

Performance Improvements

  • $compile:
    • don't register $destroy callbacks on element-transcluded nodes (b5f7970b)
    • refactor publicLinkFn to simplify the code and use 'for in' loop (645625cf)
    • clone the nodeList during linking only if necessary (3e0a2e1f)
    • delay object initialization in nodeLinkFn (31ed0af7)
    • optimize nodeLinkFn (35134a0e)
    • optimize publicLinkFn (274e9c4d)
  • $interpolate: do not keep empty separators (94b5c9f0)
  • $parse:
    • don't bind filters to a context (8863b9d0)
    • optimize filter implementation (ece6ef47)
    • speed up fn invocation for no args case (a17578ad)
    • speed up fn invocation by optimizing arg collection (fecfc5b0)
    • use no-proto maps as caches and avoid hasOwnProperty checks (d302ea0c)
    • trim expression only if string (a1341223)
  • $rootScope: do not use Function::call when not needed (7eae29e5)
  • Scope:
    • optimize $watchCollection when used for watching objects (e822e906)
    • don't use forEach in (301463a2)
    • watchCollection optimization (7d96ab0d)
    • exit $broadcast early if nobody is listening for the given event (a09fa356)
    • use remove the need for the extra watch in $watchGroup (3f0e642e, #8396)
  • benchpress: add benchpress node module and port over large table test (1229334f)
  • isObject: use strict comparison (d208ba25)
  • jqLite:
    • simplify jqLiteDealoc (f8f7a1df)
    • optimize event handler (d05f27e2)
    • only take str.split() path when needed (187b1b8e, #8648)
    • optimize off() (abb17cce)
    • refactor jqLiteExpandoStore to minimize access to expensive element.ng339 expando property (1e8698b3)
    • microoptimization in chaining fn (fafbd494)
    • don't use String#split in on() unless we need it (bda673f8)
    • don't check isString many times in constructor (443b521e)
    • optimize jqLiteAcceptsData method (b493c62f)
    • optimize append() and after() (8d933bf9)
    • don't register DOM listener for $destroy event (6251751a)
    • optimize event listener registration (566f1015)
    • improve createEventHandler method by switching from forEach to for loop (e9cd6dc0)
    • don't use forEach in off() (960a8410)
    • don't recreate the Node.contains polyfill (d1536e7c)
    • speed up shallowCopy and special case Attributes cloning (54fa16e4)
  • ngBind: bypass jquery/jqlite when setting text (0a738ce1)
  • ngRepeat:
    • simplify code and remove duplicate array.length access (08eb0558)
    • optimize marking of nodes that are being removed via an animation (36e35b2c)
    • use no-proto objects for blockMaps (13d113c5)
    • move work to compile fn (bdd853cb)
    • move updateScope fn to factory and reuse it for all repeaters (e58d65a5)
    • clone boundary comment nodes (fbd48845)

Breaking Changes

Now, ng-attr-* will never add the attribute to the DOM if any of the interpolated expressions evaluate to undefined.

To work around this, initialize values which are intended to be the empty string with the empty string:

For example, given the following markup:

<div ng-attr-style="border-radius: {{value}}{{units}}"></div>

If $scope.value is 4, and $scope.units is undefined, the resulting markup is unchanged:

<div ng-attr-style="border-radius: {{value}}{{units}}"></div>

However, if $scope.units is "", then the resulting markup is updated:

<div ng-attr-style="border-radius: {{value}}{{units}}" style="border-radius: 4"></div>

Closes #8376 Closes #8399

  • due to 0d608d04, element-transcluded directives now have an extra comment automatically appended to their cloned DOM

This comment is usually needed to keep track the end boundary in the event child directives modify the root node(s). If not used for this purpose it can be safely ignored.

  • due to 75c4cbf8, directive.type was renamed to directive.templateNamespace

This change is breaking only within 1.3.0-beta releases: directive.type was renamed to directive.templateNamespace

The property name type was too general.

  • $parse: due to 8863b9d0, this in filters is now undefined and no longer the scope

It's a bad practice for filters to have hidden dependencies, so pulling stuff from scope directly is not a good idea. Scope being the filter context was never documented as public API, so we don't expect that any significant code depends on this behavior.

If an existing filter has a dependency on the scope instance, the scope reference can be passed into the filter as a filter argument (this is highly discouraged for new code):

Before: {{ user.name | customFilter }} After: {{ user.name | customFilter:this }}

  • Scope: due to 0554c1aa, deregisterNotifier callback for $watch is no longer available

This API was available only in the last few 1.3 beta versions and is not very useful for applications, so we don't expect that anyone will be affected by this change.

  • input: due to a7fb357f, by default, do not trim input[type=password] values.

Previously, input[type=password] would trim values by default, and would require an explicit ng-trim="false" to disable the trimming behavior. After this change, ng-trim no longer affects input[type=password], and will never trim the password value.

Closes #8250 Closes #8230

1.3.0-beta.18 spontaneous-combustion (2014-08-12)

Bug Fixes

  • $compile: make '='-bindings NaN-aware (5038bf79, #8553, #8554)
  • $location: add semicolon to whitelist of delimiters to unencode (36258033, #5019)
  • $parse:
    • one-time binding for literal expressions works as expected (c024f282, #8209)
    • correctly assign expressions who's path is undefined and that use brackets notation (c03ad249, #8039)
  • Scope: add deregisterNotifier to oneTimeLiteralWatch signature (a001a417)
  • jqLite:
    • allow triggerHandler() to accept custom event (01d81cda, #8469)
    • fix regression where mutating the dom tree on a event breaks jqLite.remove (a00c9bca, #8359)
  • ngSanitize: ensure html is a string in htmlParser() (34781f18, #8417, #8416)
  • select:
    • ensure that at least one option has the selected attribute set (25a476ea, #8366, #8429)
    • do not update selected property of an option element on digest with no change event (cdc7db3f, #8221, #7715)

Features

Performance Improvements

  • $q: move Deferred and Promise methods to prototypes (23bc92b1, #8300)
  • input: prevent additional $digest when input is already touched (dd2a803f, #8450)

Breaking Changes

  • jQuery: due to 9e7cb3c3, Angular no longer supports jQuery versions below 2.1.1.
  • $q: due to 23bc92b1, Promises methods are no longer enumerated when using for-loops with hasOwnProperty check. E.g. angular.extends

1.2.22 finicky-pleasure (2014-08-12)

Bug Fixes

  • $compile: make '='-bindings NaN-aware (0b0acb03, #8553, #8554)
  • $parse: correctly assign expressions who's path is undefined and that use brackets notation (60366c8d, #8039)
  • jqLite: allow triggerHandler() to accept custom event (d262378b, #8469, #8505)
  • ngSanitize: ensure html is a string in htmlParser() (9ee07551, #8417, #8416)
  • select:
    • ensure that at least one option has the selected attribute set (79538afd, #8366, #8429)
    • do not update selected property of an option element on digest with no change event (c2860944, #8221, #7715)

Features

1.3.0-beta.17 turing-autocompletion (2014-07-25)

Bug Fixes

  • angular.copy: clone regexp flags correctly (86340a59, #5781, #8337)
  • docs: change plnkr form to open in same window (925b2080)
  • jqLite: triggerHandler support unbind self (8a27abae, #5984)
  • ngHref: remove attribute when empty value instead of ignoring (469ea338, #2755)

Features

  • $compile: change directive's restrict setting to default to EA (element/attribute) (11f5aeee, #8321)
  • $q: add streamlined ES6-style interface for using $q (f3a763fd, #8311, #6427)
  • ngRepeat: provide support for aliasing filtered repeater results as a scope member (e0adb9c4, #5919, #8046, #8282)

Performance Improvements

  • $parse: don't use reflective calls in generated functions (c54228fb)

Breaking Changes

  • $compile: due to 11f5aeee, directives now match elements by default unless specific restriction rules are set via restrict property.

This means that if a directive 'myFoo' previously didn't specify matching restriction, it will now match both the attribute and element form.

Before:

<div my-foo></div> <---- my-foo attribute matched the directive

<my-foo></my-foo> <---- no match

After:

<div my-foo></div> <---- my-foo attribute matched the directive

<my-foo></my-foo> <---- my-foo element matched the directive

It is not expected that this will be a problem in practice because of widespread use of prefixes that make <my-foo> like elements unlikely.

Closes #8321

1.2.21 wizard-props (2014-07-25)

Bug Fixes

Performance Improvements

  • $compile: only create jqLite object when necessary (71eb1901)
  • $parse: don't use reflective calls in generated functions (cbdf0c2a)
  • forEach: use native for loop instead of forEach for Arrays (492b0cdf)
  • jqLite: expose the low-level jqLite.data/removeData calls (3c46c943)
  • ngBindHtml: move addClass to the compile phase (8eede099, #8261)

1.3.0-beta.16 pizza-transubstantiation (2014-07-18)

Bug Fixes

Features

Performance Improvements

  • $compile: only create jqLite object when necessary (a160f76f)
  • bindOnce more performant interpolation and lazy one-time binding (86d55c1d)
  • jqLite: expose the low-level jqLite.data/removeData calls (e4ba8943)
  • ngBindHtml: move addClass to the compile phase (903e7352, #8261)

Breaking Changes

  • $compile: due to e8066c4b, Directives which previously depended on the implicit grouping between directive-start and directive-end attributes must be refactored in order to see this same behavior.

Before:

<div data-fancy-directive-start>{{start}}</div>
  <p>Grouped content</p>
<div data-fancy-directive-end>{{end}}</div>
.directive('fancyDirective', function() {
  return {
    link: angular.noop
  };
})

After:

<div data-fancy-directive-start>{{start}}</div>
  <p>Grouped content</p>
<div data-fancy-directive-end>{{end}}</div>
.directive('fancyDirective', function() {
  return {
    multiElement: true, // Explicitly mark as a multi-element directive.
    link: angular.noop
  };
})

Closes #5372 Closes #6574 Closes #5370 Closes #8044 Closes #7336

Previously, it was possible for an action passed to $watch to be a string, interpreted as an angular expression. This is no longer supported. The action now has to be a function. Passing an action to $watch is still optional.

Before:

$scope.$watch('state', ' name="" ');

After:

$scope.$watch('state', function () {
  $scope.name = "";
});

Closes #8190

If using any of the mechanisms specified above, then migrate by specifying the attribute ng-app to the root element. E.g.

<div ng-app="module">...</div>

Closes #8147

The ngList directive no longer supports splitting the view value via a regular expression. We need to be able to re-join list items back together and doing this when you can split with regular expressions can lead to inconsistent behavior and would be much more complex to support.

If your application relies upon ngList splitting with a regular expression then you should either try to convert the separator to a simple string or you can implement your own version of this directive for you application.

Closes #4008 Closes #2561 Closes #4344

** Directive Priority Changed ** - this commit changes the priority of ngSwitchWhen and ngSwitchDefault from 800 to 1200. This makes their priority higher than ngRepeat, which allows items to be repeated on the switch case element reliably.

In general your directives should have a lower priority than these directives if you want them to exist inside the case elements. If you relied on the priority of these directives then you should check that your code still operates correctly.

Closes #8235

1.3.0-beta.15 unbelievable-advancement (2014-07-11)

Bug Fixes

  • $animate:
  • $http:
    • don't remove content-type header if data is set by request transform (c7c363cf, #7910)
    • add ability to remove default headers (172a4093, #5784)
  • $location: remove query args when passed in object (2c7d0857, #6565)
  • input:
  • jqLite:
    • correctly dealoc svg elements in IE (012ab1f8)
    • remove exposed dealoc method (9c5b407f)
  • ngModel: test & update correct model when running $validate (f3cb2741, #7836, #7837)
  • parseKeyValue: ignore properties in prototype chain (cb42766a, #8070, #8068)
  • select: auto-select new option that is marked as selected (b8ae73e1, #6828)

Features

  • $animate: allow directives to cancel animation events (ca752790, #7722)
  • $controller: disable using global controller constructors (3f2232b5)
  • FormController: add $rollbackViewValue to rollback all controls (85b77314, #7595)
  • input: support constant expressions for ngTrueValue/ngFalseValue (c90cefe1, #8041, #5346, #1199)
  • ngAnimate: conditionally allow child animations to run in parallel with parent animations (8252b8be, #7946)
  • ngModel: bind to getters/setters (b9fcf017, #768)

Performance Improvements

  • $compile: no longer need nodeType filter when setting $scope data (b0ca5195, #7887)

Breaking Changes

$controller will no longer look for controllers on window. The old behavior of looking on window for controllers was originally intended for use in examples, demos, and toy apps. We found that allowing global controller functions encouraged poor practices, so we resolved to disable this behavior by default.

To migrate, register your controllers with modules rather than exposing them as globals:

Before:

function MyController() {
  // ...
}

After:

angular.module('myApp', []).controller('MyController', [function() {
  // ...
}]);

Although it's not recommended, you can re-enable the old behavior like this:

angular.module('myModule').config(['$controllerProvider', function($controllerProvider) {
  // this option might be handy for migrating old apps, but please don't use it
  // in new ones!
  $controllerProvider.allowGlobals();
}]);

Previously, these attributes would always be treated as strings. However, they are now parsed as expressions, and will throw if an expression is non-constant.

To convert non-constant strings into constant expressions, simply wrap them in an extra pair of quotes, like so:

<input type="checkbox" ng-model="..." ng-true-value="'truthyValue'">

Closes #8041 Closes #5346 Closes #1199

1.2.20 accidental-beautification (2014-07-11)

Bug Fixes

  • $http:
    • don't remove content-type header if data is set by request transform (7027844d, #7910)
    • add ability to remove default headers (172a4093, #5784)
  • $location: remove query args when passed in object (a26acb64, #6565)
  • input:
  • parseKeyValue: ignore properties in prototype chain (873acf8f, #8070, #8068)

Features

  • ngAnimate: conditionally allow child animations to run in parallel with parent animations (931789ec, #7946)

1.3.0-beta.14 harmonious-cacophonies (2014-06-30)

This release contains security fixes for $parse that prevent arbitrary code execution via Angular expressions under some very specific conditions. The only applications affected by these vulnerabilities are those that match all of the following conditions:

  • application mixes server-side and client-side templating
  • the server-side templating contains XSS vulnerabilities
  • the vulnerabilities in the server-side templating are being guarded by server-side XSS filters or on the client-side via CSP
  • the server-side XSS vulnerabilities can be used to augment the client-side template processed by Angular

Applications not meeting all of the conditions are not vulnerable.

This fix is in both 1.3.0-beta.14 and 1.2.19 release.

The Angular team would like to thank Jann Horn for reporting these vulnerabilities via [security@angularjs.org].

Bug Fixes

  • $compile: bind ng-attr-* even if unbound attribute follows ng-attr-* (8b0258d8, #7739)
  • $http:
    • should not read statusText on IE<10 when request is aborted (31ae3e71)
    • add the PATCH shortcut back (b28b5caa, #5894)
  • $injector: check if a fn is an array explicitly (b1a6baac, #7904, #2653)
  • $interval: when canceling, use clearInterval from $window instead of global scope. (a4904c0f)
  • $parse:
    • prevent invocation of Function's bind, call and apply (77ada4c8)
    • forbid proto properties in angular expressions (6081f207)
    • forbid {define,lookup}{Getter,Setter} properties (48fa3aad)
    • forbid referencing Object in angular expressions (528be29d)
    • handle constants as one-time binding expressions (d9763f1b, #7970)
  • $timeout/$interval: if invokeApply is false, do not use evalAsync (19b6b343, #7999, #7103)
  • Angular: nodeName should always be lowercase (dafb8a3c, #3987)
  • Angular.copy: preserve prototype chain when copying objects (b59b04f9, #5063, #3767, #4996)
  • core: drop the toBoolean function (bdfc9c02, #3969, #4277, #7960)
  • injector: allow multiple loading of function modules (2f0a4488, #7255)
  • input:
  • jqLite:
    • never add to the cache for non-element/document nodes (91754a76, #7966)
    • don't attach event handlers to comments or text nodes (462dbb20, #7913, #7942)
    • convert NodeList to an Array to make PhantomJS 1.x happy (ceaea861, #7851)
  • numberFilter: correctly round fractions despite floating-point arithmetics issues in JS (189cd064, #7870, #7878)
  • testabilityPatch: fix invocations of angular.mock.dump (e8e07502)

Features

  • NgModel:
    • port the email input type to use the validators pipeline (67379242)
    • port the URL input type to use the validators pipeline (3ee65730)
  • jqLite: support isDefaultPrevented for triggerHandler dummies (7e71acd1, #8008)

Performance Improvements

  • forEach: use native for loop instead of forEach for Arrays (36625de0)

Breaking Changes

You can no longer invoke .bind, .call or .apply on a function in angular expressions. This is to disallow changing the behavior of existing functions in an unforeseen fashion.

The (deprecated) proto property does not work inside angular expressions anymore.

This prevents the use of {define,lookup}{Getter,Setter} inside angular expressions. If you really need them for some reason, please wrap/bind them to make them less dangerous, then make them available through the scope object.

This prevents the use of Object inside angular expressions. If you need Object.keys, make it accessible in the scope.

This changes angular.copy so that it applies the prototype of the original object to the copied object. Previously, angular.copy would copy properties of the original object's prototype chain directly onto the copied object.

This means that if you iterate over only the copied object's hasOwnProperty properties, it will no longer contain the properties from the prototype. This is actually much more reasonable behavior and it is unlikely that applications are actually relying on this.

If this behavior is relied upon, in an app, then one should simply iterate over all the properties on the object (and its inherited properties) and not filter them with hasOwnProperty.

Be aware that this change also uses a feature that is not compatible with IE8. If you need this to work on IE8 then you would need to provide a polyfill for Object.create and Object.getPrototypeOf.

  • core: due to bdfc9c02, values 'f', '0', 'false', 'no', 'n', '[]' are no longer treated as falsy. Only JavaScript falsy values are now treated as falsy by the expression parser; there are six of them: false, null, undefined, NaN, 0 and "".

Closes #3969 Closes #4277 Closes #7960

Previously, even if invokeApply was set to false, a $rootScope digest would occur during promise resolution. This is no longer the case, as promises returned from $timeout and $interval will no longer trigger $evalAsync (which in turn causes a $digest) if invokeApply is false.

Workarounds include manually triggering $scope.$apply(), or returning $q.defer().promise from a promise callback, and resolving or rejecting it when appropriate.

var interval = $interval(function() {
  if (someRequirementFulfilled) {
    $interval.cancel(interval);
    $scope.$apply();
  }
}, 100, 0, false);

or:

var interval = $interval(function (idx) {
  // make the magic happen
}, 1000, 10, false);
interval.then(function(idx) {
  var deferred = $q.defer();
  // do the asynchronous magic --- $evalAsync will cause a digest and cause
  // bindings to update.
  return deferred.promise;
});

1.2.19 precognitive-flashbacks (2014-06-30)

Bug Fixes

  • $compile: bind ng-attr-* even if unbound attribute follows ng-attr-* (ed59370d)
  • $http: should not read statusText on IE<10 when request is aborted (0c80df21)
  • $injector: check if a fn is an array explicitly (67c11b9a, #7904, #2653)
  • $interval: when canceling, use clearInterval from $window instead of global scope. (f780ccfa)
  • $parse:
    • make the window check in ensureSafeObject IE8 friendly (ba62e975)
    • prevent invocation of Function's bind, call and apply (07fa87a8)
    • forbid proto properties in angular expressions (cb713e60)
    • forbid {define,lookup}{Getter,Setter} properties (89ca8597)
    • forbid referencing Object in angular expressions (bc6fb7cc)
  • injector: allow multiple loading of function modules (d71f16e7, #7255)
  • input:
  • jqLite: change expando property to a more unique name (74e1cc68)
  • numberFilter: correctly round fractions despite floating-point arithmetics issues in JS (e5f454c8, #7870, #7878)
  • testabilityPatch: fix invocations of angular.mock.dump (5e944a1c)

Performance Improvements

  • jqLite: don't use reflection to access expandoId (a4faa5cd)

Breaking Changes

You can no longer invoke .bind, .call or .apply on a function in angular expressions. This is to disallow changing the behavior of existing functions in an unforeseen fashion.

The (deprecated) proto property does not work inside angular expressions anymore.

This prevents the use of {define,lookup}{Getter,Setter} inside angular expressions. If you really need them for some reason, please wrap/bind them to make them less dangerous, then make them available through the scope object.

This prevents the use of Object inside angular expressions. If you need Object.keys, make it accessible in the scope.

1.3.0-beta.13 idiosyncratic-numerification (2014-06-16)

Bug Fixes

  • jqLite: change expando property to a more unique name (20c3c9e2)

1.3.0-beta.12 ephemeral-acceleration (2014-06-13)

Bug Fixes

  • $compile:
  • $injector: report circularity in circular dependency error message (545d22b4, #7500)
  • $parse: Handle one-time to null (600a41a7, #7743, #7787)
  • NgModel:
    • ensure pattern and ngPattern use the same validator (1be9bb9d)
    • make ngMinlength and ngMaxlength as standalone directives (26d91b65, #6750)
    • make sure the ngMinlength and ngMaxlength validators use the $validators pipeline (5b8e7ecf, #6304)
    • make sure the pattern validator uses the $validators pipeline (e63d4253)
    • make sure the required validator uses the $validators pipeline (e53554a0, #5164)
  • jqLite: data should store data only on Element and Document nodes (a196c8bc)
  • ngResource: don't convert literal values into Resource objects when isArray is true (16dfcb61, #6314, #7741)

Features

  • NgModel: introduce the $validators pipeline (a8c7cb81)
  • attrs: trigger observers for specific ng-attributes (d9b90d7c, #7758)
  • input: add $touched and $untouched states (adcc5a00)
  • ngInclude: emit $includeContentError when HTTP request fails (e4419daf, #5803)

Performance Improvements

  • $compile: move ng-binding class stamping for interpolation into compile phase (35358fdd)
  • $http: move xsrf cookie check to after cache check in $http (dd1d189e, #7717)
  • Scope: change Scope#id to be a simple number (8c6a8171)
  • forEach: cache array length (55991e33)
  • isArray: use native Array.isArray (751ebc17, #7735)
  • isWindow optimize internal isWindow call (b68ac4cb)
  • jqLite:
    • cache collection length for all methods that work on a single element (41d2eba5)
    • improve performance of jqLite#text (92489886)
    • optimize adding nodes to a jqLite collection (31faeaa7)
    • optimize element deallocation (e35abc9d)
    • don't use reflection to access expandoId (ea9a130a)
  • ngBind: set the ng-binding class during compilation instead of linking (fd5f3896)
  • shallowCopy: use Object.keys to improve performance (04468db4)

Breaking Changes

Requesting isolate scope and any other scope on a single element is an error. Before this change, the compiler let two directives request a child scope and an isolate scope if the compiler applied them in the order of non-isolate scope directive followed by isolate scope directive.

Now the compiler will error regardless of the order.

If you find that your code is now throwing a $compile:multidir error, check that you do not have directives on the same element that are trying to request both an isolate and a non-isolate scope and fix your code.

Closes #4402 Closes #4421

If an expression is used on ng-pattern (such as ng-pattern="exp") or on the pattern attribute (something like on pattern="{{ exp }}") and the expression itself evaluates to a string then the validator will not parse the string as a literal regular expression object (a value like /abc/i). Instead, the entire string will be created as the regular expression to test against. This means that any expression flags will not be placed on the RegExp object. To get around this limitation, use a regular expression object as the value for the expression.

//before
$scope.exp = '/abc/i';

//after
$scope.exp = /abc/i;
  • Scope: due to 8c6a8171, Scope#$id is now of time number rather than string. Since the id is primarily being used for debugging purposes this change should not affect anyone.
  • forEach: due to 55991e33, forEach will iterate only over the initial number of items in the array. So if items are added to the array during the iteration, these won't be iterated over during the initial forEach call.

This change also makes our forEach behave more like Array#forEach.

  • jqLite: due to a196c8bc, previously it was possible to set jqLite data on Text/Comment nodes, but now that is allowed only on Element and Document nodes just like in jQuery. We don't expect that app code actually depends on this accidental feature.

1.2.18 ear-extendability (2014-06-13)

Bug Fixes

  • $compile:
    • ensure transclude works at root of templateUrl (fd420c40, #7183, #7772)
    • bound transclusion to correct scope (1382d4e8)
    • don't pass transcludes to non-transclude templateUrl directives (b9ddef2a)
    • don't pass transclude to template of non-transclude directive (eafba9e2)
    • fix nested isolated transclude directives (bb931097, #1809, #7499)
    • pass transcludeFn down to nested transclude directives (8df5f325, #7240, #7387)
  • $injector: report circularity in circular dependency error message (14e797c1, #7500)
  • ngResource: don't convert literal values into Resource objects when isArray is true (f0904cf1, #6314, #7741)

Performance Improvements

  • $compile: move ng-binding class stamping for interpolation into compile phase (81b7e5ab)
  • $http: move xsrf cookie check to after cache check in $http (8b86d363, #7717)
  • isArray: use native Array.isArray (6c14fb1e)
  • jqLite: cache collection length for all methods that work on a single element (6d418ef5)
  • ngBind: set the ng-binding class during compilation instead of linking (1b189027)

1.3.0-beta.11 transclusion-deforestation (2014-06-06)

Bug Fixes

  • $animate: remove the need to add display:block !important for ngShow/ngHide (7c011e79, #3813)
  • $compile:
    • bound transclusion to correct scope (56c60218)
    • set the iteration state before linking (0c8a2cd2)
    • don't pass transcludes to non-transclude templateUrl directives (2ee29c5d)
    • don't pass transclude to template of non-transclude directive (19af0397)
    • fix nested isolated transclude directives (d414b787, #1809, #7499)
    • pass transcludeFn down to nested transclude directives (1fef5fe8, #7240, #7387)
  • $parse: fix parsing error with leading space and one time bind (24c844df, #7640)
  • angular.copy: support circular references in the value being copied (083f496d, #7618)
  • angular.toJson: only strip properties beginning with $$, not $ (c054288c)
  • ngAnimate:
    • $animate methods should accept native DOM elements (222d4737)
    • fix property name that is used to calculate cache key (9f5c4370, #7566)
  • ngClass: support multiple classes in key (7eaaca8e)
  • ngIf: ensure that the correct (transcluded) scope is used (d71df9f8)
  • ngLocale: fix i18n code-generation to support get_vf_, decimals_, and get_wt_ (cbab51ca)
  • ngRepeat: ensure that the correct (transcluded) scope is used (b87e5fc0)
  • ngShow: ensure that the display property is never set to block (1d90744f, #7707)

Features

  • $resource: allow props beginning with $ to be used on resources (d3c50c84)

Breaking Changes

The isolated scope of a component directive no longer leaks into the template that contains the instance of the directive. This means that you can no longer access the isolated scope from attributes on the element where the isolated directive is defined.

See https://github.com/angular/angular.js/issues/10236 for an example.

  • $resource: due to d3c50c84,

    If you expected $resource to strip these types of properties before, you will have to manually do this yourself now.

  • angular.toJson: due to c054288c,

    toJson() will no longer strip properties starting with a single $. If you relied on toJson()'s stripping these types of properties before, you will have to do it manually now. It will still strip properties starting with $$ though.

1.2.17 - quantum disentanglement (2014-06-06)

Bug Fixes

  • $animate:
    • remove the need to add display:block!important for ngShow/ngHide (55b2f0e8, #3813)
    • retain inline styles for property-specific transitions (ad08638c, #7503)
    • ensure class-based animations always perform a DOM operation if skipped (34d07403, #6957)
  • $compile:
    • do not merge attrs that are the same for replace directives (b635903e, #7463)
    • pass transcludeFn down to nested transclude directives (11385060, #7240, #7387)
    • set $isolateScope correctly for sync template directives (5319621a, #6942)
    • reference correct directive name in ctreq error (6bea0591, #7062, #7067)
    • fix regression which affected old jQuery releases (a97a172e)
  • $httpBackend: don't error when JSONP callback is called with no parameter (a7ccb753, #7031)
  • $location:
  • angular.copy: support circular references in the value being copied (5c997209, #7618)
  • grunt-utils: ensure special inline CSS works when angular is not a global (d4231171, #7176)
  • input:
    • fix ReferenceError in event listener (2d7cb14a)
    • don't dirty model when input event is triggered due to a placeholder change (109e5d1d, #2614, #5960)
  • jqLite: use jQuery only if jQuery.fn.on is present (fafcd628)
  • limitTo: do not convert Infinity to NaN (fcdac65a, #6771, #7118)
  • ngAnimate: $animate methods should accept native DOM elements (9227a5db)
  • ngClass:
    • support multiple classes in key (85ce5d0d)
    • handle index changes when an item is unshifted (a4cc9e19, #7256)
  • ngLocale: fix i18n code-generation to support get_vf_, decimals_, and get_wt_ (96a31476)
  • ngSanitize: encode surrogate pair properly (3d0b49c0, #5088, #6911)
  • ngSwitch: properly support case labels with different numbers of transclude fns (32aa4915)
  • numberFilter: fix rounding error edge case (0388eed7, #7453, #7478)

Features

Performance Improvements

  • $interpolate: optimize value stringification (9d4fa33e, #7501)
  • scope: 10x. Share the child scope class. (9ab9bf6b)

1.3.0-beta.10 excessive-clarification (2014-05-23)

Bug Fixes

  • $animate: retain inline styles for property-specific transitions (98b9d68e, #7503)
  • $compile: do not merge attrs that are the same for replace directives (1ab6e908, #7463)
  • $parse: remove deprecated promise unwrapping (fa6e411d)
  • Scope: $broadcast and $emit should set event.currentScope to null (82f45aee, #7445, #7523)
  • ngModel: do not dirty the input on $commitViewValue if nothing was changed (facd904a, #7457, #7495)

Features

Performance Improvements

Breaking Changes

  • $compile: due to eec6394a, The replace flag for defining directives that replace the element that they are on will be removed in the next major angular version. This feature has difficult semantics (e.g. how attributes are merged) and leads to more problems compared to what it solves. Also, with Web Components it is normal to have custom elements in the DOM.

  • $parse: due to fa6e411d, promise unwrapping has been removed. It has been deprecated since 1.2.0-rc.3. It can no longer be turned on. Two methods have been removed:

    • $parseProvider.unwrapPromises
    • $parseProvider.logPromiseWarnings
  • Scope: due to 82f45aee, #7445, #7523 $broadcast and $emit will now reset the currentScope property of the event to null once the event finished propagating. If any code depends on asynchronously accessing their currentScope property, it should be migrated to use targetScope instead. All of these cases should be considered programming bugs.

1.3.0-beta.9 release-naming (2014-05-16)

Bug Fixes

  • $compile: pass transcludeFn down to nested transclude directives (4f03dc5a, #7240, #7387)
  • jqLite: use jQuery only if jQuery.fn.on present (e9bc51cb)
  • ngClass: handle index changes when an item is unshifted (5fbd618c, #7256)
  • ngMessages: annotate ngMessages controller for minification (0282ca97)
  • numberFilter: fix rounding error edge case (81d427b5, #7453, #7478)

Features

  • ngTouch: add optional ngSwipeDisableMouse attribute to ngSwipe directives to ignore mouse events. (5a568b4f, #6627, #6626)

Breaking Changes

  • jqLite: due to d71dbb1a, the jQuery detach() method does not trigger the $destroy event. If you want to destroy Angular data attached to the element, use remove().

1.3.0-beta.8 accidental-haiku (2014-05-09)

Bug Fixes

  • $compile: set $isolateScope correctly for sync template directives (562c4e42, #6942)
  • $httpBackend: Add missing expectHEAD() method (e1d61784, #7320)
  • $interpolate: don't ReferenceError when context is undefined (924ee6db, #7230, #7237)
  • grunt-utils: ensure special inline CSS works when angular is not a global (af72f40a, #7176)
  • injector: invoke config blocks for module after all providers (c0b4e2db, #7139, #7147)
  • ngModelOptions:
  • ngSanitize: encode surrogate pair properly (627b0354, #5088, #6911)
  • ngSrc, ngSrcset: only interpolate if all expressions are defined (8d180383, #6984)
  • ngSwitch: properly support case labels with different numbers of transclude fns (ac37915e, #7372, #7373)

Features

  • $compile: allow SVG and MathML templates via special type property (f0e12ea7, #7265)
  • $interpolate: add optional allOrNothing param (c2362e3f)
  • FormController: commit $viewValue of all child controls when form is submitted (a0ae07bd, #7017)
  • NgMessages: introduce the NgMessages module and directives (0f4016c8)

Breaking Changes

Previously, it was possible to register a response interceptor like so:

// register the interceptor as a service
$provide.factory('myHttpInterceptor', function($q, dependency1, dependency2) {
  return function(promise) {
    return promise.then(function(response) {
      // do something on success
      return response;
    }, function(response) {
      // do something on error
      if (canRecover(response)) {
        return responseOrNewPromise
      }
      return $q.reject(response);
    });
  }
});

$httpProvider.responseInterceptors.push('myHttpInterceptor');

Now, one must use the newer API introduced in v1.1.4 (4ae46814), like so:

$provide.factory('myHttpInterceptor', function($q) {
  return {
    response: function(response) {
      // do something on success
      return response;
    },
    responseError: function(response) {
      // do something on error
      if (canRecover(response)) {
        return responseOrNewPromise
      }
      return $q.reject(response);
    }
  };
});

$httpProvider.interceptors.push('myHttpInterceptor');

More details on the new interceptors API (which has been around as of v1.1.4) can be found at https://docs.angularjs.org/api/ng/service/$http#interceptors

Previously, config blocks would be able to control behavior of provider registration, due to being invoked prior to provider registration. Now, provider registration always occurs prior to configuration for a given module, and therefore config blocks are not able to have any control over a providers registration.

Example:

Previously, the following:

angular.module('foo', [])
  .provider('$rootProvider', function() {
    this.$get = function() { ... }
  })
  .config(function($rootProvider) {
    $rootProvider.dependentMode = "B";
  })
  .provider('$dependentProvider', function($rootProvider) {
     if ($rootProvider.dependentMode === "A") {
       this.$get = function() {
        // Special mode!
       }
     } else {
       this.$get = function() {
         // something else
       }
    }
  });

would have "worked", meaning behavior of the config block between the registration of "$rootProvider" and "$dependentProvider" would have actually accomplished something and changed the behavior of the app. This is no longer possible within a single module.

This commit changes the API on NgModelController, both semantically and in terms of adding and renaming methods.

  • $setViewValue(value) - This method still changes the $viewValue but does not immediately commit this change through to the $modelValue as it did previously. Now the value is committed only when a trigger specified in an associated ngModelOptions directive occurs. If ngModelOptions also has a debounce delay specified for the trigger then the change will also be debounced before being committed. In most cases this should not have a significant impact on how NgModelController is used: If updateOn includes default then $setViewValue will trigger a (potentially debounced) commit immediately.
  • $cancelUpdate() - is renamed to $rollbackViewValue() and has the same meaning, which is to revert the current $viewValue back to the $lastCommittedViewValue, to cancel any pending debounced updates and to re-render the input.

To migrate code that used $cancelUpdate() follow the example below:

Before:

$scope.resetWithCancel = function (e) {
  if (e.keyCode == 27) {
    $scope.myForm.myInput1.$cancelUpdate();
    $scope.myValue = '';
  }
};

After:

$scope.resetWithCancel = function (e) {
  if (e.keyCode == 27) {
    $scope.myForm.myInput1.$rollbackViewValue();
    $scope.myValue = '';
  }
}

v1.3.0-beta.7 proper-attribution (2014-04-25)

Bug Fixes

  • $location: don't clobber path during parsing of path (498835a1, #7199)

Performance Improvements

  • scope: ~10x speedup from sharing the child scope class. (8377e818)

v1.3.0-beta.6 expedient-caffeination (2014-04-21)

Bug Fixes

  • $animate: ensure class-based animations always perform a domOperation if skipped (708f2ba9, #6957)
  • $compile:
    • reference correct directive name in ctreq error (1192531e, #7062, #7067)
    • fix regression which affected old jQuery releases (ef64169d)
  • $location:
  • input: don't dirty model when input event triggered due to placeholder change (ff428e72, #2614, #5960)
  • limitTo: do not convert Infinity to NaN (5dee9e4a, #6771, #7118)
  • ngModelController: introduce $cancelUpdate to cancel pending updates (940fcb40, #6994, #7014)

Features

  • $resource: Make stripping of trailing slashes configurable. (3878be52)
  • Scope: add $watchGroup method for observing a set of expressions (21f93163)
  • injector: "strict-DI" mode which disables "automatic" function annotation (4b1695ec, #6719, #6717, #4504, #6069, #3611)
  • ngModelOptions: custom triggers and debounce of ngModel updates (dbe381f2, #1285)

Performance Improvements

  • $compile: watch interpolated expressions individually (0ebfa0d1)
  • $interpolate: speed up interpolation by recreating watchGroup approach (546cb429)

Breaking Changes

  • $interpolate: due to 88c2193c, the function returned by $interpolate no longer has a .parts array set on it.

    Instead it has two arrays:

    • .expressions, an array of the expressions in the interpolated text. The expressions are parsed with $parse, with an extra layer converting them to strings when computed
    • .separators, an array of strings representing the separations between interpolations in the text. This array is always 1 item longer than the .expressions array for easy merging with it

1.3.0-beta.5 chimeric-glitterfication (2014-04-03)

Bug Fixes

  • $animate:
    • insert elements at the start of the parent container instead of at the end (1cb8584e, #4934, #6275)
    • ensure the CSS driver properly works with SVG elements (c67bd69c, #6030)
  • $parse: mark constant unary minus expressions as constant (7914d346, #6932)
  • Scope:
    • revert the __proto__ cleanup as that could cause regressions (71c11e96)
    • more scope clean up on $destroy to minimize leaks (d64d41ed, #6794, #6856, #6968)
  • ngClass: handle ngClassOdd/Even affecting the same classes (c9677920, #5271)

Breaking Changes

  • $animate: due to 1cb8584e, $animate will no longer default the after parameter to the last element of the parent container. Instead, when after is not specified, the new element will be inserted as the first child of the parent container.

To update existing code, change all instances of $animate.enter() or $animate.move() from:

$animate.enter(element, parent);

to:

$animate.enter(element, parent, angular.element(parent[0].lastChild));

1.2.16 badger-enumeration (2014-04-03)

Bug Fixes

  • $animate:
    • ensure the CSS driver properly works with SVG elements (38ea5426, #6030)
    • prevent cancellation timestamp from being too far in the future (35d635cb, #6748)
    • run CSS animations before JS animations to avoid style inheritance (0e5106ec, #6675)
  • $parse: mark constant unary minus expressions as constant (6e420ff2, #6932)
  • Scope:
  • filter.ngdoc: Check if "input" variable is defined (a275d539, #6819)
  • input: don't perform HTML5 validation on updated model-value (b2363e31, #6796, #6806)
  • ngClass: handle ngClassOdd/Even affecting the same classes (55fe6d63, #5271)

Features

1.3.0-beta.4 inconspicuous-deception (2014-03-28)

Bug Fixes

  • $animate:
    • prevent cancellation timestamp from being too far in the future (ff5cf736, #6748)
    • make CSS blocking optional for class-based animations (1bebe36a, #6674, #6739)
    • run CSS animations before JS animations to avoid style inheritance (2317af68, #6675)
  • Scope: aggressively clean up scope on $destroy to minimize leaks (f552f251, #6794, #6856)
  • doc-gen: Run Gulp on Windows too (47ba6014, #6346)
  • filter.ngdoc: Check if "input" variable is defined (4a6d4de5, #6819)
  • input: don't perform HTML5 validation on updated model-value (b472d027, #6796, #6806)

Features

Breaking Changes

  • $animate: due to 1bebe36a,

    Any class-based animation code that makes use of transitions and uses the setup CSS classes (such as class-add and class-remove) must now provide a empty transition value to ensure that its styling is applied right away. In other words if your animation code is expecting any styling to be applied that is defined in the setup class then it will not be applied "instantly" unless a transition:0s none value is present in the styling for that CSS class. This situation is only the case if a transition is already present on the base CSS class once the animation kicks off.

Before:

.animated.my-class-add {
  opacity:0;
  transition:0.5s linear all;
}
.animated.my-class-add.my-class-add-active {
  opacity:1;
}

After:

.animated.my-class-add {
  transition:0s linear all;
  opacity:0;
}
.animated.my-class-add.my-class-add-active {
  transition:0.5s linear all;
  opacity:1;
}

Please view the documentation for ngAnimate for more info.

1.3.0-beta.3 emotional-waffles (2014-03-21)

Bug Fixes

  • ngAnimate: support webkitCancelRequestAnimationFrame in addition to webkitCancelAnimationFrame (c839f78b, #6526)
  • $http: allow sending Blob data using $http (b8cc71d4, #5012)
  • $httpBackend: don't error when JSONP callback is called with no parameter (6680b7b9, #4987, #6735)
  • $rootScope: ng-repeat can't handle NaN values. #4605 (fb6062fb, #4605)
  • $rootScope: $watchCollection should call listener with old value (78057a94, #2621, #5661, #5688, #6736)
  • angular.bootstrap: allow angular to load only once (748a6c8d, #5863, #5587)
  • jqLite: inheritedData() now traverses Shadow DOM boundaries via the host property of DocumentFragment (8a96f317, #6637)
  • ngCookie: convert non-string values to string (36528310, #6151, #6220)
  • ngTouch: update workaround for Webkit quirk (bc42950b, #6302)
  • orderBy: support string predicates containing non-ident characters (37bc5ef4, #6143, #6144)
  • select: avoid checking option element's selected property in render (f40f54c6, #2448, #5994)

Features

  • $compile: add support for $observer deregistration (299b220f, #5609)
  • ngMock.$httpBackend: added support for function as URL matcher (d6cfcace, #4580)

Breaking Changes

  • $compile: due to 299b220f, calling attr.$observe no longer returns the observer function, but a deregistration function instead. To migrate the code follow the example below:

Before:

directive('directiveName', function() {
  return {
    link: function(scope, elm, attr) {
      var observer = attr.$observe('someAttr', function(value) {
        console.log(value);
      });
    }
  };
});

After:

directive('directiveName', function() {
  return {
    link: function(scope, elm, attr) {
      var observer = function(value) {
        console.log(value);
      };

      attr.$observe('someAttr', observer);
    }
  };
});
  • $httpBackend: due to 6680b7b9, the JSONP behavior for erroneous and empty responses changed: Previously, a JSONP response was regarded as erroneous if it was empty. Now Angular is listening to the correct events to detect errors, i.e. even empty responses can be successful.

v1.2.15 beer-underestimating (2014-03-21)

Bug Fixes

  • $$RAFProvider: check for webkitCancelRequestAnimationFrame (e84da228, #6526)
  • $$rAF: always fallback to a $timeout incase native rAF isn't supported (ee8e4a94, #6654)
  • $compile: support templates with thead and tfoot root elements (ca0ac649, #6289)
  • $http:
  • $rootScope:
  • angular.bootstrap: only allow angular to load once (0d60f8d3, #5863, #5587)
  • jqLite: traverse host property for DocumentFragment in inheritedData() (98d825e1, #6637)
  • ngAnimate: setting classNameFilter disables animation inside ng-if (a41a2a1d, #6539)
  • ngCookie: convert non-string values to string (93d1c95c, #6151, #6220)
  • ngTouch: update workaround for desktop Webkit quirk (01a34f51, #6302)
  • orderBy: support string predicates containing non-ident characters (10d3e1e4, #6143, #6144)
  • select: avoid checking option element selected properties in render (dc149de9, #2448, #5994, #6769)

1.3.0-beta.2 silent-ventriloquism (2014-03-14)

Bug Fixes

  • $$rAF: always fallback to a $timeout in case native rAF isn't supported (7b5e0199, #6654)
  • $http: don't convert 0 status codes to 404 for non-file protocols (56e73ea3, #6074, #6155)
  • ngAnimate: setting classNameFilter disables animation inside ng-if (129e2e02, #6539)

Features

  • whitelist blob urls for sanitization of data-bound image urls (47ab8df4, #4623)

1.3.0-beta.1 retractable-eyebrow (2014-03-07)

Bug Fixes

Features

  • input: support types date, time, datetime-local, month, week (46bd6dc8, #5864)

Breaking Changes

  • build: due to eaa1d00b, As communicated before, IE8 is no longer supported.
  • input: types date, time, datetime-local, month, week now always require a Date object as model (46bd6dc8, #5864)

For more info: http://blog.angularjs.org/2013/12/angularjs-13-new-release-approaches.html

1.2.14 feisty-cryokinesis (2014-03-01)

Bug Fixes

  • $animate:
    • delegate down to addClass/removeClass if setClass is not found (18c41af0, #6463)
    • ensure all comment nodes are removed during a leave animation (f4f1f43d, #6403)
    • only block keyframes if a stagger is set to occur (e71e7b6c, #4225)
    • ensure that animatable directives cancel expired leave animations (e9881991, #5886)
    • ensure all animated elements are taken care of during the closing timeout (99720fb5, #6395)
    • fix for TypeError Cannot call method 'querySelectorAll' in cancelChildAnimations (c914cd99, #6205)
  • $http:
  • $parse: reduce false-positives in isElement tests (5fe1f39f, #4805, #5675)
  • input: use ValidityState to determine validity (c2d447e3, #4293, #2144, #4857, #5120, #4945, #5500, #5944)
  • isElement: reduce false-positives in isElement tests (75515852)
  • jqLite:
  • numberFilter: convert all non-finite/non-numbers/non-numeric strings to the empty string (cceb455f, #6188, #6261)
  • $parse: support trailing commas in object & array literals (6b049c74)
  • ngHref: bind ng-href to xlink:href for SVGAElement (2bce71e9, #5904)

Features

  • $animate: animate dirty, pristine, valid, invalid for form/fields (33443966, #5378)

Performance Improvements

  • $animate: use rAF instead of timeouts to issue animation callbacks (4c4537e6)
  • $cacheFactory: skip LRU bookkeeping for caches with unbound capacity (a4078fca, #6193, #6226)

1.2.13 romantic-transclusion (2014-02-14)

Bug Fixes

Features

  • filterFilter: support deeply nested predicate objects (b4eed8ad, #6215)

Breaking Changes

  • $animate:

    • due to 4f84f6b3, ngClass and {{ class }} will now call the setClass animation callback instead of addClass / removeClass when both a addClass/removeClass operation is being executed on the element during the animation.

      Please include the setClass animation callback as well as addClass and removeClass within your JS animations to work with ngClass and {{ class }} directives.

    • due to cf5e463a, Both the $animate:before and $animate:after DOM events must be now registered prior to the $animate operation taking place. The $animate:close event can be registered anytime afterwards.

      DOM callbacks used to fired for each and every animation operation that occurs within the $animate service provided in the ngAnimate module. This may end up slowing down an application if 100s of elements are being inserted into the page. Therefore after this change callbacks are only fired if registered on the element being animated.

  • input:

    • due to a9fcb0d0, input[type=file] will no longer support ngModel. Due to browser support being spotty among target browsers, file inputs cannot be cleanly supported, and even features which technically do work (such as ng-change) work in an inconsistent way depending on the attributes of the form control.

      As a workaround, one can manually listen for change events on file inputs and handle them manually.

1.2.12 cauliflower-eradication (2014-02-07)

Bug Fixes

  • $compile: retain CSS classes added in cloneAttachFn on asynchronous directives (5ed721b9, #5439, #5617)
  • $http:
  • $locale: minor grammar amends for the locale locale_lt (95be253f, #6164)
  • $q: make $q.reject support finally and catch (074b0675, #6048, #6076)
  • docs: clarify doc for "args" in $broadcast and $emit (caed2dfe, #6047)
  • filterFilter: don't interpret dots in predicate object fields as paths (339a1658, #6005, #6009)
  • http: make jshint happy (6609e3da)
  • jqLite: trim HTML string in jqLite constructor (36d37c0e, #6053)
  • mocks:
    • rename mock.animate to ngAnimateMock and ensure it contains all test helper code for ngAnimate (4224cd51, #5822, #5917)
    • remove usage of $animate.flushNext in favor of queuing (906fdad0)
    • always call functions injected with inject with this set to the current spec (3bf43903, #6102)
    • refactor currentSpec to work w/ Jasmine 2 (95f0bf9b, #5662)
  • ngMock: return false from mock $interval.cancel() when no argument is supplied (dd24c783, #6103)
  • ngResource:

Breaking Changes

The animation mock module has been renamed from mock.animate to ngAnimateMock. In addition to the rename, animations will not block within test code even when ngAnimateMock is used. However, all function calls to $animate will be recorded into $animate.queue and are available within test code to assert animation calls. In addition, $animate.triggerReflow() is now only available when ngAnimateMock is used.

1.2.11 cryptocurrency-hyperdeflation (2014-02-03)

Bug Fixes

  • $compile: retain CSS classes added in cloneAttachFn on asynchronous directives (5ed721b9, #5439, #5617)
  • $http: update httpBackend to use ActiveXObject on IE8 if necessary (ef210e5e, #5677, #5679)
  • $q: make $q.reject support finally and catch (074b0675, #6048, #6076)
  • filterFilter: don't interpret dots in predicate object fields as paths (339a1658, #6005, #6009)
  • mocks: refactor currentSpec to work w/ Jasmine 2 (95f0bf9b, #5662)
  • ngResource: don't append number to '$' in url param value when encoding URI (ce1f1f97, #6003, #6004)

1.2.10 augmented-serendipity (2014-01-24)

Bug Fixes

  • $parse: do not use locals to resolve object properties (f09b6aa5, #5838, #5862)
  • a: don't call preventDefault on click when a SVGAElement has an xlink:href attribute (e0209169, #5896, #5897)
  • input: use Chromium's email validation regexp (79e519fe, #5899, #5924)
  • ngRoute: pipe preceding route param no longer masks ? or * operator (fd6bac7d, #5920)