I put that as a contrived example, but I understand it is on the user of the tool to understand how to select values without matching to the markup. As I say in footnote 2 there is a chance that the link generated for the pingbacks matches with markup. Not sure if it is worth having this extra complexity to handle that rare case.

---

Unrelated: The mpwp text editor should not be evaluating htmlentities. I wrote <a href="http://trilema.com">trilema</a> as &lt;a href="http://trilema.com"&gt;trilema&lt;/a&gt; into the text editor. Whenever I save or update, the escaped html gets evaluated back to <a href="http://trilema.com">trilema</a>. If I save again, it gets saved to the db as an actual html tag. billymg seems to have found a solution to this.

It should be impossible ; don't link a.com as a, nude like that, it's stupid. There must be come relevant context, or else why are you linking ?

In other words, just because some user errors are more entrenched in common [lazy] practice than others dun make them less erroneous. Allow well made tools to guide your work experience much like you allow your work experience guide the making of wel lmade tools.

But yes, it's good practice to always provide the closing e ; even if it's just a .