Editing text with HTML elements in mixed mode strips HTML from textarea value about tagify

[yairEO]

You should to set the initial value before initializing Tagify and also for links to work they should have a contentEditable="false" attribute but note that they won't be editable.

input.value = `This is some text with a <a contentEditable="false"  href="http:google.com">link</a>. The link will show initially, but it won't be saved back to the textarea.`;

See my Stackoverflow answer

[atownley]

Unfortunately, this requires pre/post processing the HTML in order to facilitate the solution you mentioned. And it means you don't have the ability to easily round-trip things without a whole lot of extra effort.

Due to this issue and a few others, I've moved away from Tagify for mixed-mode content. I think it's great for tags, but I think there's a lot of stuff in mixed-mode it just doesn't handle well—this being one of them.

But it's all good. It's not really what it is for, and if it works for people in this use case, great. For me, I need something a bit different, and the change you made isn't doing to work for my usage scenario.

[yairEO]

Yeah I understand.. mix-mode is insanely difficult to develop, there are endless amount of browser bugs that I do not have time/motivation to address as I'm pretty thin on my motivation to continue programming after almost 3 decades.

When I started working on mix-mode in 2017 I thought how hard can this be.
well, it's pretty much very hard. and it's not my fault, it's there are just so so many browser bugs and insane workarounds that has to be done around them.. and browser vendors won't fix a thing. frustrating.

I did re-wrote the whole code in React 2 years ago to make a mix-mode version which works very well but have never released it.. it takes a lot of time to release a project because demo pages needs to be authored and README file and whatnot..