You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: CycleStreets [Submitted to the original trac issue database at 2.29pm, Saturday, 2nd April 2011]
The current Loading data.. indicator at the top is currently too subtle and very easy to miss.
This is especially important to fix on first load.
On my Dual-Core Windows computer it can take a good 10 seconds at least before anything appears on the screen, and that's a reasonably fast computer. On the kinds of underpowered, IE6-style computers that things like Local Authorities and similar use, it would be easy for the user to wonder whether they'd done something wrong.
The text was updated successfully, but these errors were encountered:
Author: CycleStreets [Added to the original trac issue at 2.35pm, Saturday, 2nd April 2011]
My suggested fix is that the first-load (per session, not first ever load only), i.e. when no data is present, shows the 'Loading data...' as a largish (at least 150px size), modal dialog, with a a clear spinner graphic, and a small piece of text giving likely loading times.
When it has finished, i.e. the data is loaded, clear this dialog by having it dissipate into the top-right corner location (i.e. its current location) with an animation. That way it is then obvious that the loading indicator is to be found in that location there, and it need no longer be modal (though a semi-modal dialog could be considered.
Reporter: CycleStreets
[Submitted to the original trac issue database at 2.29pm, Saturday, 2nd April 2011]
The current Loading data.. indicator at the top is currently too subtle and very easy to miss.
This is especially important to fix on first load.
On my Dual-Core Windows computer it can take a good 10 seconds at least before anything appears on the screen, and that's a reasonably fast computer. On the kinds of underpowered, IE6-style computers that things like Local Authorities and similar use, it would be easy for the user to wonder whether they'd done something wrong.
The text was updated successfully, but these errors were encountered: