| Age | Commit message (Collapse) | Author | 
 | 
If you have zoomed into the page in your browser then the screen coordinate system no longer
matches the page coordinate system.  To ensure that dragged elements work correctly when zoomed
we should use pageX/pageY rather than screenX/screenY.
Closes #4687
 | 
 | 
Nested bullet points don't appear very nicely so resorted to nested
heading for the Learning Resources and in particular Books sections.
Closes #4677
 | 
 | 
 | 
 | 
 | 
 | 
is used
Closes #4669
 | 
 | 
 | 
 | 
Closes #4674
 | 
 | 
Annotation allows the angular-mocks to be minified, which sometimes happens with frameworks that
automatically process files before running tests.
Also, some developers have been using this library in code for their applications.
This is not recommended as the library is only designed to support testing and not production
applications.  If you are likely to want to use the code here in production you would be best
forking and maintaining your own version of the code as we will not guarantee that we won't
break the annotation of the code in the future.
Closes #4448
 | 
 | 
directives
This is a fix for regression introduced last week by faf5b980.
Closes #4654
 | 
 | 
feature
 | 
 | 
Closes #4536
 | 
 | 
Closes #4670
 | 
 | 
Add note that `input()` fn matches ng-model instead of HTML name attribute.
About five users on forums were snagged by this assumption:
http://docs.angularjs.org/guide/dev_guide.e2e-testing#comment-898079915
Closes #4655
 | 
 | 
Close #4671
 | 
 | 
 | 
 | 
The escaping of the colon in the example CSS is incorrect.
Replace `ng\\:view {` with `ng\:view {`
Closes #4570
 | 
 | 
Closes #1569
Closes #4446
 | 
 | 
Closes #4601
 | 
 | 
 | 
 | 
Closes #4503
 | 
 | 
It is instructive to give literal examples that reflect common (my) experience of the problem. :)
 | 
 | 
Closes #4668
 | 
 | 
Closes #4667
 | 
 | 
Add a note to warn people starting new projects about Protractor replacing the
current ngScenario way of doing E2E testing.
Closes #4644
 | 
 | 
Closes #4648
 | 
 | 
Closes #4647
 | 
 | 
Closes #4639
 | 
 | 
The BabyCtrl was a bit confusing and GrandChildCtrl seems to make more sense
with the whole "scope inheritance" concept.
Closes #4634
 | 
 | 
Closes #4633
 | 
 | 
Although it is still possible to turn this on, the feature is deprecated and it is
best to remove this mention completely here.
Closes #4632
 | 
 | 
 | 
 | 
Closes #4622
 | 
 | 
Closes #4621
 | 
 | 
Closes #4615
 | 
 | 
Closes #4611
 | 
 | 
Closes 4611
 | 
 | 
Angular uses the I18N code from Closure library to generate its own localization
files. So there is no point submitting pull requests for these files, since
all changes would be lost when we next generate these files.
Closes #4610
 | 
 | 
Added documentation for `locals` parameter of `$eval` method.
 | 
 | 
Recently we changed the priority of attribute interpolation directive to -100
to ensure that it executes early in the post linking phase. This causes issues
with when terminal directives are placed on elements with attribute bindings
because the terminal directive will usually have 0 or higher priority which
results in attr interpolation directive not being applied to the element.
To fix this issue I'm switching the priority back to 100 and making moving the
binding setup into the pre-linking function.
This means that:
- terminal directives with priority lower than 100 will not affect the attribute
  binding
- if a directive wants to add or alter bindings it can do so in the pre-linking
  phase, as long as the priority of this directive is more than 100
- all post-linking functions will execute after the attribute binding has been
  set up
- all pre-linking functions with directive priority lower than 100 will execute
  after the attribute bindings have been setup
BREAKING CHANGE: the attribute interpolation (binding) executes as a directive
with priority 100 and the binding is set up in the pre-linking phase. It used
to be that the priority was -100 in rc.2 (100 before rc.2) and that the binding
was setup in the post-linking phase.
Closes #4525
Closes #4528
Closes #4649
 | 
 | 
Closes #4589
 | 
 | 
Closes #4578
 | 
 | 
Closes #4552
 | 
 | 
Closes #4512
 | 
 | 
The non-global controller test throws an error because the test does not
know about the module and so can not find the controller. This change
tells the test about the module so the test can find the controller.
Closes #4489
 | 
 | 
Closes #4483
 | 
 | 
Closes #4477
 | 
 | 
Change landing page to include a set of curated links with subject
headings as a guide through Angular's docs and other resources.
Closes #4470
 | 
 | 
The removed block is repeated from the unit-testing guide and appears
in an awkward place in this text.
Closes #4456
 | 
 | 
The example that demonstrates how to parse expressions can fail if you
pass in the same expression twice.  By using "track by $index" we can
fix this.
Closes #4472
 | 
 | 
It is very easy to let jshint failures slip into the master build if
the jshint task is not part of the standard local grunt tasks.
 |