Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150)

> I actually don't think the issue here is that it's too difficult to make a richtext comment form editor. 

It's harder than it should be, because contenteditable is too permissive. If you want to save formatted comments in a backend, you have to clean up and sanitize the markup yourself (you don't want a tag soup in your database). Instead, I would argue the browser should support a textbox with a strictly defined set of markup.

> I think on sites that are for less techy people that's what is done.

Yes, on techie sites Markdown is probably a better fit. But Markdown is also used on non-techie sites*, which I think is due to technical problems with contenteditable. Of course I cannot prove it, but I think if we had a `<textarea type=rich>`, many non-techie sites would use it.

*) For example, the classic UI of Reddit uses Markdown for comments. So does Trello. Here's Trello CEO [saying](https://startupxplore.com/en/blog/qa-michael-pryor-trello-interview-spain-launch/) it was probably a mistake to go with Markdown.



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/150#issuecomment-568170027