I'd much rather wade through the html and css in a github project then try to decode the ramblings of a hastily written tutorial.
I wrote something very similar a couple weeks ago - going to go back and apply some of the nice visual effects this contribution shows - very appreciated!
Yes!
The sum of these tiny 'do one thing and do it well'-projects improve our collective developer-lives tremendously.
This one may be just 3 lines of CSS. But it has to be the right three lines or it will break on some browsers. And those 3 lines might change in the future to accomodate new browsers.
tldr; Code sharing is good. Do it.
What's the rationale for CSS only? Considering progress is about waiting for things to happen, what is the timing based on? What triggers updates or changes?
Seems like an odd thing to have a progress bar, but no JavaScript events or methods to update it. Missing an important abstraction/interface. I'm not seeing the use cases where JavaScript won't be used to update the progress. A meta-refresh?