The latest version of Slack has a setting to disable the WYSIWYG editor

Re:The latest version of Slack has a setting to disable the ... by zamalek on Tuesday December 03, 2019 @08:28PM (#21698795)

The reason is that content editable is a gaping hole in the HTML5 spec, at least last time I checked, there are tons of undefined undefined behaviors (not a typo) where vendors have to choose what they want to do and where developers have no idea that the behavior does not exist in a specification.

My very wise coworker made every effort to avoid that minefield. I thought he was wrong for many years, but I have been forced to agree, content editable is completely and utterly useless and should be avoided at all costs.

[ Parent | on HN ]

Re:The latest version of Slack has a setting to disable the ... by swader999 on Tuesday December 03, 2019 @08:59PM (#21698966)

I always thought the entire cms space, the idea that non coders could manage web content, was a non starter just because of the editors.

[ Parent | on HN ]

Re:The latest version of Slack has a setting to disable the ... by tiborsaas on Wednesday December 04, 2019 @05:49AM (#21701149)

But it's utterly inefficient to use coder time to manage web content. That's why the best idea is to create a block by block content editor with textareas or severally limited editors that remove and reformat HTML that's being generated. I've seen good results thanks to this.

I agree though, whenever I included a full WYSIWYG editor to a CMS the end users created unimaginable havoc. "Hey it's Word, I know this".

[ Parent | on HN ]

Re:The latest version of Slack has a setting to disable the ... by leeoniya on Tuesday December 03, 2019 @09:05PM (#21698994)

but it's good enough these days to serve as the basis for the CodeMirror 6 rewrite:

https://news.ycombinator.com/item?id=17859291

[ Parent | on HN ]