Jason Miller 🦊⚛️Feb 14, 2023
With the new Navigation API, you can now show the native spinner + stop button for any asynchronous operation - all you need is a Promise.
Show threadPatrick SmithFeb 14, 2023

@developit So the user can hit the Stop button to cancel whatever is loading? It would be easy for them to accidentally hit Reload if the thing finishes (promise resolves) a moment before the user expects.

I actually think the loading indicator and reload button being reliably controlled by the browser is what makes them so great. If the site can control it, my trust goes down.

Plus the loading indicator kinda has negative connotations (this site is slow).

Show threadJason Miller 🦊⚛️Feb 14, 2023
@royalicing these are all very much accounted for in the browser UI and spec design. Example: The refresh button is inert for a few seconds and until cursor movement when it switches from stop to refresh.
Show threadJason Miller 🦊⚛️
@royalicing hitting stop does cancel this, yes (you get an AbortSignal). Agreed about the negative connotation, but tbh I'd still rather this versus the existing hodgepodge of bespoke spinners and loading treatments (skeleton shimmers 😮‍💨)
Feb 14, 2023 at 10:50pmMasto
Show threadPatrick SmithFeb 14, 2023

@developit True, it’s almost a cultural thing. If the loading indicator can be used consistently and reliably then this will be better. Maybe if it had a slightly different symbol or colour then I as a user know which Loading or Stop will happen?

Yeah I agree skeleton UI is totally over used. A bandaid on top of slow responses.