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
{{ message }}
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.
I'm running Windows 7 with the latest Sprint 31, installed from the online-provided MSI. Everything works as intended, with the exception of live HTML viewing. The Brackets console gives me an error immediately after opening the live development window.
HTML always updates on save as is intentional, and CSS always updates as I type - but the new HTML updating feature, without looking at the console, seems absent.
Here's the recipe:
Version of Brackets:
I've cleared the Brackets console before we start.
Start with blank 'index.html' and blank project. Project settings are set correctly to the right folder.
Insert basic HTML template with no content.
Enable Live Development.
Gives us a blank window, as expected.
Insert content into body tags.
HTML does not update.
Save the current 'index.html' file and the preview updates as was normal in previous Brackets builds.
Insert invalid HTML in an effort to get Live Development to throw an error and complain about invalid HTML. Do not save the file. (The below screenshot doesn't contain invalid HTML as I realized after posting this, but I tried it without the space between the open tag and 'abc'. The HTML definitely becomes invalid but Brackets still doesn't complain.
The page stays the same, no HTML updating. Does not complain about any errors.
Save the file.
Content updates as is expected. No errors from the Live Development so far.
Check the Brackets console window.
The "recursive test" issues happen, but not always. The one that seems to pertain to the Live Development window is the GET request which seems to be having some issues.
The text was updated successfully, but these errors were encountered:
@frizkie Thanks for logging bugs! Does this similar issue describe the bug you're seeing? If not, can you describe the kind of edits you're trying to make? It would also be helpful to see one of the (simplest) files you are trying to edit if you can post a link or a gist (or even paste here if small enough).
@taylorthurlow I can see the problem. Live HTML (and also Live Highlighting) are not supported for User Servers (e.g. localhost). I am going to close this issue. Let me know if you have any questions.
I'm running Windows 7 with the latest Sprint 31, installed from the online-provided MSI. Everything works as intended, with the exception of live HTML viewing. The Brackets console gives me an error immediately after opening the live development window.
HTML always updates on save as is intentional, and CSS always updates as I type - but the new HTML updating feature, without looking at the console, seems absent.
Here's the recipe:
Version of Brackets:
I've cleared the Brackets console before we start.
Start with blank 'index.html' and blank project. Project settings are set correctly to the right folder.
Insert basic HTML template with no content.
Enable Live Development.
Gives us a blank window, as expected.
Insert content into body tags.
HTML does not update.
Save the current 'index.html' file and the preview updates as was normal in previous Brackets builds.
Insert invalid HTML in an effort to get Live Development to throw an error and complain about invalid HTML. Do not save the file. (The below screenshot doesn't contain invalid HTML as I realized after posting this, but I tried it without the space between the open tag and 'abc'. The HTML definitely becomes invalid but Brackets still doesn't complain.
The page stays the same, no HTML updating. Does not complain about any errors.
Save the file.
Content updates as is expected. No errors from the Live Development so far.
Check the Brackets console window.
The "recursive test" issues happen, but not always. The one that seems to pertain to the Live Development window is the GET request which seems to be having some issues.
The text was updated successfully, but these errors were encountered: