-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CLOSED] Dirty dot no longer appears when JS or server file is edited #4894
Comments
Comment by njx Reviewed. To me, medium priority |
Comment by njx Nominating for sprint 35 |
Comment by njx It looks like the issue is that in
(As a side note, it looks like the comment for |
Comment by njx
|
Comment by jasonsanjose Those changes look good. The server is ready before the inspector is connected. Thanks for finding that bug, sorry that I missed those |
Comment by njx Yeah, not sure. It seems like we rely on URLs even for non-live docs, though, at least in this case. |
Comment by jasonsanjose Confirmed fixed. Closing. |
Issue by njx
Tuesday Sep 24, 2013 at 00:43 GMT
Originally opened as adobe/brackets#5317
<script>
tag referring to a JS fileResult: No dirty dot showing that the live preview is out of sync. This used to work. It's also broken for HTML files that are served from a user server (where live editing isn't enabled).
The text was updated successfully, but these errors were encountered: