Skip to content

Show percentage result like in V3 #1314

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
stormynight9 opened this issue Apr 14, 2025 · 2 comments · Fixed by #1316
Closed

Show percentage result like in V3 #1314

stormynight9 opened this issue Apr 14, 2025 · 2 comments · Fixed by #1316
Assignees
Labels
enhancement New feature or request

Comments

@stormynight9
Copy link

What version of VS Code are you using?

Cursor v0.48

What version of Tailwind CSS IntelliSense are you using?

v0.14.15

What version of Tailwind CSS are you using?

v4.0.15

What package manager are you using?

npm

What operating system are you using?

Windows

Tailwind config

// Paste the contents of your Tailwind config file here

VS Code settings

// Paste your VS Code settings in JSON format here

Reproduction URL

You can try it here: https://play.tailwindcss.com/

Describe your issue

in V3 I used to get the actual percentage here:

Image

in V4 I don't get them anymore

Image

@thecrypticace thecrypticace self-assigned this Apr 14, 2025
@thecrypticace thecrypticace added the enhancement New feature or request label Apr 14, 2025
@thecrypticace
Copy link
Contributor

thecrypticace commented Apr 14, 2025

Hey, thanks for reporting this. This is due to the way v4 generates these values and relies on minification to simplify them. Will look into addressing this.

Notes for me for later:

  • We'll need to add fractions & percentage value evaluation when lowering calc(…) expressions
  • We're probably at the point where we need a more generalized AST structure for these values
  • Need a more generalized calc(…) solver that can handle more value types
    • Maybe look at how lightning CSS lowers and simplifies calc expressions
    • Ideally we could optimize them in IntelliSense as much as possible for the purposes of completion details

@thecrypticace
Copy link
Contributor

The fix for this will go out in the next release of IntelliSense. I'm aiming to do that possibly tomorrow if not earlier.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
2 participants