Hylke, there are actually two actions involved in this issue:
1) page loading spinner you have provided is suitable for route changes (when you are navigating e.g. dashboard -> applications or applications -> app detail
This situation is rate, you will mostly perceive it during initial page transitions, when "views" are not chaged yet. Note that this "delay" can be avoided by concatenating vies to one file and load them during initial page load (see AGPUSH-718).
2) data loading spinner which was suggested in AGPUSH-268 is related to any action that requires data exchange with the server - for this purpose we would likely need some spinner that is placed on top of the page.. indicating that some action is in progress
|