angular.js v1.5.0-beta.1 Release Notes
Release Date: 2015-09-29 // over 8 years ago-
๐ Bug Fixes
- $compile:
- ๐ $parse:
- $sanitize:
- filters: ensure
formatNumber
observes i18n decimal separators (658a865c, #10342, #12850) - injector: support arrow functions with no parenthesis (03726f7f, #12890)
- input: remove workaround for Firefox bug (b366f035)
- ngAnimate:
- ngMessages: prevent race condition with ngAnimate (8366622b, #12856, #12903)
- ngOptions:
- ngResource: encode
&
in URL query param values (1c97a605, #12201)
๐ Features
- $animateCss: add support for temporary styles via
cleanupStyles
(9f67da62, #12930) - $http: add
$xhrFactory
service to enable creation of custom xhr objects (106f90aa, #2318, #9319, #12159) - $injector: add strictDi property to $injector instance (79577c5d, #11728, #11734)
- $sanitize: make svg support an opt-in (181fc567, #12524)
- ngModel: provide ng-empty and ng-not-empty CSS classes (630280c7, #10050, #12848)
๐ Performance Improvements
- $compile: Lazily compile the
transclude
function (652b83eb) See https://github.com/angular/angular.js/issues/14343#issuecomment-229037252 for more information.
๐ฅ 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.
- ngOptions: due to b71d7c3f,
If your data contains falsy values (
''
,0
,false
andnull
) 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 tongOptions
converting falsy values toundefined
.- ngOptions: due to ded25187,
ngOptions
will now throw ifngModel
is not present on theselect
element. Previously, having nongModel
letngOptions
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.