You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Default stylesheet looks more like a page one than a component one, with a lot of resets, defaults, etc. It had some minor side effects over other styles in my page, but nothing critical. I guess this is related with the new tailwind-based styles and will be improved in the future.
we have some issue related to the disabling: we should have saved in another file the reset css, because in most cases people need the reset in their application, for example, our html-template should import the preflight. In the rest it should be optional, because people probably have imported normalizer from other sources and we cannot "break" their styles.
So we should produce two css:
with reset
without reset - with name {name of theme}.reset.min.css
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity 😴
It will be closed in 60 days if no further activity occurs. To unstale this issue, add a comment with detailed explanation.
Thank you for your contributions ❤️
Description
Regarding to this comment #177 (comment):
we should disable the default css normalizer (css reset) from final styles produced by TailwindCSS. We can use the https://tailwindcss.com/docs/preflight#disabling-preflight option, but...
we have some issue related to the disabling: we should have saved in another file the reset css, because in most cases people need the reset in their application, for example, our html-template should import the preflight. In the rest it should be optional, because people probably have imported normalizer from other sources and we cannot "break" their styles.
So we should produce two css:
{name of theme}.reset.min.css
The text was updated successfully, but these errors were encountered: