Why is there noescape_gt_in_attrs counterpart ofescape_lt_in_attrs? Optimistic regex tag-soup readers do negative lookaheads for> to determine the closing point of a tag. They’re just as important to escape in atts as< for compatibility with everything.

Authors can’t work around this because<elm attr="&lt;example&gt;"> is always turned into<elm attr="&lt;example>">