angular-cookies
Advanced tools
Changelog
1.3.5 cybernetic-mercantilism (2014-12-01)
<a name="1.3.4"></a>
Changelog
1.3.4 highfalutin-petroglyph (2014-11-24)
$isEmpty
to check the model validity
(40406e2f)count
to be a one-time expression
(2b41a586,
#10004)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
.
<a name="1.2.27"></a>
Changelog
1.2.27 prime-factorization (2014-11-20)
<a name="1.3.3"></a>
Changelog
1.3.3 undersea-arithmetic (2014-11-17)
.
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.<a name="1.3.2"></a>
Changelog
1.3.2 cardiovasculatory-magnification (2014-11-07)
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.
<a name="1.3.1"></a>
Changelog
1.3.1 spectral-lobster (2014-10-31)
findBindings
if using exactMatch
(02aa4f4b,
#9595, #9600)$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
}
}
<a name="1.3.0"></a>
Changelog
1.3.0 superluminal-nudge (2014-10-13)
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.<a name="1.3.0-rc.5"></a>
Changelog
1.3.0-rc.5 impossible-choreography (2014-10-08)
0
in path()
and hash()
(b8c5b871)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
<a name="1.3.0-rc.4"></a>
Changelog
1.2.19 precognitive-flashbacks (2014-06-30)
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.
<a name="1.3.0-beta.13"></a>