-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spinner good or bad? #12
Comments
I guess the current throbber is a little bit over the top. Many applications use throbbers to indicate that something is loading. This is good UX. If an image have progressive loading the user doesn't know when the image is finished loading, i.e. if the quality will get any better, or if you're just sitting there and waiting for nothing. Perhaps displaying a smaller throbber on top of the image while it's loading would be a better solution? |
The last paragrapsh sounds like the best of both worlds. The throbber is cool, but I prefer progressive loading. I get to see some of it much sooner. |
I agree that we should use a more subtle throbber. Something like this: http://codepen.io/anon/pen/WvpaNy Not sure about the progressive loading, but would be nice to see it in action or external examples. |
Fixed so that there's only a throbber when uploading new images. Image loading is handled by the browser. (i.e. progressively if supported) |
I would think that showing the images as they are loaded the normal way would be much better than showing the spinner. The spinner is distracting, doesn't show the progress and give you no idea about what's to come. Is there a technical reason for using a throbber or is it there to make it look cool?
The text was updated successfully, but these errors were encountered: