| Age | Commit message (Collapse) | Author | 
 | 
we needed this upgrade to disable animations in scenario runner
(karma ships with its own copy of angular-scenario.js which
got update in 0.8.4)
 | 
 | 
animations cause the dom to contain elements that have been removed
from the model but are being animated out.
we could teach the e2e runner to wait for animations but that would
make all tests slower. it should be quite safe to just disable
animations automatically when the app is running via the e2e test
runner.
this change disables only css animations. we should make additional
change that disables js animations as well, but since we don't need
this right now I'm punting on it.
 | 
 | 
Regression introduced by ngAnimation
SHA: 0b6f1ce5f89f47f9302ff1e8cd8f4b92f837c413
 | 
 | 
Offending SHA: 0b6f1ce5f89f47f9302ff1e8cd8f4b92f837c413
 | 
 | 
Offending SHA: 0b6f1ce5f89f47f9302ff1e8cd8f4b92f837c413
 | 
 | 
 | 
 | 
files inside docs comment code
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
BREAKING CHANGE:
It is considered an error to have two items produce
the same track by key. (This was tolerated before.)
 | 
 | 
The new method allows to shallow watch collections (Arrays/Maps).
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
Improved $controller function doc readability.
 | 
 | 
 | 
 | 
myApp.factory('myAroundInterceptor', function($rootScope, $timeout) {
    return function(configPromise, responsePromise) {
        return {
            request: configPromise.then(function(config) {
                return config
            });
            response: responsePromise.then(function(response) {
                return 'ha!';
            }
        });
}
myApp.config(function($httpProvider){
    $httpProvider.aroundInterceptors.push('myAroundInterceptor');
});
 | 
 | 
 | 
 | 
docs(forms): Fixed a typo. render -> $render
 | 
 | 
datetime symbols
 | 
 | 
datetimesymbolsext.js)
 | 
 | 
Added aliases for minification
 | 
 | 
Rename unused arrayLength variable to arrayBound and use it inside loop
 | 
 | 
Off-by-one error.
 | 
 | 
Remove fromCharCode function as it was used only in two inner
functions in the code, and its functionality is achieved in several
other places by using String.fromCharCode
Breaks fromCharCode closure function, String.fromCharCode should be
used instead
 | 
 | 
This doc was using both definite article and indefinite article at the same time.
 | 
 | 
 | 
 | 
FirefoxOS uses special URLs like
app://{d0419af1-8b42-41c5-96f4-ef4179e52315}/index.html for packaged Apps.
Closes #2112
 | 
 | 
I hope this helps someone, I ran into some issues when following the API as described - handlers of this event receive 3 arguments, not 2.
Although this is mentioned [elsewhere](http://docs.angularjs.org/api/ng.$rootScope.Scope#$on) it's not clear when viewing the docs for this behaviour in isolation. 
The first argument is an Event Object, not the current route. The previous route argument can also be omitted on occasions.
 | 
 | 
edit mode of that file in github
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
Add a new module ngMobile, with mobile/touch-specific directives.
Add ngClick, which overrides the default ngClick. This ngClick uses touch
events, which are much faster on mobile. On desktop browsers, ngClick
responds to click events, so it can be used for portable sites.
 | 
 | 
$inject was used where $injector was appropriate; confusing and
misleading.
 | 
 | 
... so that we can access it from local VMs.
The security risk of doing this is very low since only the current
working directory is being made accessible to everyone. There is also
an option to run a local firewall, which is a better way to secure the
developer's machine anyway.
 | 
 | 
In situations where path() matched basepath and we needed to
convert from html5 url to hashbang url, the $location service
considered the url to be already rewritten, which resulted in
an error.
 | 
 | 
Preserve the order of the elements that are not part of a case nor default in
a ng-switch directive
BREAKING CHANGE: elements not in the ng-switch were rendered after the
    ng-switch elements.  Now they are rendered in-place.
    Ng-switch directives should be updated with non ng-switch elements
    in render-order.  e.g.
    The following was previously rendered with <li>1</li> after "2":
    <ul ng-switch="select">
        <li>1</li>
        <li ng-switch-when="option">2</li>
    </ul>
    To keep the old behaviour, say:
    <ul ng-switch="select">
        <li ng-switch-when="1">2</li>
        <li>1</li>
    </ul>
Closes #1074
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
Changed "obeject" to "object"
 | 
 | 
 | 
 | 
 | 
 | 
the `nextRoute` object available in `$routeChangeStart` handler
accidentaly leaked  property which pointed to the route definition
currently being matched.
this was done just for the internal needs of the `$route` implementation
and was never documented as public api.
Some confusion arouse around why the $route property was not always
available on the `nextRoute` object (see #1907). The right thing for us
to do is to prefix the property with $$ for now and refactor the code
to remove the property completely in the future. Application developers
should use the `nextRoute` object itself rather than its `$route` property.
The main diff is that nextRoute inherits from the object referenced by $route.
BREAKING CHANGE: in $routeChangeStart event, nextRoute.$route property is gone.
Use the nextRoute object instead of nextRoute.$route.
Closes #1907
 | 
 | 
 | 
 | 
When we need more control over http caching, we may want to provide
a custom cache to be used in all http requests by default.
To skip default cache, set {cache: false} in request configuration.
To use other cache, set {cache: cache} as before.
See #2079
 |