This repository was archived by the owner on Apr 12, 2024. It is now read-only.

Description
scenario:
app with two routes (/a and /b). user navigates to /a and then quckly to /b without waiting for /a to load.
ng:view sends a request to load /a's template and then /b's template. When the responses arrive, both are processed.
we should ignore or better yet abort request generated due to /a route