You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That's definitely a "pick your poison" kind of situation. If we change the type of the --tw-gradient-via-position variable, you won't be able to animate it anymore but otherwise you can only add one percentage value here. 🤔
If I may suggest, maybe we could split this variable in two? since every color stop has one or two positions, we could use --tw-gradient-via-start-position and --tw-gradient-via-end-position
Nevermind my previous suggestion, just remembered that @Property vars need a default value, so it probably won't work because you can't leave the values blank like in v3 🤔
What version of Tailwind CSS are you using?
v4.0.7
What build tool (or framework if it abstracts the build tool) are you using?
gulp v5.0.0 + Postcss
What version of Node.js are you using?
v20.18.1
What browser are you using?
Brave + Safari
What operating system are you using?
macOS
Reproduction URL
https://play.tailwindcss.com/16SCposb3z
Describe your issue
Using the following class doesn't give the desired result in v4:
bg-gradient-to-r from-sky-500 to-sky-500 via-rose-500 via-[percentage:10%_90%]
v3
v4
The browser considers the property as invalid because it's not a <length-percentage>:
The text was updated successfully, but these errors were encountered: