Breaking change after upgrade related to border-color
See original GitHub issueWhat version of Tailwind CSS are you using?
v2.2.6
What build tool (or framework if it abstracts the build tool) are you using?
webpack 5.37.0
What version of Node.js are you using?
v14.1.0
What browser are you using?
Chrome
What operating system are you using?
Linux
Describe your issue
This line has a huge impact on the default styles and it was removed on the recent version. Most Tailwind examples out there uses something like:
<div class="text-black">
<div class="border">
<!-- Expected: border should not be black -->
</div>
</div>
And it was used by the hr
tag as well. Please, revert this change if possible. Thank you!
Issue Analytics
- State:
- Created 2 years ago
- Reactions:4
- Comments:14 (6 by maintainers)
Top Results From Across the Web
[system] borderColor not respected anymore #16995 - GitHub
After the upgrade from 4.3.1 to 4.3.2 the borderColor prop doesn't get respected anymore on a Box , at least for the following...
Read more >border-color - CSS: Cascading Style Sheets - MDN Web Docs
The border-color shorthand CSS property sets the color of an element's border.
Read more >Visual Breaking Change in Design Systems - Medium
After the system change, the color contrast is no longer accessible. Your system broke their product. Imagine your system's minor release ...
Read more >Breaking changes in v5, part two: core components - Material UI
Replace background-color with border-color. Use border-color instead of background-color . This prevents inconsistent height on scaled ...
Read more >HTML DOM Style borderColor Property - W3Schools
Change the color of the four borders of a <div> element to red: document. ... The borderColor property sets or returns the color...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yeah we’ll see, the main problem is it was causing the Tailwind CSS homepage to take over 3 seconds to load in Safari, and now it loads in a few hundred milliseconds. Mainly effects pages with a huge number of DOM nodes (our homepage is almost 7000).
@adamwathan You rock! I’m going to test it as soon as possible.