Documentation Example Missing Acceptable Values #17991
Unanswered
domtripodi
asked this question in
Help
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
You are free to let me know if I am blind or stupid with this query.
Prior to Tailwind 4, documentation for properties such as height, width, size etc. specified all options that existed within Tailwind. Then the documentation provided examples as expected.
Tailwind 3.4.17 (before)

Now Tailwind 4 specifies the acceptable type (e.g. number, fraction...) but does not provide an entire list of options.
Tailwind 4 (after)

My understanding from release notes is that it now accepts any number and will treat an odd number like w-17 as an arbitrary value and work out the box. If this is the case, does that not defeat the purpose of the principles stated in Refactoring UI.
Arbitrary values avoided unless completely necessary which gives a more finite range of values to use. This then keeps designs consistent and neat, especially for responsive design.
Could someone else with their expertise shed some light on this as I am a bit confused and open to another perspective.
Also, I love TailwindCSS and have loved the updates in version 4, just am confused at the above.
Beta Was this translation helpful? Give feedback.
All reactions