Why Aren’t More Generators Using Contenteditable for Direct Text Editing?

Implementing `contenteditable` in a way that’s accessible can be quite tricky. But, it's definitely a feature that could be revolutionary if only it had better cross-browser support. It's frustrating to see such potential go unrealized!

Many developers initially wonder why `contenteditable` isn't more popular. However, once they try implementing it, the complications become clear! It's easy to have a vision, but dealing with various browsers and their inconsistent handling of it is a headache.

Using `contenteditable` can lead to messy outcomes. While it seems great in theory, getting clean, parsable text can be a real challenge. Copying and pasting into it can also cause major formatting issues. I've seen some success with systems like Facebook's Lexical, but it's still not straightforward.

Though `contenteditable` sounds appealing, it comes with its own set of troubles. Browser compatibility issues abound, and syncing those edits with underlying data can get messy. Plus, validating what users input is more complicated, and it can hurt accessibility too. That's why many prefer simpler forms with live previews. They're more reliable.

If you're keen to explore `contenteditable`, I suggest learning through trial and error. The more you encounter the hiccups, the better you'll understand its limitations and how to navigate them.