Closed carlesandres closed 11 years ago
Sorry. My fault. I didn't know about the Cmd+S
command. How stupid! Sorry if I have bugged you.
DevTools AutoSave is awesome! Congratulations!
Just one short comment: http://127.0.0.1:9104/ reports DevTools Autosave 1.0.0
while the chrome://chrome/extensions/ page reports DevTools Autosave 1.2.1
.
Keep up with the good work!
Just one short comment: http://127.0.0.1:9104/ reports DevTools Autosave 1.0.0 while the chrome://chrome/extensions/ page reports DevTools Autosave 1.2.1.
It’s a bit confusing yet correct. http://127.0.0.1:9104/ shows the version of autosave protocol, e.g. 1.0.0. chrome://extensions/ shows the version of the browser extension. The extension may have changes unrelated to the protocol, so it’s different.
Hi!
I have just installed DevTools AutoSave in Chrome's stable channel form Mac (Version 20.0.1132.57).
I have also installed node.js and the autosave package since I didn't have them on my system.
I added the following "route" to AutoSave config options:
Now, whenever I modify a CSS property, the corresponding stylesheet file gets updated, and changes are kept when I reload the page. However, changes made to my javascript functions (which are located in a file named main.js) aren't saved at all.
I am not getting any messages neither on my webpage console, nor on the extension's background page console.
Any idea about what I might be doing wrong?
Thanks in advance.