--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/34decd79-67f0-43eb-b4f9-6b6f78efc537%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi,This seems to be related to Persistence2.0 release. We rolled it back in chrome 59/60 - they should work as before.Next, could you please elaborate on what was not working for you in the new setup? We still want to have persistence 2.0, and your feedback will help us understand your use cases.
On Mon, Apr 24, 2017 at 10:05 PM briceh <sido...@gmail.com> wrote:
Hi,--With the new version of Chrome devTools, when I inspect, modify and save a css file from the source nothing happens. It does not ask me anymore where to save the file as before. I have tried to use workspace but I really hate the fact that style changes in the source are persisted immediately without an explicit save. Even so, sometimes I refresh the page and realize that some files have not been saved, and I lost my changes without any notice in the editor.I really regret why I did that update. Google devTools which was one of my best editor is now the one I hate the most. Please let me know how I can disable these persistence change on disk, I want to modify my source files from Chrome devTools as before, and if I am happy with the changes I save them somewhere on my computer, otherwise I refresh the page and restart. I also used to do that to keep and play with several versions of the same css file on my disk, now it is no more possible.Thanks,
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-developer-tools+unsub...@googlegroups.com.