Skip to content

Support autocomplete in additional variants. #1257

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
smhmd opened this issue Mar 6, 2025 · 1 comment · Fixed by #1263
Closed

Support autocomplete in additional variants. #1257

smhmd opened this issue Mar 6, 2025 · 1 comment · Fixed by #1263
Assignees
Labels
bug Something isn't working

Comments

@smhmd
Copy link

smhmd commented Mar 6, 2025

What version of VS Code are you using?

v1.97.2

What version of Tailwind CSS IntelliSense are you using?

v0.14.8

What version of Tailwind CSS are you using?

v4.0.11

What package manager are you using?

pnpm

What operating system are you using?

macOS

Tailwind config

/* n/a */

VS Code settings

{
  "files.associations": {
    "*.css": "tailwindcss"
  }
}

Reproduction URL

Please, insist on this and I will make a reproduction repo

Describe your issue

The following instances don't trigger autocompletion (| is the cursor)

  • has-[button]:|
  • data-[size=large]:|
  • supports-specific-css-feature:|, supports-[display:grid]:|
  • not-supp| (not-support: does autocomplete after you type it, but not before)
@thecrypticace
Copy link
Contributor

I'm gonna get a release out soon with this fixed

The not-supp| case is harder and will require some more work in Tailwind CSS core. I need to redesign the internal API we use in Tailwind CSS itself to support interactive variant suggestions

I have some ideas for this but they won't happen until at least Tailwind CSS v4.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants