I very much enjoy using NProgress.js (http://ricostacruz.com/nprogress/). Very similar to this library, but with the added benefit of a random increment function that allows you to show progress without knowing the specific position.
NProgress.js natively requires jQuery (1.8+). If you don't want to use jQuery as a dependency, there's a PR on github that uses CSS instead https://github.com/rstacruz/nprogress/pull/28
For Angular there is http://chieffancypants.github.io/angular-loading-bar/, which adds a loading bar by intercepting the $http service. It works automatically. Just drop it in and you have a loading bar just like Nanobar.js
But, this one is nano size :-) I haven't seen how mobile browsers handle the progress element, but this visual is very well suited for showing background activity progress in mobile.
I have to go off-topic to ask something serious. What has happened in the last months that you use something called npm or bower to intsall Javascript libraries, where in the old days I just downloaded them and dropped in my static/lib folder?
Does that assume my project is Node.js powered? I'm on Windows...
You can easily do the same thing you always have. Just snag the JS file [1] or the minified version [2] from the github repo and drop it in your js folder.
Google pretty much Broke The Web with Chrome 33. It shipped a bug that skips rendering Web Fonts until you force a DOM repaint. That means that roughly half the sites in existence will, from time time to time, load up with absolutely no visible text.
The fix will ship in a few weeks with Chrome 35. Until then, get used to refreshing a lot.
It took me several website clicks, comparing different versions, and a lot of work to even see where it was.
I had absolutely no idea what it was doing. I can't be the only one that isn't used to this function, and thus has no idea what's going on when you use one of these.
