Open ivanpajon opened 1 day ago
Unfortunately for now it can’t work like that, the parser in PostHTML doesn’t support not closing tags out of the box, it’ll close them automatically. That’s why we don’t have such examples in the tag’s docs.
The reason it exists is so that you can use Tailwind classes or tags/attributes from Maizzle inside of it, before it gets turned into a string. Parsers don’t treat strings as HTML, they just return them as-is.
If we can ever find a way to make it work as you described, I’d be more than happy to do it :)
And also would be nice to have posibility to specify IE in outlook tag.
What would be the use case? All Outlooks that support MSO conditionals (2006-2021) work with the current if mso
statement.
What would be the use case? All Outlooks that support MSO conditionals (2006-2021) work with the current
if mso
statement.
I'm not an expert in html emails, but most examples I found use <!--[if (gte mso 9)|(IE)]>
but I don't know if it is really necessary the "IE".
I think tag has some weird behavior. When using legacy comments like tag the content of some of them are rendered outside the comment and breaks the html tree.
<!--[if (gte mso 9)|(IE)]><![endif]-->
content inside that comments are rendered properly in browser. But when I switch toCode with legacy comments:
Rendered html in browser (good):
Code with outlook tags:
Rendered html in browser (bad):
And also would be nice to have posibility to specify IE in outlook tag.