| Age | Commit message (Collapse) | Author | 
 | 
Closes #5643
 | 
 | 
In order to improve readability from "Is set" (confused on my screen as 'Ls set') updated the
capitalization describing the setting of 4 CSS classes.
Closes #5642
 | 
 | 
This will safe peoples' time, since ngRepeat's docs, not ngInit's, is the first
place where one would search for such info.
Closes #5622
 | 
 | 
With this change it's possible to split the ng-repeat expression into multiple
lines at any point in the expression where white-space is expected.
Closes #5537
Closes #5598
 | 
 | 
Closes #5293
 | 
 | 
If an event was performed natively, jQuery sets the isTrigger property.
When triggering event manually, the field is not present. Manually
triggered events are performed synchronously which causes the "$digest
already in progress" error.
Closes #5293
 | 
 | 
Closes #5374
 | 
 | 
Closes #5361
 | 
 | 
Closes #5338
 | 
 | 
Closes #5343
 | 
 | 
Workaround for chrome for android until #2129 is ready.
Closes #5308, #5323
 | 
 | 
When `multiple` attribute is set on a `<select>` control and the model value is an empty array,
we should invalidate the control.  Previously, this directive was using incorrect logic for
determining if the model was empty.
Closes #5337
 | 
 | 
We cannot use valid /* ... */ CSS comments in examples because they break the parsing
of the ngdoc comments.  We can't use inline // comments because these are not valid in
CSS.
We could use the //!annotate extension to the ngdoc parser but this does not seem to be
working.  It is best to simply remove this line.
Closes #5234
 | 
 | 
allow and pass through new line characters when checking passed in expression
Closes #5000
 | 
 | 
jQuery's elem.html('') is way slower than elem.empty(). As clearing
element contents happens quite often in certain scenarios, switching
to using .empty() provides a significant performance boost when using
Angular with jQuery.
Closes #4457
 | 
 | 
Change the a directive to link and hookup a click event only when
there is no href or name in the template element.
In a large Google app, this results in about 800 fewer registrations,
saving a small but measurable amount of time and memory.
Closes #5362
 | 
 | 
The template needs to be added to the DOM before
other directives at the same element as `ngInclude` are linked.
Fixes #5247.
 | 
 | 
Closes #5285
 | 
 | 
Closes #5257
 | 
 | 
If an element has a directive whose content is loaded using `templateUrl`,
and the element is cloned using a linking function before the template arrives,
the clone needs to be updated as well.
This also updates `ngIf` and `ngRepeat` to keep the connection to the clone
of a tranclude function, so that they know about the changes a directive with
`templateUrl` does to the element in the future.
Fixes to #4930.
 | 
 | 
The priority of ngInit is adjusted to occur before ngInclude, and after
ngController. This enables ngInit to initiallize values in a controller's
scope, and also to initiallize values before ngInclude executes.
Closes #5167
Closes #5208
 | 
 | 
Due to an earlier change, ngModelWatch() no longer returns a value to the
caller. This means the digest loop has no way to tell if the watch actually
modified anything and so can not schedule another pass.
This means any watches that watch form or model controller changes
(e.g. watches on form.$valid) that are scheduled prior to an ngModelWatch()
will not be able to see any changes made therin.
This commit fixes this behavior by returning the latest evaluated ng-model
value.
Closes #5258
Closes #5282
 | 
 | 
The 1.2 release fixed the documented pitfall at 909cabd36d779598763cc358979ecd85bb40d4d7
by isolating only the isolated directive's scope.
Closes #5179
 | 
 | 
As requested by a top-rated Disqus comment: http://docs.angularjs.org/api/ng.directive:form.FormController#comment-655325797
Closes #5121
 | 
 | 
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
 | 
 | 
directives.
Related to #5069
 | 
 | 
When $compile interpolates a CSS class attribute expression it will
do so by comparing the CSS class value already present on the element.
This may lead to unexpected results when dealing with ngClass values being
added and removed therefore it is best that both compile and ngClass delegate
addClass/removeClass operations to the same block of code.
 | 
 | 
This changes the priority of ngController to 500 so that it takes precedence
over ngInclude.
Closes #4431, #4521
 | 
 | 
When composing text in CJKV, intermediate buffer for unfinished text should not
be updating the bound scope variables.
Closes #4684
 | 
 | 
ngClass works by removing all the former classes and then adding all the
new classes to the element during each watch change operation. This may
cause transition animations to never render. The ngClass directive will
now only add and remove the classes that change during each watch operation.
Closes #4960
Closes #4944
 | 
 | 
It was not explicitly and consistently stated that the transient nature of boolean
attributes precludes them from hosting binding expressions.
This change make that more clear and reinforces the simplicity and elegance of the solution.
Closes #5031
 | 
 | 
Replace "ian" in "in"
Closes #5027
 | 
 | 
There should be a space between "braces" and "(`{}`)"
Closes #5026
 | 
 | 
Additional API (backwards compatible)
- Injects `$transclude` (see directive controllers) as 5th argument to directive link functions.
- `$transclude` takes an optional scope as first parameter that overrides the
  bound scope.
Deprecations:
- `transclude` parameter of directive compile functions (use the new parameter for link functions instead).
Refactorings:
- Don't use comment node to temporarily store controllers
- `ngIf`, `ngRepeat`, ... now all use `$transclude`
Closes #4935.
 | 
 | 
Broken by fd7bca22e16b0ecbe1feaf49bab39d9a44b8df01
 | 
 | 
Closes #4948
 | 
 | 
Closes #4936
 | 
 | 
Closes #4914
 | 
 | 
$setViewValue does not really "Read a value from view".
It should be called to trigger the ngModel to be updated when the value in the view changes.
Closes #4907
 | 
 | 
The `<doc:example>` directive does not load up the dependencies correctly.
Using the `<example>` directive, with `<file>` elements fixes this.
Closes #4951
 | 
 | 
another thruthy value.
Fixes #4852.
 | 
 | 
 | 
 | 
Before, there we multiple overview docs:
- guide/overview
- guide/introduction
- guide/dev_guide.mvc
- guide/dev_guide.mvc.understanding_model
- guide/dev_guide.mvc.understanding_view
- guide/concepts
Now we have:
- guide/introduction: High level description of Angular with the key benefits but without code or any concrete concepts
- guide/concepts: explains all important concepts with a simple example and contains deep links to the other parts of the guide.
 All the old information was moved into existing documents or deleted when they were duplicates.
 | 
 | 
 | 
 | 
We need to wait until animations have added the content to the document before
trying to `autoscroll` to anchors that may have been inserted.
Fixes #4723
 | 
 | 
 | 
 | 
Closes #4734
 | 
 | 
Due to animations, DOM might get destroyed much later than scope and so the element $destroy event
might get fired outside of $digest, which causes changes to the validation model go unobserved
until the next digest. By deregistering on scope  event, the deregistration always happens
in $digest and the form validation model changes will be observed.
Closes #4226
Closes #4779
 | 
 | 
 | 
 | 
 |