| Age | Commit message (Collapse) | Author |
|
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.
|
|
the specified attribute is depricated and creates warnings in Firefox
Closes #3231
Closes #2160
|
|
|
|
Normally $exceptionHandler doesn't throw an exception. It is normally
used just for logging and so on. But if an application developer
implemented a version that did throw an exception then $q would never
have called reject() when converting an exception thrown inside a `then`
handler into a rejected promise.
|
|
|
|
To avoid "Argument type Array is not assignable to parameter type function" validation error When using the minifcation-safe array style
(eg .directive('myDirective', ['$http','$timeout','$compile', function($http,$timeout $compile).... )
Closes #3392
|
|
Closes #3525
|
|
`expect` methods can receive an Object as the data parameter, which was
undocumented.
|
|
angular.copy previously copied RegExp as an empty object. Change detects
RegExp instance and clones into new RegExp. This change is based on a previous
fix to allow Date to be copied.
Closes #3473
Closes #3474
|
|
Closes #3498
|
|
Controllers should be always instantiated after compile fn runs, but before
pre-link fn runs. This way, controllers are available to pre-link fns that
request them.
Previously this was broken for async directives (directives with templateUrl).
Closes #3493
Closes #3482
Closes #3514
|
|
<form name="ctrl.form"> form controller will accessible
as $scope.ctrl.form instead of $scope['ctrl.form']
BREAKING CHANGE:
If you have form names that will evaluate as an expression:
<form name="ctrl.form">
And if you are accessing the form from your controller:
Before:
function($scope) {
$scope['ctrl.form'] // form controller instance
}
After:
function($scope) {
$scope.ctrl.form // form controller instance
}
This makes it possible to access a form from a controller
using the new "controller as" syntax. Supporting the previous
behavior offers no benefit.
|
|
The input field email regex does't not match long domain extensions. This commit extends the email regexp to take a 6 character TLD.
Example 6-character TLDs include .museum and .travel - (e.g. allabout.travel).
|
|
|
|
Closes: #3468
|
|
This reverts commit 90532f5e3c2016c99833a4dd779a5c4718c84f4d.
The commit contains references to minErr that are not available
in the stable branch.
|
|
|
|
Closes #2997
|
|
Previously, the number filter would format small and large numbers
as scientific notation. It now uses toFixed() to ensure that all
requested digits are shown.
|
|
If an app uses HTML5 mode and we open an html5 url on IE8 or 9 which
don't support location href, we use location.replace to reload the page
with the hashbang equivalent of the url but this fails with infinite
digest. This is because location.replace doesn't update location.href
synchronously on IE8 and 9.
Closes #2802, #3305, #1417
|