| Age | Commit message (Collapse) | Author | 
 | 
In Firefox, hovering over an option in an open select menu updates the selected property of option
elements. This means that when a render is triggered by the digest cycle, and the list of options
is being rendered, the selected properties are reset to the values from the model and the option
hovered over changes. This fix changes the code to only use DOM elements' selected properties in a
comparison when a change event has been fired. Otherwise, the internal new and existing option
arrays are used.
Closes #2448
Closes #5994
Closes #6769
 | 
 | 
Android 4.3 only supports webkitCancelRequestAnimationFrame.
Closes #6526
 | 
 | 
Originally we destroyed the oldValue by incrementaly copying over portions of the newValue
into the oldValue during dirty-checking, this resulted in oldValue to be equal to newValue
by the time we called the watchCollection listener.
The fix creates a copy of the newValue each time a change is detected and then uses that
copy *the next time* a change is detected.
To make `$watchCollection` behave the same way as `$watch`, during the first iteration
the listener is called with newValue and oldValue being identical.
Since many of the corner-cases are already covered by existing tests, I refactored the
test logging to include oldValue and made the tests more readable.
Closes #2621
Closes #5661
Closes #5688
Closes #6736
 | 
 | 
Closes #5012
 | 
 | 
PR #5547 introduced conversion of all 0 status codes to 404 for cases
where no response was recieved (previously this was done for the
file:// protocol only). But this mechanism is too eager and
masks legitimate cases where status 0 should be returned. This commits
reverts to the previous mechanism of handling 0 status code for the
file:// protocol (converting 0 to 404) while retaining the returned
status code 0 for all the protocols other than file://
Fixes #6074
Fixes #6155
 | 
 | 
 | 
 | 
 | 
 | 
The recent $$RAFProvider which is a wrapper for the native
requestAnimationFrame method doesn't use the mozRequestAnimationFrame.
Old versions of FF (20 for example) crash if ngAnimate is included
No breaking changes and fix issue https://github.com/angular/angular.js/issues/6535
Closes #6535
Closes #6540
 | 
 | 
Closes #6654
 | 
 | 
Closes #6539
 | 
 | 
 | 
 | 
Moving to new lines & making it bold to avoid confusion
when they r all in same line without any separation
Closes #6633
 | 
 | 
change $route.routes property type to Object, property is marked incorrectly as an Array
Closes #6552
 | 
 | 
`consititute` -> `constitute`
Typo fixed
Closes #6607
 | 
 | 
`preferrable` -> `preferable`
Typo fixed
Closes #6606
 | 
 | 
As highlighted by the new sterner dgeni.
 | 
 | 
If the first element in a template is a <thead> or a <tfoot>, then
use the existing logic to handle table elements compilation.
Closes #6289
 | 
 | 
 | 
 | 
Closed #6544.
 | 
 | 
Typo fixup
Closes #6521
 | 
 | 
- According to
  https://github.com/angular/angular.js/blob/5bf81bc111a866ec65ef86c01336911e577df5df/docs/content/guide/controller.ngdoc#L166
  Ctrl should be the suffix for a controller
Closes #5817
 | 
 | 
Closes #6485
 | 
 | 
 | 
 | 
Closes #5393
 | 
 | 
The docs for the `flush()` method contained a few grammatical
errors and were awkwardly worded. Change the explanation of
the method to remove errors and read more naturally.
Closes #4886
 | 
 | 
 | 
 | 
 | 
 | 
Make it clear that the result of the $parsers pipeline is what goes to the model value.
Closes #5708
 | 
 | 
 | 
 | 
Closes #6463
 | 
 | 
Add css animations when form or field status change to/from dirty,
pristine, valid or invalid. This works like animation system present
with ngClass, ngShow, etc.
Closes #5378
 | 
 | 
Dates are not returned, so remove Date from list of return values.
Closes #3070
 | 
 | 
Fixes #4467
Closes #6448
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
Duplicate 'that' words present in the document, just remove one of them.
Closes #6469
 | 
 | 
Closes #6403
 | 
 | 
Transitions must be blocked so that the initial CSS class can be applied
without triggering an animation. Keyframes do not need to be blocked since
animations are always triggered on the starting CSS class, however, if a
stagger animation is set to occur then all elements for index > 0 should
be blocked. This is to prevent the animation from occuring early on before
the stagger delay for the given element has passed.
With ngAnimate and keyframe animations, IE10 and Safari will render a slight
flicker effect caused by the blocking. This fix resolves this issue.
Closes #4225
 | 
 | 
cancelChildAnimations
When an element containing both ng-repeat and ng-if directives attempts to remove any items from
the repeat collection, the following error is thrown: "TypeError Cannot call method 'querySelectorAll'
of undefined".  This happens because the cancelChildAnimations code naively belives that the jqLite
object always has an element node within it. The fix in this commit addresses to securely check to see
if a node was properly extracted before any child elements are inspected.
Closes #6205
 | 
 | 
animations
If enter -> leave -> enter -> leave occurs then the first leave animation will
animate alongside the second. This causes the very first DOM node (the view in ngView
for example) to animate at the same time as the most recent DOM node which ends
up being an undesired effect. This fix takes care of this issue.
Closes #5886
 | 
 | 
closing timeout
Closes #6395
 | 
 | 
These errors in the docs were preventing some parts of the docs from being
parsed.
 | 
 | 
This reverts commit cad717b1171affc3d540cea372576c70b0cb2295.
This change causes regressions in existing code and after closer inspection
I realized that it is trying to fix an issue that is should not be considered
a valid issue.
The location service was designed to work against either "hash" part of the
window.location when in the hashbang mode or full url when in the html5 mode.
This change tries to merge the two modes partially, which is not right. One
reason for this is that the search part of window.location can't be modified
while in the hashbang mode (a browser limitation), so with this change part
of the search object should be immutable and read-only which will only cause
more confusion.
Relates to #5964
 | 
 | 
Per ECMAScript 5.1 specification trailing commas are allowed in object and
array literals. All modern browsers as well as IE>8 support this syntax.
This commit adds support for such syntax to Angular expressions.
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
Closes #6418
 | 
 | 
Closes #6415
 |