Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Add missing border styles to Tailwind CSS #19112

eduardconstantin started this conversation in Ideas
Discussion options

Currently, Tailwind provides utilities for border-solid, border-dashed, border-double and border-dotted, but some CSS border styles are missing (e.g. groove, ridge, inset, outset). These are part of the CSS spec and could be useful in certain design contexts.
https://developer.mozilla.org/en-US/docs/Web/CSS/border-style

You must be logged in to vote

Replies: 1 comment 3 replies

Comment options

You can already do this via arbitrary properties (no config):

<div class="border-4 border-gray-400 [border-style:groove]"></div>
<div class="border-4 border-gray-400 [border-top-style:groove] [border-right-style:ridge] [border-bottom-style:inset] [border-left-style:outset]"></div>

Preview in Playground


@eduardconstantin Also, I’d suggest opening a feature request under Ideas so the core team can consider first-class utilities.

Feature Request

You must be logged in to vote
3 replies
Comment options

Nice, I didn't knew we can do that.
If it's ok I can create a PR with this feature.

Comment options

Sounds good! Yup, you can close this discussion. A PR would be great, thanks!

Comment options

wongjn Oct 17, 2025
Collaborator

Do be aware of .github/CONTRIBUTING.md:

If there's a new feature you'd like to see added to Tailwind, share your idea with us in our discussion forum to get it on our radar as something to consider for a future release before starting work on it.

Please note that we don't often accept pull requests for new features. Adding a new feature to Tailwind requires us to think through the entire problem ourselves to make sure we agree with the proposed API, which means the feature needs to be high on our own priority list for us to be able to give it the attention it needs.

If you open a pull request for a new feature, we're likely to close it not because it's a bad idea, but because we aren't ready to prioritize the feature and don't want the PR to sit open for months or even years.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Ideas
Labels
None yet

AltStyle によって変換されたページ (->オリジナル) /