[BasDirks]

Why I don't like this kind of solution (yet):

I like to mess around in my CSS loads, trying different combinations, trying whether a property has an actual effect on the appearance/flow of the page, etc.

I like to then make changes that have been throughly tested inside vim, :w, CMD-TAB, CMD-SHIFT-R.

By separating experimentation and editing, I know exactly what is added to my CSS, without having to think about whether or not all in-browser changes are truly necessary for my purpose. I bet use of these kinds of extensions by inexperienced web-designers (togglers we might call them) will lead to extremely ugly and bloated stylesheets.

[rlander]

Unless you accidentally close or reload the browser window (or there's a power failure). This has happened to me more times than I care to remember.

[BasDirks]

I create a "task" (you can do this with any todo app, but I use taskwarrior) for every change I make to my css, ie: "more appropriate top margin @ index". Then I solve exactly that problem, change the selectors/properties I need in my stylesheet, and review the solution (to see if other rules are affected or overwritten).

define problem -> solve problem -> refine solution -> commit/save changes.

might sounds slow, but really isn't, and keeps things clean.