When a page timeout occurs (relatively rare), the event from the timed out page request has the potential to fire in the middle of the subsequent page request. This doesn't usually occur because new page requests will cancel the previous transition, but there is a small window of opportunity for it to happen between the time that node receives the request and when it tells the app to load the new route.
I haven't yet decided what the best way to handle this is - we can tell Ember to quit loading after a page times out, we can detach the event listener between requests, or we can restart phantom.
When a page timeout occurs (relatively rare), the event from the timed out page request has the potential to fire in the middle of the subsequent page request. This doesn't usually occur because new page requests will cancel the previous transition, but there is a small window of opportunity for it to happen between the time that node receives the request and when it tells the app to load the new route.
I haven't yet decided what the best way to handle this is - we can tell Ember to quit loading after a page times out, we can detach the event listener between requests, or we can restart phantom.