Saving file doesn't trigger browser reload

[peheje]

Brackets version 37, OSX Mavericks 10.9.2

Sometimes saving a file doesn't trigger the reload in Chrome, seems to only happen if I open the folder in which the file I'm editing is located.

A video is linked:
https://dl.dropboxusercontent.com/u/1823537/bug.mp4
I noticed how it's as if it doesn' work when Chrome address bar says 127.0.0.1 but works when the address bar just displays the filepath.

Thanks for a nice piece of SW!

[marcelgerber]

Well, AFAIK (inline) JS works not that good yet in live preview (at least code that is only fired once).

It works in the other project cause files outside of a project are "previewed" via file:/// protocol and simply reloaded on save.

[pthiess]

@dangoor Is this getting better once we refactored the Tern integration?

[dangoor]

@contradel We could change the behavior so that if you save an HTML file with JavaScript changes in it, it then reloads the browser. I don't think we'd want to reload the browser on every keypress (with HTML and CSS, we can make less disruptive changes in the browser in a way that's not really possible with JS).

@pthiess this particular request doesn't really touch the JS code hints.

[njx]

Reviewed, medium priority. Might at least want a way to message to people that script tags don't live update.

[nullroar]

I've been spoiled by live, in-editor CSS changes without the need to save. I guess I shouldn't have gotten my hopes up for JS, in retrospect.

[dangoor]

@nullroar Yeah, I'd love to be able to do live JS and have thought about it a fair bit. But, there are a variety of reasons why it just can't work (at least not the way people write typically JS).

[nullroar]

Assuming it wouldn't load any variables that haven't been declared and wouldn't run a loop before it is finished, what's wrong with, say, a "push" feature to push the new functions / variables etc. without actually "saving" ?

The issue a lot of folks have (especially those from an HTML/CSS background) is that we are in the habit of testing code before we save, and it feels a bit unusual to "save" in order to test.

#Wishlist.

[peheje]

Hi Dangoor. Thank you for the response.
Have you seen the video?
When you save a file it already automatically refreshes the page IF you haven't opened the folder wherein your working file is. This seems to agree with the feature list:
https://github.com/adobe/brackets/wiki/How-to-Use-Brackets#live-preview

"If you edit any other type of file, the page is auto-reloaded when you save".

If however you have opened the folder wherein the file you're working with lies, it doesn't reload the browser when you save.

That's the culprit. That's what I wanted to report as a bug. This is not a feature request.

Nice to see such an active community 👍

[dangoor]

@contradel yes, sorry to hijack your bug for a couple of comments there. The short story is indeed that it should reload when you save JavaScript and anything else is a bug :)

[peheje]

No sweat!
Just wanted to make sure the bug report was clear ;-) Have a nice easter.

2014-04-16 19:06 GMT+02:00 Kevin Dangoor notifications@github.com:

@contradel https://github.com/contradel yes, sorry to hijack your bug
for a couple of comments there. The short story is indeed that it should
reload when you save JavaScript and anything else is a bug :)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/7497#issuecomment-40624985
.

[baursak]

So if I have HTML file with Javascript snippet inside - just saving this "mixed" HTML file after embedded Javascript changes will not cause Chrome to reload? - And this isn't a bug, but rather a feature???

[dangoor]

@baursak No, it's not a feature. The change here would be to make it so that saving an HTML file with changes to inline scripts should reload the page.

[redmunds]

Closing as a duplicate of #5656.