Replies: 2 comments 1 reply
-
Hey! Try the https://github.com/tailwindlabs/tailwindcss-typography/blob/master/src/index.test.js#L335 Sort of a secret API, have kept it quiet just to get a better sense of how many people actually need it by waiting for issues like this to pop up. |
Beta Was this translation helpful? Give feedback.
1 reply
-
thanks, this was really helpful! I was trying the whole day to get purgecss to remove all the bloat from the typography plugin, but it seems to have trouble with the conditional syntax. activating the legacy option solved it. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm using @tailwindcss/typography along with Maizzle, to craft emails. I'm using sendgrid to send these emails. I'm using the
prose
functionality in the@tailwindcss/typography
plugin, in order to ensure the emails look great.There are a handful of CSS elements that Maizzle produces, when used with
@tailwindcss/typography
, which strip all CSS from the resulting email. For example, ifol[type="a" s]
is included in the email's CSS, the email style gets stripped.I've been getting around this by modifying the Tailwind typography plugin defaults to disable these styles:
This worked great.
I upgraded to the latest Typography version (0.5.2), and there's a new addition of the
not-prose
class to disable prose styles selectively. The resulting CSS in the email that Maizzle produces now has these classes:This causes the email CSS to break:
Removing this CSS from the email, and re-sending it, causes the styles to look completely normal:
It doesn't appear possible to disable the
not-prose
classes from being generated. There's nothing in the defaults to override. It'd be great to add functionality to disable this.Beta Was this translation helpful? Give feedback.
All reactions