| Age | Commit message (Collapse) | Author |
|
jQuery 1.10.2 does not attach data to comment nodes, which previously broke `$compile`.
This changes how elements with "transclude element" and a controller are compiled to
avoid the issue.
Closes #3764
|
|
Closes #4106
|
|
Closes #4105
|
|
Initially, `$httpProvider.defaults.headers.get` is `undefined`, so
`$httpProvider.defaults.headers.get['My-Header']='value'` will throw an
error.
Closes #4101
|
|
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.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
|
|
Closes #4050
|
|
Closes #3835
|
|
|
|
Closes #3840
|
|
|
|
Closes #3841
|
|
Closes #3838
|
|
- Add missing words.
- Simplify text.
|
|
- Add missing word 'directive'.
- Add missing word 'an'.
|
|
|
|
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.
|
|
|
|
According to http://validator.w3.org/ , <!--> is not a valid comment
and neither is any comment containing the -- substring.
|
|
Closes #3973
|
|
Some typos fixed and grammar improved:
- withing -> within
- life-cycle -> life cycle
- extraneous spaces
- grammar mistakes
- missing commas
- reworded unclear statements
Closes #3920
|
|
|
|
|
|
|
|
- Add proper ngdoc annotations to existing $observe documentation
- Add link to directive guide for usage example of $observe
- Add note about $observe function parameter signature
Closes #3957
|
|
Closes #3943
|
|
The behaviour when null or undefined was passed was not clear.
The exception thrown when source == destination was not documented.
Closes #3946
|
|
|
|
Firefox 23 has deprecated the use of createEvent for transition and
animation events. We must now use `new TransitionEvent()` and
`new AnimationEvent()` if they are available.
But of course IE doesn't support this format correctly so we must wrap
the attempt in a try block and revert to document.createEvent if necessary..
|
|
onAnimationProgress now checks the event's elapsedTime property before
checking the originalEvent.elapsedTime property.
Use browserTrigger with elapsedTime parameter to trigger animation events
|
|
BREAKING CHANGE: browserTrigger now uses an eventData object instead of direct parameters for mouse events.
To migrate, place the `keys`,`x` and `y` parameters inside of an object and place that as the third parameter
for the browserTrigger function.
|
|
$timeouts to track ongoing animations
Closes #3629
Closes #3874
|
|
Add a summary describing the ignored underscore syntax sugar helper,
with a simple use case example.
Closes #3621
|