2 ms·
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 typ
by zamalek 7y ago
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.
- swader999 7y agoI always thought the entire cms space, the idea that non coders could manage web content, was a non starter just because of the editors.
- tiborsaas 7y agoBut 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".
- leeoniya 7y agobut it's good enough these days to serve as the basis for the CodeMirror 6 rewrite: https://news.ycombinator.com/item?id=17859291 https://news.ycombinator.com/item?id=17859291