| Age | Commit message (Collapse) | Author |
|
|
|
|
|
Closes #4106
|
|
Closes #4105
|
|
Initially, `$httpProvider.defaults.headers.get` is `undefined`, so
`$httpProvider.defaults.headers.get['My-Header']='value'` will throw an
error.
Closes #4101
|
|
|
|
Provides a performance improvement when serializing to JSON strings.
Closes #4093
|
|
See #4043
|
|
|
|
|
|
Closes #3816
|
|
Closes #4050
|
|
Closes #3840
|
|
Closes #3841
|
|
Closes #3838
|
|
- Add missing words.
- Simplify text.
|
|
- Add missing word 'directive'.
- Add missing word 'an'.
|
|
|
|
|
|
Closes #3996
|
|
I came across this issue today and after researching has found out this thread on so:
http://stackoverflow.com/questions/17039998/angular-not-making-http-requests-immediately.
It took me quite sometimes to figure out this so I hope the addition in documentation could save somebody else some times and frustration.
|
|
|
|
Closes #3973
|
|
- Add proper ngdoc annotations to existing $observe documentation
- Add link to directive guide for usage example of $observe
- Add note about $observe function parameter signature
Closes #3957
|
|
Closes #3943
|
|
The behaviour when null or undefined was passed was not clear.
The exception thrown when source == destination was not documented.
Closes #3946
|
|
|
|
Add a summary describing the ignored underscore syntax sugar helper,
with a simple use case example.
Closes #3621
|
|
|
|
It was not clear what you could pass to specify modules to load in the
`module` parameter of this function. The `modules` parameter takes an
array.
The main case is to provide a String, which is the name of a "predefined"
angular module.
The side cases are to provide a Function (or an annotated function in the
form of an Array), which will be invoked by the injector as a run block.
It is not possible to "define" new modules via this parameter.
Closes #3692
|
|
|
|
Per a request made by Peter Bacon Darwin here: http://www.benlesh.com/2013/02/angular-js-scrolling-to-element-by-id.html?showComment=1370941217879#c8718313084813008967
|
|
Closes #3809
|
|
This reverts commit 4407e81c618d42c70e8cfca4f52dfc4a669b5c68.
No features or breaking changes in the stable branch please.
|
|
fix($compile): correct controller for async directives
This reverts commit 51d32243fe8cfbdcd1b647950d4e99ed57677558
as well as commit 9c51d503188efae14b81bd4d6dd7d5a3363f050f
Changing ordering of events in stable branch is not a good idea.
|
|
fix($compile): always instantiate controllers in parent->child order
This reverts commit 683fd713c41eaf5da8bfbf53b574e0176c18c518.
It turns out that there is some existing code that relies on the
incorrect timing. Rather than breaking these apps that depend on
stable releases, we are going to keep this changeo only in master
and the apps will need to migrate to the correc timing during the
1.2 upgrade.
|
|
This fixes regression introduced by #3514 (9c51d503) - this commit is being
reverted here and a better fix is included.
The regression caused the controller to be instantiated before the isolate scope
was initialized.
Closes #3493
Closes #3482
Closes #3537
Closes #3540
|
|
per the [top comment here](http://docs.angularjs.org/api/ngCookies.$cookies#comment-912064775)
updating documentation so it matches [$resource](http://docs.angularjs.org/api/ngResource.$resource)
and instructs the user to include the `angular-cookies.js` and load `ngCookies`.
Closes #3607
|
|
Removed unnecessary additional conditional statement.
|
|
Make sure $timeout callbacks are forgotten about immediately after
execution or cancellation.
Previously when passing invokeApply=false, the cleanup used $q and so
would be pending until the next $digest was triggered. This does not
make a large functional difference, but can be very visible when
looking at memory consumption of an app or debugging around the
$$asyncQueue - these callbacks can have a big retaining tree.
|
|
The $timeout decorator was not forwarding the delay argument to `browser.defer.flush(delay)`.
|
|
|
|
This reverts commit 1a01e80b9cde4a711bee3e6244594b0d7e4b92a4.
This example is bogus, breaks docs.angularjs.org and karma e2e tests
|
|
All other input types already have it.
|
|
|
|
Previously an element like
<div class="foo ng-cloak">...</div>
would still be annoyingly visible if it matched a CSS rule like
.foo { display: inline-block; }, overriding ng-cloak's display: none.
|
|
|
|
Do not trasnform arrays into objects when generating the locale objects
Add unit test for this check
|
|
|
|
angular.equals was returning inconsistent values for the comparison between
{} and []:
angular.equals({}, []) // true
angular.equals([], {}]) // false
Since these object are not of the same type, they should not be considered
equivalent.
|