Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
How do you whitelist attribute selectors in email-comb?
See original GitHub issuePackage’s name
email-comb
Describe the situation
How do I prevent it from removing this CSS?
@media (max-width: 600px) {
[data-ogsc] .sm-text-red-500 {
color: #ef4444;
}
}
Issue Analytics
- State:
- Created 2 years ago
- Comments:15 (9 by maintainers)
Top Results From Across the Web
CSS attribute selectors are removed even when whitelisted
So I thought using a whitelist pattern would "solve" it, but even with a white list pattern (e.g. whitelistPatterns: [/company-colors/]) the ...
Read more >email-comb - npm
Remove unused CSS from email templates. ... Start using email-comb in your project by running `npm i ... Options - opts.whitelist.
Read more >Attribute selectors - CSS: Cascading Style Sheets | MDN
The CSS attribute selector matches elements based on the presence or value of a given attribute.
Read more >Code Cleanup - Framework for Rapid Email Prototyping
Resetting email client styles is often done through CSS selectors that do not exist in your email's code - whitelist ensures these selectors...
Read more >How to allow and configure the whitelist for the HTML output ...
This article provides steps for allowing HTML and configuring the whitelist for HTML output on a selector.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Sure, I’ll try. Reopening.
apparently, Node 17 is not entirely stable; normal unit tests were failing with
error:0308010C:digital envelope routines::unsupportederror — I’ll switch to node 16 on CI and try to publish again