| Age | Commit message (Collapse) | Author | 
 | 
The example in the section "JavaScript-defined Animations" would not run without the ngAnimate dependency. Also added a missing comma and semicolons.
 | 
 | 
Closes https://github.com/angular/angularjs.org/issues/45
 | 
 | 
Closes #5171
 | 
 | 
 | 
 | 
Closes #5148
 | 
 | 
Closes #5145
 | 
 | 
As requested by a top-rated Disqus comment: http://docs.angularjs.org/api/ng.directive:form.FormController#comment-655325797
Closes #5121
 | 
 | 
Closes #5116
 | 
 | 
Move use of `$window` from template to controller, because accessing `$window`
in expressions is now disallowed and doesn't work.
Closes #5110
 | 
 | 
Closes #5104
 | 
 | 
Closes #5104
 | 
 | 
Closes #5102
 | 
 | 
the DOM
Closes #5087
 | 
 | 
Closes #5086
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
This fixes the issue that any usage of $attr is broken after js compilation.
 | 
 | 
The urlResolve method was fixed to automatically remove the
volume label from path names to fix issues with the file
protocol on windows where $location.path() was returning
paths where the first segment would be the volume name,
such as "/C:/mypath". See #4942 and #4928
However, the solution was specific to the $location non-
HTML5 mode, and was implemented at a lower level of
abstraction than it should have been. This refactor moves
the fix to inside of the LocationHashBangUrl $$parse method.
Closes #5041
 | 
 | 
 | 
 | 
`$sanitize` now uses the same mechanism as `$compile` to validate uris.
By this, the validation in `$sanitize` is more general and can be
configured in the same way as the one in `$compile`.
Changes
- Creates the new private service `$$sanitizeUri`.
- Moves related specs from `compileSpec.js` into `sanitizeUriSpec.js`.
- Refactors the `linky` filter to be less dependent on `$sanitize`
  internal functions.
Fixes #3748.
 | 
 | 
apps
Previously if an app was running from file:// origin we would always return either
http 200 or 404 depending on whether the response was present.
This changes the behavior so that we do this only if the protocol of the request
(not the origin) is file:// and only if the status code is 0.
Closes #4436
Closes #4587
Closes #4514
 | 
 | 
Closes #5080
 | 
 | 
 | 
 | 
Closes #5133
 | 
 | 
Closes #5134
 | 
 | 
Closes #4884
 | 
 | 
According to Flagrant Badassery's blog
http://blog.stevenlevithan.com/archives/faster-trim-javascript
and this comparison http://jsperf.com/trim-function, this trim method is faster.
Closes #4406
 | 
 | 
 | 
 | 
Switch the build to use BrowserStack instead of SauceLabs.
This also adds IE11 to our build.
 | 
 | 
 | 
 | 
 | 
 | 
animations
Closes #5130
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
DOM operation
Closes #5106
 | 
 | 
Although modern browser support the "input" event, they still only fire
the "change" event when they auto complete form elements
other than the currently selected one.
Related to #1460
 | 
 | 
We don't actively moderate these comments, and they range from
out of date, to inflammatory, to spam. Going forward, improvements
to the docs should be done via a PR, and questions should go on
StackOverflow where they can be curated and kept up to date by
AngularJS developers who help out there.
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
IE8, IE9 and IE10 can use `script.onreadystate` so up till now we have been using this
if the sniffer says we are on IE.
But IE11 now does not support `script.onreadystate` and only supports the more standard
`script.onload` and `script.onerror`.
IE9 and IE10 do support `script.onload` and `script.onerror`. So now we only test whether
we are on IE8 or earlier before using `script.onreadystate`.
See http://pieisgood.org/test/script-link-events/
jQuery just uses all these handlers at once and hopes for the best, but since IE9 and IE10
support both sets of handlers, this could cause the handlers to be run more than once.
jQuery also notes that there is a potential memory leak in IE unless we remove the handlers
from the script object once they are run.  So we are doing this too, now.
Closes #4523
Closes #4527
Closes #4922
 | 
 | 
 | 
 | 
Previously, when unwrapping promises was set to `true`,
an error would occur if a parsed expression had a
new line in it.
This was because when generating the `evaledFnGetter` code,
a new line in an parsed expression would create a new line
in a JS string in that code, which is illegal. That is:
```js
pw("A+
B")
```
Closes #4718
 | 
 | 
Require bindings to form[action] to be $sce.RESOURCE_URL and bindings to
iframe[srcdoc] to be $sce.HTML
Closes #4927
Closes #4933
 | 
 | 
When a request is aborted, it makes no sense to read the response headers or text.
Also in IE9, trying to read data (either response headers or text) from an aborted request
throws an Error c00c023f.
Fixes #4913
Closes #4940
 | 
 | 
Fixes an issue with httpBackend expectations where a given body object
may not match the actual request body if its keys are serialized in a
different order.
Closes #4956
 |