When I use this in my Ember App, the spinner seems to act in a modal fashion: blocks any input to the Ember app and blocks the UI until it stops spinning or is hidden. This is not desired behavior because what if the app has an error or for some reason is unable to stop or hide the spinner? In that case, the spinner basically "locks up" the Ember app and the user is forced to edit the url in the browser address bar to escape. Instead, I would still like the user to be able to navigate away from the route showing the spinner and interact with the UI while the spinner is spinning.
I want the spinner to be just an indicator saying "hey, something that takes a while is happening, please be patient ..." but if the user decides to navigate away while the spinner is spinning, they should be allowed to.
Sometimes timeouts and error handling can fail, so this is important to me. :-)
Thanks for making this available! :-)
When I use this in my Ember App, the spinner seems to act in a modal fashion: blocks any input to the Ember app and blocks the UI until it stops spinning or is hidden. This is not desired behavior because what if the app has an error or for some reason is unable to stop or hide the spinner? In that case, the spinner basically "locks up" the Ember app and the user is forced to edit the url in the browser address bar to escape. Instead, I would still like the user to be able to navigate away from the route showing the spinner and interact with the UI while the spinner is spinning.
I want the spinner to be just an indicator saying "hey, something that takes a while is happening, please be patient ..." but if the user decides to navigate away while the spinner is spinning, they should be allowed to.
Sometimes timeouts and error handling can fail, so this is important to me. :-)
Any ideas? Thanks!