2 ms·
That's not true at all. In the websites I and many others build, that loading spinner is linked directly to network code. The spinner appears when a request is
by fastball 9y ago
That's not true at all. In the websites I and many others build, that loading spinner is linked directly to network code.
The spinner appears when a request is made. It disappears when the request is resolved.
- TeMPOraL 9y agoI was talking about animation. Show/hide on request made/resolved gives only binary information about starting and finishing something. But the spinning animation itself does not represent any operations being executed. It may very well be that the request failed and a bug in JS made it not remove the spinner. You end up with a forever-looping animation of "work", even though no work is being done. This makes the spinner an untrustworthy element.
- fastball 9y agoStill better than nothing? Sure, maybe sometimes exceptions aren't handled properly, but at least you know that it was trying to do something, rather than having users click a submit button 10x because there was no UI feedback whatsoever.