Replies: 1 comment
-
Hey! This is how Tailwind CSS worked basically from the beginning, changing this now will result in breaking changes. If you want, you can always add CSS to change the defaults. E.g.: @layer base {
*,
::after,
::before,
::backdrop,
::file-selector-button {
border-style: none;
}
} |
Beta Was this translation helpful? Give feedback.
0 replies
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.
-
What version of Tailwind CSS are you using?
Both 3.x and 4.x
What build tool (or framework if it abstracts the build tool) are you using?
No matter
What version of Node.js are you using?
No matter
What browser are you using?
Chrome
What operating system are you using?
Windows
Describe your issue
Pull Request #116
border-style: solid;
may introduce unintended side effects in certain contexts. For instance, when users copy content from a webpage into Microsoft Word, they may encounter unexpected visible lines—these stem from borders defined in the HTML. Specifically, some HTML-to-DOC conversion tools do not interpret aborder
with zero width andsolid
style (e.g.,border: 0 solid;
) as visually absent; instead, they render it as a visible border. While settingborder-style: none
can prevent this rendering artifact, it disrupts components relying on utility-first frameworks like Tailwind CSS, where border visibility is controlled exclusively viaborder-width
utilities (which implicitly assume a defaultborder-style: solid
). This creates a conflict between document interoperability and component integrity. Are there established strategies or workarounds to resolve this issue?Beta Was this translation helpful? Give feedback.
All reactions