|
|
|
|
|
by chearon
812 days ago
|
|
Google Docs uses canvas, yeah, and last I looked it used an empty contentEditable just to receive [rich text] input. I do think you could use this to write a document editor like Docs and side-step many of the problems with contentEditable, but I haven't tried to. Every time someone releases a new rich text editor I'm disappointed to find that it uses contentEdtiable. Would be very interesting! |
|
Sciter is using its own implementation (obviously).
contentEdtiable thing is indeed quite limited for general purpose WYSIWYG editor.
For example Web platform is missing transactional update [1] mechanism that allows to put custom DOM mutation groups into unified undo/redo stack.
Sciter's <htmlarea> element ( implement behavior:richtext - WYSIWYG ) allows to build specialized editors. For example it is used in Sciter.Notes [2].
[1] https://docs.sciter.com/docs/behaviors/behavior-richtext#ric... [2] https://notes.sciter.com/