You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Start Brackets, open "Getting started" Project, and restart Brackets (you may restart it without extension as well)
Quickly launch Live Preview and wait for the window to load
Open Brackets' DevTools (F12) then
Result:
The browser window uses the file:/// protocol. Therefore, pushing changes won't work. There is at least one error logged in the console.
Expected:
The Live Preview should use the Live Preview server.
The text was updated successfully, but these errors were encountered:
Comment by redmunds Wednesday Aug 13, 2014 at 22:28 GMT
@MarcelGerber How quickly do you have to do step 2? It sounds like the nodejs server has not yet started because the fall-back is to open page with file:// protocol.
Comment by MarcelGerber Wednesday Aug 13, 2014 at 22:46 GMT
Guess it's 5 to 15 seconds. But even if the node server isn't started yet, we can still do something better (like a longer waiting time).
And btw, this issue causes a console.error that we can probably avoid.
Comment by redmunds Wednesday Aug 13, 2014 at 23:30 GMT
I am not sure if we can tell the difference between "nodejs server is still initializing" and "nodejs server is down" cases. We might just need to document this in Troubleshooting page.
Wednesday Aug 13, 2014 at 22:02 GMT
Originally opened as adobe/brackets#8755
Result:
The browser window uses the file:/// protocol. Therefore, pushing changes won't work. There is at least one error logged in the console.
Expected:
The Live Preview should use the Live Preview server.
The text was updated successfully, but these errors were encountered: