-
Notifications
You must be signed in to change notification settings - Fork 7.6k
Quick Edit shows no results if project contains ANY non-UTF8 CSS/LESS/SCSS files #10013
Comments
@nrennert Did you use File > Open Folder to open the root folder of your file as the project root? If not, then you won't be able to use Quick Edit by just opening the file. |
Yes, I opened the whole folder and then opened the file by double clicking on it in the File Tree view. The Live Preview works but not html file. Quick Edit does work in the css file though. |
@nrennert Can you provide some sample HTML code with steps to reproduce so that we can understand what is not working for you? |
I tried it on a super simple html page (saved to the same folder) and a super simple css file (saved to css/test.css) without success.
css file =
|
I corrected your html and css sample code and wrap them with three backticks to show them as code blocks. And I also try it by placing the cursor inside the |
no, I've tried it with several different files; several I'm working on and then I also created this very short and simple test file. Nothing has worked. |
|
@nrennert Can you take a screenshot that include left sidebar, menu and your cursor position in the html file so that we can see what went wrong with your testing? Below is a sample screenshot showing Quick Edit not working when I invoke it in the body tag of a not-yet-saved new file. Are you getting a message popup as in my screenshot? |
@nrennert Can you open Developer Tools (Debug > Show Developer Tools) and look into Console tab? And tell us whether you see any errors or warnings in there. You mentioned that Ctrl+E is working in CSS file for colors. Can you try one more thing in a CSS file by pressing Ctrl+T? See do you get a list pop up on the top right corner showing all the selectors in your css file? |
@nrennert Can you try this?
|
If my read of this is correct, the issue is that So, we should make Quick Edit similarly robust to file IO errors. Although since we're filtering on file extension in this case, read errors are a little more unexpected (vs. FindInFiles where we could easily encounter binary files with unknown extensions) -- so I think in this case we should log a warning to the console instead of being 100% silent. |
Interesting. Can you share one of the utf-8 css files that is causing this failure? |
I've just tested the utf8 possibility and it does not make a difference. Even with the html and css file both being in ANSI my version of Brackets still doesn't have the Quick Edit function. |
@nrennert UTF-8 is actually the only encoding that Brackets does support. So if you have even a single CSS/SCSS/LESS file that is in some other encoding (including ANSI), then this bug will prevent Quick Edit from working. |
…project contians any non-UTF8 CSS/LESS/SCSS files) - Silently ignore files that can't be read, and continue the search anyway (warning logged to console, but no user-visible error shown). Similar to what we've always done for Find in Files. With unit test, and matching test for the pre-existing same behavior in Find in Files. Also clean up dated use of waitsFor() in the CSSUtils test spec.
Posted a fix for the encoding issue, which is presumably what's going on here (and is definitely a real issue regardless) |
Semi-fix bug #10013 (CSS Quick Edit provider does not respond if project contains any non-UTF8 CSS/LESS/SCSS files)
@nrennert The fix for this should be in 1.1. Please try that out when 1.1 is released and reopen this issue if you're having the same problem. |
Clarifying title |
Im in linux parrot sec as a root user |
I'm using Win 7 Home/64bit. I've installed Brackets version 1.0 build 1.0.0-15191 twice; first time with no extensions, the second time it was a fresh install with Extract for Brackets installed. In both installs I tried to use the Ctrl+E, right-click and choose Quick Edit and tried the menu. In neither case did the function work. I did get it to work on a css file when I tried to change a color. In that case I used the Ctrl+E shortcut. I would love to use this feature; any help to figure out why it doesn't work would be great.
I tried using it on a bare bones html file with a very short and simple css file and it still didn't work.
The text was updated successfully, but these errors were encountered: