scribe

https://github.com/guardian/scribe Here you go!

I tried Scribe and was quite enthused about it but there are trivial bugs that never got fixed, been a year since I filed this issue[1]: Basically, http://jsfiddle.net/L59kL1rf/ -- you cannot delete the first paragraph and always end up with <p><br /></p> and if you try to delete that it just starts acting strange. This issue has been open since 2014 and it seems it's a bug in the core. There were other similar issues I ran into around the same and decided I would revisit later but it's been a nearly a year since. [1]: https://github.com/guardian/scribe/issues/300

Great timing, we were just looking for a new editor for our project. Since there are so many choices, here's a list of everything mentioned in this post. Trix - https://github.com/basecamp/trix - demo here: http://trix-editor.org/ by basecamp and used in v3, handles files/images well Squire - https://github.com/neilj/Squire - used in FastMail webmail, better for text than images ProseMirror - http://prosemirror.net/ - not great with images Scribe - https://github.com/guardian/scribe - by the Guardian team CKEditor - http://ckeditor.com/ - solid and very customizable, lots of plugins, a little dated in look/feel Quill - http://quilljs.com/ Summernote - http://summernote.org/ wysihtml - http://wysihtml.com/ Etherpad - http://etherpad.org/ - collaborative realtime editing TinyMCE - http://www.tinymce.com/ - older editor but still good Textb

Sadly, while the Scribe developers correctly identified all the various problems with contenteditable (https://github.com/guardian/scribe/blob/master/BROWSERINCONS...), they chose to solve it like most other editors: by using execCommand, waiting for the browser to make a change, and then attempting to clean it up afterwards. Trix's thesis is that this approach is fundamentally broken. Instead, Trix updates an internal document model on each input event, then re-renders the editor contents in response.

'contenteditable is inconsistent across browsers'. We (the Guardian) created Scribe to tackle this: https://github.com/guardian/scribe (I can't take any credit personally though alas!)

Have you tried Scribe editor? https://github.com/guardian/scribe I've found it has better HTML output than medium-editor (though still not perfect) and has a more flexible design, though it requires a bit more developer involvement to get up and running.

Thanks for releasing! It would be awesome to see your toolbar / UI released as a separate project also. Also check out Scribe - https://github.com/guardian/scribe which is similarly very light weight - has no UI built in. Mostly exists to fix browser inconsistencies with contenteditable.

Try looking into Scribe. They describe it as: > A rich text editor framework for the web platform, with patches for browser inconsistencies and sensible defaults. https://github.com/guardian/scribe

Just to clear up any confusion: this is not the same as the Guardian’s “Scribe” project (https://github.com/guardian/scribe). I believe Quill did used to be called Scribe, but they are not the same. (Similar in purpose - take your pick.)

Can you add an issue here (https://github.com/guardian/scribe/issues) and we can talk solutions? I have a few in mind! Generally speaking, it should patch behaviour to the point where it doesn’t get in the way of the user and produces clean and semantic markup. We have found that patching some of the smaller behaviour obscurities would not be trivial. If it matters to the community though, we (the open source community) can definitely get them patched!

The behaviour you describe around italics is completely native to the browser, so it will at least be consistent across uses of `contentEditable`. I agree that it is annoying, but there were much bigger fish to fry (https://github.com/guardian/scribe/blob/87d3ed1a7f28d9fcdcc0...). You make some very good points about Markdown, and we spent awhile thinking about whether to go down that road or not. Although there is a technical barrier to access for Markdown, that’s not the reason we decided against it. Maybe we should do another blog post to follow up with more details regarding our decisions. (Or, I’ll come here with more details in just a bit.)

The distribution files are kept in the `dist` branch. The tree you linked to is just for the example. We encourage consumers to download these files using Bower (`bower install scribe`) https://github.com/guardian/scribe/tree/dist

This is awesome. Copying and pasting text from Word files seems to work fairly well, instantly generating HTML with all the cruft removed. To download it to your desktop and try it out locally get [these files](https://github.com/guardian/scribe/tree/gh-pages)