-
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
Live preview issue - page displayed multiple times #12714
Comments
Comment by peterflynn Here's the code as text, pulled from the newsgroup thread: (@casterle, fyi you can use Markdown formatting syntax to include code in a bug report while preserving formatting)
|
Comment by njx
|
Comment by casterle I haven’t been able to correlate the issue to any specific editing activity. I often don’t notice the issue immediately because the duplication is added to the bottom of the page and is thus sometimes not obvious. Everything I’ve been doing is very simple as one might expect of a student – I’ve not even gotten into the HTML5-specific elements yet. I’ll try to pay more attention to what I am doing when I see the problem in the future. Before reporting the issue I uninstalled and reinstalled both Chrome and Brackets; no joy. From: Narciso Jaramillo [mailto:[email protected]]
— |
Comment by casterle Here's another datapoint. I installed Brackets on a different computer and ran into the same issue. Same versions of Chrome/Brackets. Both computers are i7's running Win7 Ultimate x64 w/latest updates. |
Comment by casterle The problem seems to be caused by jsbeautifier - whenever I beautify my code the issue occurs. I've opened an issue here: taichi/brackets-jsbeautifier#4 |
Comment by njx Hmmm, interesting - thanks for narrowing that down. That might still be our bug - if the only thing jsbeautifier is doing is making simple text edits, we should be able to handle that (especially if it's just changing whitespace). I'm going to reopen this so we can see if it's on our end. |
Comment by jeremy-beliez The bug is always here (taichi/brackets-jsbeautifier#4 and brackets-beautify/brackets-beautify#49). So beautifier are unusable. Is it possible to have a working built-in beautifier option in Brackets ? Thanks. |
Comment by Hirse The same issue appears on my beautify-fork: Hirse/brackets-beautify#14 As far as I was able to find out, this is the same as this Brackets issue: adobe/brackets#10634 |
Comment by bplus Has anyone seen a fix for this? I'm experiencing the same thing. |
Comment by Hirse Added a work-around here: Hirse/brackets-beautify@3b9dc39 Should be available in the latest version of https://github.com/brackets-beautify/brackets-beautify. |
Comment by cdokolas I have this problem only when I save the file. Brackets Release 1.7 build 1.7.0-16898 (release b0a363b71) Observations: With developer mode on, I see something like this:
I then have to turn off developer mode and re-enable live preview, because developer mode closes live preview. After a small edit and "save", I see this (in developer mode):
What I've found out is that, as long as I don't cause live preview to stop, I can reload the page and get the right content. It looks like saving the document clears and re-generates the internal node ids, which the live preview updating engine can't find and ends up just creating and appending new nodes to the document. So, the only workaround is to also reload the page every time I save... |
Comment by imiMike I've got the same issue in Release 1.9 build 1.9.0-17312 (release 189f6d39a) |
Issue by casterle
Tuesday Jun 17, 2014 at 18:50 GMT
Originally opened as adobe/brackets#8151
I'm using Brackets sprint 40 with Chrome 35.0.1916.153m. The problem I'm having is that sometimes Chrome does not update the displayed page, but instead postpends my changes to the bottom of the existing page.
For example, if I have a page that displays:
and I edit the page in Brackets, sometimes Chrome will display:
This occurs fairly often, perhaps 10% of my edits; refreshing the page fixes the issue. I just learning HTML/CSS so all of my pages to date have been static.
Here's the HTML that most recently caused the issue:
BTW, Brackets is an outstanding learning tool! Thank you all for such a great gift!
The text was updated successfully, but these errors were encountered: