User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:30.0) Gecko/20100101 Firefox/30.0 (Beta/Release) Build ID: 20140219030203 Steps to reproduce: Development server is Eclipse/Tomcat on Windows 7 Professional SP1 64-bit. SASS watched and compiled using Prepros. with source maps turned on. Originally source map updating was not working on latest Aurora 29, so have tested in 30 with all add-ons disabled. In developer tools select 'Show original sources' Make a CSS change to my scss file. Prepros recompiles file. Actual results: No change to the page. On the file select area no change to '- rules.' Expected results: Page should update with new CSS. '- rules.' should change to '1 rule.' (or more depending on how many changes are made.) If I refresh the page at this point the css has definitely been compiled.

I have tried some other ways of getting this to work. If I load an html page directly from the filesystem, the page styles will reload when changed, and almost instantly. I have tried to get this to work using WAMP (as well as Tomcat mentioned in original post) and cannot get it to work. There may be some issue with my setup though as I have just given it a try in Chrome and I do not see any changes automatically apply in that either. However Chrome it has a history panel which has a link 'apply original content', clicking this will update the styles.

I'm still experiencing this behavior (or something very much like it) in firefox-developer 53.0a2 on linux. I've described my exact setup in this SO post: http://stackoverflow.com/q/42745181/2730823 The only additional behavior is that when I save over my scss file from Firefox, the corresponding entry in the style editor receives a strike-through.

If this is about editing the original sources in the style editor, then I think it is a dup of bug 1346662. If it is about editing in the editor, then I don't think the style editor has any kind of hot-reloading of css like this (at least I haven't found it - if I'm mistaken I would like to know). Do you remember which one you were doing?

This was quite a while ago now... So this was relating to styles being live-reloaded on page by a script which Prepros injected into the html. The changes would show in the browser window fine, but the developer tools would still show the old css files.

In this case I think it was probably fixed by bug 1224558. That bug changed the style editor to notice when style sheets are added.