-
Notifications
You must be signed in to change notification settings - Fork 99
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
webapp: we need a loading spinner #1131
Comments
felipesanches
added a commit
to felipesanches/fontbakery
that referenced
this issue
Oct 26, 2016
animation attributes. To be used as "loading spinner" in the webapp UI. (issues fonttools#1131 & fonttools#1121)
FontBakery logo animated with SVG SMIL attributes to be used as a "spinner" on the webapp while waiting for the server-side check results: Isn't that cool ? :-D |
felipesanches
added a commit
to felipesanches/fontbakery
that referenced
this issue
Oct 27, 2016
animation attributes. To be used as "loading spinner" in the webapp UI. (issues fonttools#1131 & fonttools#1121)
felipesanches
added a commit
to felipesanches/fontbakery
that referenced
this issue
Oct 27, 2016
...server-side. (issues fonttools#1121 & fonttools#1131)
implemented on branch issue_1121 will be merged with the rest of the webapp code tracked by issue #1121 |
felipesanches
added a commit
to felipesanches/fontbakery
that referenced
this issue
Oct 27, 2016
animation attributes. To be used as "loading spinner" in the webapp UI. (issues fonttools#1131 & fonttools#1121)
felipesanches
added a commit
to felipesanches/fontbakery
that referenced
this issue
Oct 27, 2016
...server-side. (issues fonttools#1121 & fonttools#1131)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected behaviour
Display a "waiting for check results ..." with a spinner image so that the user knows something is going on.
Observed behaviour
Webapp feels frozen while waiting for server-side fontbakery run, due to the lack of a visual indicator of the ongoing activity.
The text was updated successfully, but these errors were encountered: