| Age | Commit message (Collapse) | Author |
|
Added documentation for `locals` parameter of `$eval` method.
|
|
Recently we changed the priority of attribute interpolation directive to -100
to ensure that it executes early in the post linking phase. This causes issues
with when terminal directives are placed on elements with attribute bindings
because the terminal directive will usually have 0 or higher priority which
results in attr interpolation directive not being applied to the element.
To fix this issue I'm switching the priority back to 100 and making moving the
binding setup into the pre-linking function.
This means that:
- terminal directives with priority lower than 100 will not affect the attribute
binding
- if a directive wants to add or alter bindings it can do so in the pre-linking
phase, as long as the priority of this directive is more than 100
- all post-linking functions will execute after the attribute binding has been
set up
- all pre-linking functions with directive priority lower than 100 will execute
after the attribute bindings have been setup
BREAKING CHANGE: the attribute interpolation (binding) executes as a directive
with priority 100 and the binding is set up in the pre-linking phase. It used
to be that the priority was -100 in rc.2 (100 before rc.2) and that the binding
was setup in the post-linking phase.
Closes #4525
Closes #4528
Closes #4649
|
|
Closes #4589
|
|
Closes #4578
|
|
Closes #4552
|
|
Closes #4512
|
|
The non-global controller test throws an error because the test does not
know about the module and so can not find the controller. This change
tells the test about the module so the test can find the controller.
Closes #4489
|
|
Closes #4483
|
|
Closes #4477
|
|
Change landing page to include a set of curated links with subject
headings as a guide through Angular's docs and other resources.
Closes #4470
|
|
The removed block is repeated from the unit-testing guide and appears
in an awkward place in this text.
Closes #4456
|
|
The example that demonstrates how to parse expressions can fail if you
pass in the same expression twice. By using "track by $index" we can
fix this.
Closes #4472
|
|
It is very easy to let jshint failures slip into the master build if
the jshint task is not part of the standard local grunt tasks.
|
|
Closes #4471
|
|
Closes #4451
|
|
messages from 70 to 100
|
|
|
|
Skip addClass animations if the element already contains the class that is being
added to element. Also skip removeClass animations if the element does not contain
the class that is being removed.
Closes #4401
Closes #2332
|
|
|
|
Closes #4449
|
|
Add documentation that the $routeChangeError event is fired when a
route resolve promise is rejected
Closes #4447
|
|
Closes #4433
|
|
Closes #4429
|
|
Closes #4427
|
|
When we re-enter compilation either due to async directive templates or element transclude directive
we need to keep track of controllers to instantiate during linking.
This piece of info was missing when re-entering compilation and that's what this commit fixes.
I also reordered the properties in the previousCompileContext object.
Closes #4434
Closes #4616
|
|
Closes #4424
|
|
Closes #4420
|
|
Closes #4418
|
|
Closes #4410
|
|
A common mistake for beginners is to attach a controller in both the
$routeProvider and also in the html document using the ng-controller
directive. This change highlights this, to help prevent developers from
doing so in the future.
Closes #4409
|
|
Closes #4619
|
|
Now input[type=button] keeps track of both min and max attrs even if they change over time.
|
|
|
|
|
|
errors
|
|
|
|
Closes #4362
|
|
being animated
Closes #4397
Closes #4231
|
|
contains CSS transition/keyframe animation code
Closes #4463
Closes #3784
|
|
|
|
BREAKING CHANGE
The side search bar on the docs page has been removed in favor of the
top search bar.
|
|
|
|
|
|
|
|
|
|
Also add `angular-csp.css` to the resulting build.
|
|
fix ngAnimate throwing exception in cancelChildAnimations on deletion of
element (ngAnimate's leave decorator) of repeated element when using
ng-include on this element.
Closes #4548
|
|
|
|
Revert 581ec6be7d7e546a1c563906e1877498d7d655a2 since it was not valid.
Closes #3952
|
|
When we refactored , we broke the csp mode because the previous implementation
relied on the fact that it was ok to lazy initialize the .csp property, this
is not the case any more.
Besides, we need to know about csp mode during bootstrap and avoid injecting the
stylesheet when csp is active, so I refactored the code to fix both issues.
PR #4411 will follow up on this commit and add more improvements.
Closes #917
Closes #2963
Closes #4394
Closes #4444
BREAKING CHANGE: triggering ngCsp directive via `ng:csp` attribute is not
supported any more. Please use data-ng-csp instead.
|