| Age | Commit message (Collapse) | Author |
|
Initially, `$httpProvider.defaults.headers.get` is `undefined`, so
`$httpProvider.defaults.headers.get['My-Header']='value'` will throw an
error.
Closes #4101
|
|
Closes #4100
|
|
Closes #4099
|
|
initially undefined
Previously if the collection model was set to undefined on the first digest,
the repeater would get confused and not use the correct tracking function
for associating model with dom elements in the repeater.
Closes #4145
Closes #3964
|
|
|
|
Provides a performance improvement when serializing to JSON strings.
Closes #4093
|
|
Ref: https://github.com/angular/angular.dart/blob/master/test/directives/ng_non_bindable_spec.dart
|
|
Ref: https://github.com/angular/angular.js/pull/4045
I have this sinking feeling that support this use case sort of
encourages binding to function that blindly trust some html. For now,
I'm fixing the issue while I think about the use cases some more.
In the case of a function that performs any non-trivial work before
wrapping the value (e.g. the showdown filter in issue #3980, or the
binding to a simply wrapper function in issue #3932 if it did anything
meaty), this fix makes it "work" - but performance is going to suck -
you should bind to some other thing on scope that watches the actual
source and adjusts itself when that changes (e.g. the showdown filter.)
For the case of the wrapper in #3932, if one isn't performing
sanitization or some such thing - then you the developer has insight
into why that value is safe in that particular context - and it should
be available simply by name and not as a result of a function taking any
arbitrary input to make auditing of security a little saner.
Closes #3932, #3980
|
|
|
|
BREAKING CHANGE: ngInclude's priority is now set to 1000
It's quite rare for anyone to depend on explicity directive priority,
but if a custom directive that needs to run before ngInclude exists,
it should have its priority checked and adjusted if needed.
Closes #3793
|
|
This fixes the "TypeError: Object doesn't support this property or method" error on IE8,
when view templates contain leading white-space.
Closes #3971
|
|
Closes #4061
|
|
Closes #4076
|
|
See #4043
|
|
|
|
|
|
Closes #3816
|
|
|
|
|
|
See the discussion at http://docs.angularjs.org/guide/dev_guide.services.understanding_services#comment-1002821035
Closes #4055
|
|
The de-ge locale does not exist
Closes #4053
|
|
Closes #4050
|
|
|
|
Closes #3835
|
|
|
|
When using Angular in the root of a domain with HTML5 URLs
where there are links to external paths within the same directory,
the `otherwise` route handler will catch these external files.
This can be fixed by prefixing '.' onto the links to URLs that should
be handled by angular routing.
Original Issue: #3520
Example of Fix: http://fiddle.jshell.net/fgHf6/3/
Closes #3555
|
|
The existing documentation for this step could have people find themselves
unable to run the `e2e-test.sh` script. This note added regarding
`karma-ng-scenario` will minimize their confusion and allow people to run
the script.
Closes #4033
|
|
Closes #3840
|
|
|
|
|
|
|
|
Closes #3841
|
|
Closes #3836
|
|
Closes #3838
|
|
- Add missing words.
- Simplify text.
|
|
- Add missing word 'directive'.
- Add missing word 'an'.
|
|
|
|
|
|
Closes #3985
|
|
The first parameter in $routeChangeError is the event object.
Closes #3986
|
|
Closes #3993
|
|
|
|
|
|
Closes #3996
|
|
I came across this issue today and after researching has found out this thread on so:
http://stackoverflow.com/questions/17039998/angular-not-making-http-requests-immediately.
It took me quite sometimes to figure out this so I hope the addition in documentation could save somebody else some times and frustration.
|
|
|
|
|
|
Previously, the check that Application should return a new $window and
$document had the arguments reversed in the first call to navigateTo;
thus, the subsequent check of inequality of $window and $document in the
next navigateTo call would always pass.
This corrects the argument order, which makes this test not succeptible
to false positives.
|
|
According to http://validator.w3.org/ , <!--> is not a valid comment
and neither is any comment containing the -- substring.
|
|
Closes #3972
|