Live data from Hacker News

LoaderShip – CSS-Only Loaders

loadership.com

1–10 of 65 posts

Re: LoaderShip – CSS-Only Loaders

#3
I wish loaders would provide some feedback on what is going on.

So often, I look at a loader and think "How long will it take? Is it actually still doing something? Or should I try to reload the page?".

Also, I often wonder why developers put tools like this on an extra domain instead of just putting it on a page or subdomain on their personal domain. Is there a reason for this that I am missing?

Re: LoaderShip – CSS-Only Loaders

#4
post #3

I wish loaders would provide some feedback on what is going on. So often, I look at a loader and think "How long will it take? Is it actually still doing something? Or should I try to reload the page?". Also, I often wonder why developers put tools like this on an extra domain instead of just putting it on a page or subdomain on their personal domain. Is there a reason for this that I am missing?

1. It gets worse. Often in aspdotnet we have programmers who will only remove loader on success so you could get a 500 internal server error response and the loader never goes away.

2. I think it makes it easier to get to your website without having to use search and it is easy to share like are we web yet dot org

Re: LoaderShip – CSS-Only Loaders

#10
post #3

I wish loaders would provide some feedback on what is going on. So often, I look at a loader and think "How long will it take? Is it actually still doing something? Or should I try to reload the page?". Also, I often wonder why developers put tools like this on an extra domain instead of just putting it on a page or subdomain on their personal domain. Is there a reason for this that I am missing?

Sometimes I see additional messages pop up next to loaders after certain times passed. Personally if I load from multiple endpoints at the same time I usually add a ##% in the middle of my loading circle calculated based on total and ongoing requests.
Post reply on HN