fix an issue with tailwindcss
fix an issue #13
Thank you for your contribution.
If I remember correctly, with this change, the computation will not work correctly anymore, because the border heights will simultaneously count towards one and the other row height. Use the requireBorderCollapse property instead, since that switches the way the computation works, see here.
Feel free to suggest a change in the documentation if you agree and think that it was not yet documented properly.
On a side note, I would have recommended to simply override this styling in your own stylesheet (you can e.g. add a class to the table and refer to it that way), rather than requiring every user of this library to have that styling, it's not like everyone is using tailwindcss.
In my case, toggling requireBorderCollapse didn’t work well, so I analyzed each affecting style declaration and realized that fixing this improves the situation. This might only apply when using Tailwind CSS.
I will look for a better solution!
I will look for a better solution!
You get this solution also e.g. using
<VirtualTable className={myClass} …
<!-- some other code -->
<style>
.myClass {
border-collapse: initial !important;
}
</style>