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
In order to overwrite the global preflight style, tailwindcss requires local CSS to be loaded after the global styles, see tailwindlabs/tailwindcss#6602 (where the button issue is discussed).
Unfortunately, elm-tailwind-modules can’t control the ordering of the final CSS, because that’s in the user’s control with elm-css. I’m working on fixing that.
This issue keeps track of this problem.
In the following example (using elm-default-tailwind-modules 4.0.1), the button has a transparent background despite having a different local background definition:
The default tailwind "preflight" global styles include definitions with high specificity, e.g.:
In order to overwrite the global preflight style, tailwindcss requires local CSS to be loaded after the global styles, see tailwindlabs/tailwindcss#6602 (where the button issue is discussed).
@matheus23 states in an elm discourse thread that we can't do this right now in elm-tailwind-modules:
This issue keeps track of this problem.
In the following example (using elm-default-tailwind-modules 4.0.1), the button has a transparent background despite having a different local background definition:
@matheus23 also mentions a workaround in the discourse thread - use
See also: #7
The text was updated successfully, but these errors were encountered: