You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In one of the later releases, there was a change which made some characters like < and >, be encoded if they were found within a HTML comment.
We experience that this breaks MSO conditional comments, which uses HTML comment to "hide" the Outlook specific parts.
For example this:
<h1>Hello</h1><!-- Normal comment --><!--[if mso]>
<table><tr><td>
<p>This information will display only in Microsoft Outlook.</p>
</td></tr></table>
<![endif]-->
becomes the following after being sanitized:
<h1>Hello</h1><!-- Normal comment --><!--[if mso]>
<table><tr><td>
<p>This information will display only in Microsoft Outlook.</p>
</td></tr></table>
<![endif]-->
and Outlook does not seem to understand when the HTML within the conditional comment is encoded.
Is there anything that can be done with this?
The text was updated successfully, but these errors were encountered:
I've created a property EncodeComment to customize the encoding of comments similar to what has been done for #511. Watch out for possible bypasses if you override the default behavior (see GHSA-43cp-6p3q-2pc4).
In one of the later releases, there was a change which made some characters like < and >, be encoded if they were found within a HTML comment.
We experience that this breaks MSO conditional comments, which uses HTML comment to "hide" the Outlook specific parts.
For example this:
becomes the following after being sanitized:
and Outlook does not seem to understand when the HTML within the conditional comment is encoded.
Is there anything that can be done with this?
The text was updated successfully, but these errors were encountered: