You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 12, 2024. It is now read-only.
Discovered this trying to recreate an issue I'm having with a custom directive that uses the $http service. Check the console in each... the code is identical, but with v1.0.7 the ajax request is made and with v1.2.0rc1 the ajax request is never sent. If you copy -> paste the ajax request lines in 1.2.0 then both of the requests are fired:
With the absolute latest 1.2.0rc1 if you use $timeout instead, the ajax does fire. However, whether or not $http makes an ajax request shouldn't depend on whether or not it was called inside of a setTimeout or a $timeout - both should work. $timeout should only be necessary for $apply'ing the results.
Discovered this trying to recreate an issue I'm having with a custom directive that uses the $http service. Check the console in each... the code is identical, but with v1.0.7 the ajax request is made and with v1.2.0rc1 the ajax request is never sent. If you copy -> paste the ajax request lines in 1.2.0 then both of the requests are fired:
http://jsfiddle.net/mQpNh/
http://jsfiddle.net/xW4YY/1/
The text was updated successfully, but these errors were encountered: