tailwindcss-forms
A plugin that provides a basic reset for form styles that makes form elements easy to override with utilities.
by tailwindlabsHTML
Commit activity
Last 12 weeks · 1 commit
Community health
2 of 6 standards met
37
✓README✓License○Contributing○Code of Conduct○Issue Template○PR Template
Recent PRs & issues
Active · 1 in progress · Last activity 1mo ago
See all on GitHub →
This updates the checkbox/radio examples to use when showing checked-state colors, and adds a short note for the + checked state case. The current examples show for checkbox color. With the custom appearance styles in this plugin, native utilities do not control the rendered checked background, and in Tailwind CSS v4 an unchecked can make that especially confusing. works for the checked background in both v3 and v4. Checked: Tailwind CSS v3.4.13 fixture build Tailwind CSS v4.3.0 fixture build Browser computed-style check on the v3/v4 fixtures through Related to #184.
What version of @tailwindcss/forms are you using? v0.5.11 What version of Node.js are you using? v22.22.0 What browser are you using? Chrome, Firefox What operating system are you using? Fedora Reproduction repository https://play.tailwindcss.com/2lY3Z2TaqM Describe your issue I'm unable to set the background color of a checkbox or radio input. See the following example: https://play.tailwindcss.com/2lY3Z2TaqM When removing the class it does work. Also, in Tailwind V3 I didn't have this issue so I'm guessing it introduced with V4.
What version of @tailwindcss/forms are you using? v0.5.7 Describe your issue I read the discussion https://github.com/tailwindlabs/tailwindcss-forms/issues/22. The thread has been closed by adding strategy. Sorry to bring this up again However, the strategy is not easily overridable because it was placed later in the CSS file (at the components layer). No matter the strategy used, should always be a base, ready to be overridden by other stylings. Why the need for overrides? I can't talk for others, as you'll see some of them on the discussion links above, but for me, adds colors that almost always need overriding because they stand out like sore thumbs. What should we do? Can we move CSS declarations of strategy from layer to layer? Basically, modify the code here: https://github.com/tailwindlabs/tailwindcss-forms/blob/c9d9da3e010b194a1f0e9c36fbd98c83e4762840/src/index.js#L353 from to . Why do I, or other similar people, use at all? has its ecosystem, and some 3rd-party components expect to be there as the base. We still want to work with and the people creating those components, even if we are not a fan of the approaches.
Recent fixes
This PR sets up OIDC publishing by merging the workflows first
Currently the rules for styling the inputs are too broad and may conflict with web components that use props named type or mutiple. This PR address this issue by using :where to select only inputs without change the specificity.
What version of @tailwindcss/forms are you using? v0.5.10 What version of Node.js are you using? v22.14.0 What browser are you using? Chrome What operating system are you using? macOS Reproduction repository https://github.com/farseekers/tailwind Describe your issue When running in a minimal-reproduction repository with SCSS and postcss.config.mjs the following warning appears in my console A PostCSS plugin did not pass the option to . This may cause imported assets to be incorrectly transformed. If you've recently added a PostCSS plugin that raised this warning, please contact the package author to fix the issue. I understand I might be doing something wrong. I will say this only started happening with tailwindcss 4.1.6. Thanks for any help.
Structured data for AI agents
Repository: tailwindlabs/tailwindcss-forms. Description: A plugin that provides a basic reset for form styles that makes form elements easy to override with utilities. Stars: 4565, Forks: 230. Primary language: HTML. Languages: HTML (57.1%), JavaScript (42.9%). License: MIT. Homepage: https://tailwindcss-forms.vercel.app Latest release: v0.5.11 (6mo ago). Open PRs: 1, open issues: 3. Last activity: 1mo ago. Community health: 37%. Top contributors: adamwathan, thecrypticace, RobinMalfait, reinink, chasegiunta, philipp-spiess, bradlc, hyunbinseo, simonswiss, saibotk and others.