-
Notifications
You must be signed in to change notification settings - Fork 127
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
Suggestion: position of the default spinner #42
Comments
Thanks a lot for your feedback! If you have any suggestion or request about it, please share them here. Cheers, |
Great to hear you had already given it some thought. I think your suggested options would do the trick indeed! |
any news on the next release where this is included? |
I had started to work on a new major release that used the Intersection Observer API, but it became clear that in order to fully take advantage of it (and get rid of interval polling), it had to implement the Resize Observer API too. If things don't get better in a few months, I will probably release a new minor version that includes some new features like this one (even thought I wanted to implement and expose them in a totally different way), leaving the complete overhaul for better times... |
Hi,
I've used this awesome snippet a lot in various websites. Love it, you did an amazing job!
I know that several elements, such as the progress-bar, can be positioned.
The default spinner can't tough. I recently run into an issue where the overlay is shown into a particularly div element. No matter how large the dive, the user is always scrolled to the top of it, before the loading overlay shows. Therefore it makes sense to position the spinner at the top, instead of center, as well. Checking the currently online demo, the following code does that trick:
.loadingoverlay{ flex-flow: unset; align-items: flex-start; }
I thought I'd share the suggestion; perhaps there are more people looking for this flexibility.
Once again: keep up the good work!
The text was updated successfully, but these errors were encountered: