Autocomplete double quotes issue
Opened this issue · 1 comments
Prerequisites
- Put an X between the brackets on this line if you have done all of the following:
- Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
- Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
- Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
- Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
- Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages
Description
When autocompleting a tag attribute, the cursor jumps inbetween the autocompleted double quotes. If another double quote is input, rather than skipping over the closing double quote, another double quote is created. Meaning, if using autocomplete to import a tag attribute, after naming the attribute, one would have to use the arrow keys to move the cursor out of the double quotes, as opposed to being able to input a "closing" double quote, to skip over the imported closing double quote.
Steps to Reproduce
- Go to any HTML document
- Start a html tag (i.e. <div)
- Start typing a html tag attribute (i.e. class)
- Autocomplete the tag attribute.
- Your cursor should now be inbetween the autocompleted double quotes.
Expected behavior: At this point, if I put in another double quote, I'd expect that my cursor would skip over the existing closing double quote.
Actual behavior: Another double quote is input, rather than the cursor skipping over the existing one.
Reproduces how often: 100%
Versions
apm 1.19.0
npm 3.10.10
node 6.9.5 x64
atom 1.25.1
python 2.7.10
git 2.15.1
OS: macOS 10.13.4
Additional Information
Any additional information, configuration or data that might be necessary to reproduce the issue.
edit: this might actually be an issue for the autocomplete-plus package, as this same issue is present regardless of the language for which autocomplete is being used.
I'm in trouble about this issue too :(