-
Notifications
You must be signed in to change notification settings - Fork 293
No way to unset .not-prose without using Tailwind config #390
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hey! Something we've been tinkering with (while looking at building a CSS-only version of the Typography plugin) was to do this instead: @utility prose {
:not(:where([class~='not-prose'], [class~='not-prose'] *)) {
h1 {
color: red;
}
}
} The |
That still doesn't look right to me. Here's what I'd expect using the v3 config https://play.tailwindcss.com/krKYNAX0AV |
My bad, the @utility wysiwyg {
:not(:where([class~='not-wysiwyg'], [class~='not-wysiwyg'] *)) {
&:where(h1) {
color: red;
}
}
} https://play.tailwindcss.com/ADGo1nkQNt?file=css Looks like I copied it wrongly from the CSS-only exploration that I mentioned earlier 🙈 |
Ah, yes, this looks great. Looking forward to it! |
What version of @tailwindcss/typography are you using?
v0.5.16
What version of Node.js are you using?
v20.15.1
What browser are you using?
Brave Version 1.76.73 Chromium: 134.0.6998.45 (Official Build) (arm64)
What operating system are you using?
macOS 15.1.1 (24B91)
Reproduction repository
https://play.tailwindcss.com/B72CiZiVnw?file=css
Describe your issue
Looking through past issues, it seems like this is a potentially viable solution for customizing the prose plugin; however using
.not-prose
in this case won't unset styles defined in@utility prose
.It's mentioned a few times in various places, but just to make it clear: as of writing, in order to customize the typography plugin, you must use the Tailwind config.
Hopefully, this issue can help track the state of supporting customizing the prose plugin in a "v4 way".
The text was updated successfully, but these errors were encountered: