Open ukaaa opened 6 years ago
+1 - This has really been annoying me recently.
When I type in margin-bottom for instance it will keep doing the // BUG autocomplete.
+1 Yep driving me nuts type in 'width' and hit tab then the F*#$ing thing replaces it with a god dam "window"....
I've found the autocomplete in CSS/SCSS recently to have become even worse. I also get completely irrelevant suggestions, and, now, there are even suggestions when there shouldn't be such as after typing the ending semicolon. I hit enter to go to the next line and then have to back up because there's random crap now at the end of the previous line after the ;
What's going on here?
Prerequisites
Description
When working inside a .sass file, the autocompletion works, but suggestions contain irrelevant items when autocompleting property values.
And example can be seen in the screenshot below. Why does it suggest "note" when I obviously am more interested in "none". This really slows me down because I can't just blindly hit TAB but I have to look at the suggestions first to make sure I don't pick a wrong one.
Steps to Reproduce
Expected behavior: I expect it to either not show these irrelevant suggestions (which seems to be the default when using a .css or .scss file. Or an alternative could be that it sorts the suggestions in a way that the most relevant one is at the top.
Actual behavior: [What actually happens]
Reproduces how often: [What percentage of the time does it reproduce?]
Versions
Atom : 1.20.1 Electron: 1.6.9 Chrome : 56.0.2924.87 Node : 7.4.0 apm 1.18.4 npm 3.10.10 node 6.9.5 x64 python 2.7.10 git 2.14.1 OS: macOS Sierra