angular-scenario
Advanced tools
Changelog
1.5.6 arrow-stringification (2016-05-27)
templateUrl
(5ae72dc7)this
in pre-/post-linking functions
(47bc98a1,
#9306)srcset
to undefined
(308f22ba,
#14470, #14493)$templateCache
as well
(10955969,
#14479, #14496)splice()
with 2 arguments or more
(6f1fae8a,
#14467, #14489)$sce.valueOf()
(instead of toString()
)
(1c1c9b27,
#14526, #14527)<a name="1.4.11"></a>
Changelog
1.4.11 relentless-syncomania (2016-05-27)
srcset
to undefined
(85a53ea9,
#14470, #14493)$templateCache
as well
(ad21f8fe,
#14479, #14496)splice()
with 2 arguments or more
(4e735e53,
#14467, #14489)gSize
!== lgSize
(a1188721,
#14289, #14290)$sce.valueOf()
(instead of toString()
)
(f31586db,
#14526, #14527)inject()
on IE10+, PhantomJS
(56dae6fa,
#13591, #13592, #13593)<a name="1.5.5"></a>
Changelog
1.5.5 material-conspiration (2016-04-18)
$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.
noop()
as controller for multiple components
(4c8aeefb,
#14391, #14402)$onChanges
even if the inner value already matches the new value
(d9448dcb,
#14406)@
bindings
(499e1b2a,
#14070)$onChanges
hook is called correctly
(0ad2b708,
#14355, #14359)toString()
are annotated properly
(d384834f,
#14361)inject()
on IE10+, PhantomJS
(e9c718a4,
#13591, #13592, #13593)eventHandlers
/uploadEventHandlers
(25d4e5cc,
#14436)forEach
(c115b37c,
#12529)documentFragment
to populate select
options
(6a4124d0,
#13607, #13239, #12076)<a name="1.5.4"></a>
Changelog
1.5.3 diplohaplontic-meiosis (2016-03-25)
gSize
!== lgSize
(3277b885,
#14289, #14290)<a name="1.5.2"></a>
Changelog
1.4.10 benignant-oscillation (2016-03-16)
console.log
when window.console
exists
(beb00e44,
#14006, #14007, #14047)$watch
(ab5c7698)Blob
objects
(863a4232,
#9669, #14064):
(571afd65,
#13880, #13887)ngIf
(dc158e7e,
#13865, #13876)responseType
to $delegate
when using passThrough
(947cb4d1,
#5415, #5783)<a name="1.5.0"></a>
Changelog
1.5.1 equivocal-sophistication (2016-03-16)
console.log
when window.console
exists
(ce138f3c,
#14006, #14007, #14047)Blob
objects
(e9d579b6,
#9669, #14064)ngView
to be included in an asynchronously loaded template
(8237482d,
#1213, #6812, #14088)responseType
to $delegate
when using passThrough
(d16faf9f,
#5415, #5783)has()
method for checking the existence of a controller
(bb9575db,
#13951, #14109)LLLL
)
(3e5b25b3,
#13999, #14013)sharedInjector()
to angular.mock.module
(a46ab60f,
#14093, #10238)<a name="1.4.10"></a>
Changelog
1.5.0 ennoblement-facilitation (2016-02-05)
inputs
for expressions with expensive checks
(37cb9ad4)this
context when calling helper functions for $watch
(1c6edd41):
(622c4216,
#13880, #13887)ngIf
(8aecf46a,
#13865, #13876)Changelog
1.5.0-rc.2 controller-requisition (2016-01-28)
ngTouch
module's ngClick
directive has been deprecated and disabled by default. See the breaking
changes section for more informationangular.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.$animate.pin()
host elements
(7700e2df,
#13783)usemap
as it can be used as a security exploit
(234053fc)$locale
(63492a02,
#13390)areAnimationsAllowed
check
(683bd92f)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:
<meta name="viewport" content="width=device-width">
is settouch-action
css property is set to none
or manipulation
See this article by Telerik for more info on the topic.
Note that this change does not affect the ngSwipe
directive.
<a name="1.4.9"></a>
Changelog
1.4.9 implicit-superannuation (2016-01-21)
event.timeStamp
anymore for time tracking
(620a20d1,
#13494, #13495)$animate.pin()
host elements
(a985adfd,
#13783)minErr
(0c1b54f0)$
(2563ff7b,
#13736)undefined
expressions
(7bb2414b)timeout
and log a warning
(47486524)ngModelCtrl.$render
in the select
directive's postLink function
(529b2507,
#13583, #13583, #13663)$animate.closeAndFlush()
(512c0811)areAnimationsAllowed
check
(2d3303dd)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.
<a name="1.5.0-rc.1"></a>