@bttf wrote:
We're currently building our Ember app inside the context of our legacy app.
There are cases where we navigate away from the app, and the URL is updated by outside javascript.
Ember still tries to 'digest' these URLs even though it's in the background (technically, rootElement is display: none).
Wondering if there was something in the application instance or any other trickery I could employ to 'halt' the app from trying to resolve URLs when it is hidden.
I do have a way of keeping track of its visibility status but can't seem to find a way to 'halt' the app.
Thanks in advance
Posts: 1
Participants: 1