A new way to build custom web editing experiences with EditContext

by laaczon 3/8/2024, 6:54 AMwith 1 comments

by russellbeattieon 3/8/2024, 7:47 AM

This is a truly half-baked implementation of an editing API which adds 100 problems for every one it solves. Examples are: No native keyboard bindings (ctrl-c, etc.), no undo stack, no native text selection, no native spell check, and more.

Rather than simply solving the real problem - adding a <richtextarea> field with full fledged editing control and APIs that builds on contenteditable functionality - this anemic API was created which is essentially a more complicated KeyEvent manager and leaves us in the same situation we're in today: A hundred custom incompatible online editors.