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
{{ message }}
Repository navigation
Maybe a bug? Opening <a tag is stripped from HTML body when the YAML block is folded (>-)
#13
Recipient/provider: GMX (verified in the raw sent message, so not provider-related)
Summary
When the html payload is written as a YAML folded block (>-), the opening <a of an anchor tag is missing from the message that is actually sent. The
closing </a> survives. With a literal block (|-) and identical markup,
the anchor is sent correctly.
Steps to reproduce
Call email_notifier.send from Developer Tools → Actions.
Only the opening <a is removed; </a> is untouched, so a tag allow-list
filter seems unlikely.
There is a single space between <p> and href, exactly where the YAML line
break was. YAML folding therefore worked as specified and the string handed to
the integration should have been <p><a href="...">. Something after that
point removes the two characters <a.
The only difference between A and B after YAML parsing is line breaks vs.
spaces elsewhere in the string.
Side observation
The text/plain alternative part of the generated message is empty (an empty
base64 block) when only html is supplied. Clients that prefer plain text show
nothing at all.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Environment
Summary
When the
htmlpayload is written as a YAML folded block (>-), the opening<aof an anchor tag is missing from the message that is actually sent. Theclosing
</a>survives. With a literal block (|-) and identical markup,the anchor is sent correctly.
Steps to reproduce
Call
email_notifier.sendfrom Developer Tools → Actions.Case A — works:
Case B — broken:
Expected
Both cases produce a clickable link.
Actual
Case B renders as plain text. The base64
text/htmlpart of the sent messagedecodes to:
Notes that may help narrow it down
<ais removed;</a>is untouched, so a tag allow-listfilter seems unlikely.
<p>andhref, exactly where the YAML linebreak was. YAML folding therefore worked as specified and the string handed to
the integration should have been
<p><a href="...">. Something after thatpoint removes the two characters
<a.spaces elsewhere in the string.
Side observation
The
text/plainalternative part of the generated message is empty (an emptybase64 block) when only
htmlis supplied. Clients that prefer plain text shownothing at all.
All reactions