You're viewing old version number 3. - Current version

ContentEditable web browser editors

Not for me. I'll continue to use my "enhanced" JavaScript editor that I "created" in the summer of 2013. Around that time.

I did not create it from scratch. I downloaded someone else's open source code and modified the code to work the way I wanted. I added features.

For my Junco, Grebe, Scaup, and Veery web publishing apps, "my" JavaScript editor has been modified slightly for each web app. It now sends JSON requests to my API code instead of packaging JSON within a url-encoded POST to the API.

My modified editor has always received JSON from my API code.

Anyway, about ContentEditable:

http://scripting.com/2015/08/12/theresAContenteditableCommunity.html

http://html5demos.com/contenteditable

https://w3c.github.io/editing/contentEditable.html

https://medium.com/medium-eng/why-contenteditable-is-terrible-122d8a40e480

http://marijnhaverbeke.nl/blog/prosemirror.html

https://www.indiegogo.com/projects/prosemirror#/story

#browser - #web - #editor - #javascript

From JR's : articles
117 words - 985 chars
created on
updated on - #
source - versions

Related articles
ContentEditable web browser editors - Aug 12, 2015
Cross-Origin Resource Sharing header - Jan 09, 2015
Tt post about article design - mon, sep 8 and tue, sep 9, 2015 - Sep 09, 2015
Web vs Native apps in 2013 and beyond - Oct 22, 2013
Tt post mon, jun 6, 2016 - a - Jun 06, 2016
more >>



A     A     A     A     A

© 2013-2017 JotHut - Online notebook

current date: May 3, 2024 - 8:43 a.m. EDT