-
Sample Repo: https://github.com/PsyGik/try-tailwind-psuedo-issue Steps to Replicate:
Versions:
|
Beta Was this translation helpful? Give feedback.
Answered by
wongjn
Aug 13, 2022
Replies: 1 comment 1 reply
-
Seems to be a bug in
This results in an erroneous rule as the following: .dark .dark\:prose :where(ol li,ul li):not(:where([class~="not-prose"] *))::before,::before {
/* … */
} In particular, the lone WorkaroundAs a workaround for now, you can slightly tweak the config CSS to be like the following: - 'ol li::before,ul li::before': {
- // …
+ 'ol li, ul li': {
+ '&::before': {
+ // …
+ },
}, Edit: opened an issue at tailwindlabs/tailwindcss-typography#280 |
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
PsyGik
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Seems to be a bug in
@tailwindcss/typography
when the following criteria are met:::before
rules in the same selector (in your case, theol li::before,ul li::before
)darkMode
set toclass
dark:prose
class existsThis results in an erroneous rule as the following:
In particular, the lone
::before
selector at the end (minimum reproduction Tailwind Play).Workaround
As a workaround for now, you can slightly tweak the config CSS to be like the following:
Tailwind Pla…