There’s been healthy talk about progress indicators in the age of ajax. In our will-to-design I think some things are being missed.

First, your browser’s UI already includes a progress indicator, and perhaps more than one:

progress-chrome

status-chrome

progress-ff

Your user is accustomed to these things, not unlike the back button. Why would we introduce a novel UI element, adding to the user’s cognitive load, when we already have them?

The shortcoming here is that, perhaps, the browser doesn’t offer obvious programmatic access to the above, or that it doesn’t occur to us to use it.

So I published this hack to put the browser in a loading state programmatically. I am sure it can be improved upon, let me know your thoughts.

discuss on hacker news