Intellisense does not show up in a certain scenario on Ubuntu 21.10

[hunghvu]

What version of Tailwind CSS IntelliSense are you using?

v0.7.7

What version of Tailwind CSS are you using?

v3.0.23

What package manager are you using?

npm

What operating system are you using?

Ubuntu 21.10

Reproduction URL

No existing codebase, I only install the extension to try out its features using a few lines of code. If a codebase is required, then it is a fresh install of NextJS and TailwindCSS.

Describe your issue

It seems an auto-complete panel does not show up in a certain scenario and can be seen in point (3) below. I also tried out in a fresh VM instance with a fresh VS Code installation (latest - v1.64.2), but the result is the same. It is not a deal-breaker but surely reduces user experience.

1. The panel shows up if there is no closing quote.
   
   

2. If there is a closing quote, there must be a space before a class name to make the panel shows up.
   
   

3. If there is a closing quote, and no space before a class name, the panel does not show up.
   
   

4. I did check for online examples, and point (3) should not happen.
   
   An example is from this Youtube video

[hunghvu]

Update

I tried again with Windows 10, and it seems the bug is not there. Perhaps the issue is on VS Code - Ubuntu itself? However, I noticed another issue that might be related to the one above.

Another issue description

The autocomplete panel randomly disappears. It mostly happens when a non-existing class name is typed in. After the disappearance, it cannot be triggered again. The demonstration can be seen in the video below.

1.mp4

Expected behavior

I expect the autocomplete panel to reappear after a mistake in name is fixed. The example of that behavior can be seen in the video below. Note, this uses Python IntelliSense by Microsoft, and this is a normal behavior in several other plugins too.

2.mp4

[bradlc]

Hey @hunghvu. I'm pretty sure this is due to how VS Code handles completions in "string" contexts. Setting editor.quickSuggestions.strings to true should improve this:

"editor.quickSuggestions": {
  "strings": true
}

[hunghvu]

Hey @hunghvu. I'm pretty sure this is due to how VS Code handles completions in "string" contexts. Setting editor.quickSuggestions.strings to true should improve this:

"editor.quickSuggestions": {
  "strings": true
}

Great solution! It's still a bit glitchy as shown above but still, much better behavior than before. Anyway, I can certainly live with this.