Fix parser errors that can occur when rendered tooltip contains certain characters like  

+1 on this. Worked on my end!

I think the concerning issue should be fixed ASAP or the tooltips are unusable, since with "common" filters any editor may create html entities by pressing 'shift+enters' on (eg) taxonomy term description and the parse errors will be triggered.

Agreed on getting this in. I fixed the merge conflict in the branch. The CI failures are not from this merge request. The unit tests are passing.

Great stuff, thanks @bkosborne! Looks good and works great! :)

First, I thought this might have some security implications, as we remove the "html_specialchars" call and therefore let the linked node's / term's / commerce product variation's textarea filter decide what HTML would be allowed.

But that's no problem, as all the "risky" strings are escaped in the twig template anyway! And in the case, where we just reinsert the replaced text (e.g. when "first_only" is checked), we just use the original (HTML) string which was allowed by the currently active filter anyway!

Great work! Merging.

Ah, the new test fails, I'll have a quick check.

Ok, no biggy, the new "ignore_tags" setting was simply missing.

Automatically closed - issue fixed for 2 weeks with no activity.