| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
this is necessary to avoid $apply from within $apply situations
|
|
|
|
$apply/$digest
Chrome (probably other browsers as well) fires 'hashchange' event synchronously, so if you change raw location from within $apply/$digest, we don't want to $apply twice. (It would throw an exception)
|
|
|
|
|
|
|
|
|
|
|
|
- there are too many unknowns about PATCH, so I'm dropping its support until we know that this is actually useful
- expectGET, expectHEAD and expectJSON (and the same for whenXXX) should not require response data to be specified
|
|
|
|
scrolling (links)
Now, that we have autoscroll attribute on ng:include, there is no reason to disable the service completely, so $anchorScrollProvider.disableAutoScrolling() means it won't be scrolling when $location.hash() changes.
And then, it's not $autoScroll at all, it actually scrolls to anchor when it's called, so I renamed
it to $anchorScroll.
|
|
|
|
+ use autoscroll in docs (ng:include)
|
|
|
|
|
|
|
|
|
|
mock)
|
|
|
|
|
|
|
|
|
|
|
|
typeof null == 'object', but it doesn't behave like an object
because its properties can't be dereferenced, so we need
to special-case it.
Closes #702
|
|
|
|
it's just slowing down the test runs and debugging
|
|
|
|
|
|
- provider -> decorator
- autoflush + passThrough mode
- fix noop -> angular.noop
|
|
|
|
|
