-
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] Quick Edit shows no results if project contains ANY non-UTF8 CSS/LESS/SCSS files #8890
Comments
Comment by RaymondLim
|
Comment by nrennert 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. |
Comment by RaymondLim
|
Comment by nrennert 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 =
|
Comment by RaymondLim 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 |
Comment by nrennert 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. |
Comment by nrennert
|
Comment by RaymondLim
|
Comment by nrennert Here is a screen shot of the simple html file with test.css. |
Comment by RaymondLim
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? |
Comment by nrennert |
Comment by nrennert On another file of mine I get a lot more information on the console. This might help. |
Comment by peterflynn
|
Comment by peterflynn 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. |
Comment by nrennert Here is the screen shot of the call stack. The error is "unsupportedEncoding". Could Brackets have a problem with files that are in utf8? All my files are in utf8, including the css files. |
Comment by RaymondLim Interesting. Can you share one of the utf-8 css files that is causing this failure? |
Comment by nrennert 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. |
Issue by nrennert
Tuesday Nov 25, 2014 at 02:53 GMT
Originally opened as adobe/brackets#10013
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: