Making a New ContentEditable Editor
summary
Builds a new ContentEditable editor that abandons DOM observers and relies on the beforeinput API to capture edits, implements everything in TypeScript with functional libraries like fp-ts and lenses, and drives behavior with real browser tests via puppeteer tests. Handles tricky IME and spell‑checker cases first, plans enter and operations next, and estimates a simple two‑command core in one to two months. Claims code ends up far smaller and more testable.
AI-written summary · about
chapters (6)
- 0:00Start
- 3:55Usable contentEditable editors
- 9:29How to choose? By features you need.
- 10:45Seven Deadly Sins
- 15:52contenteditable Editor Dream
- 23:38How to Learn Functional Programming
related talks
24mYet Another Text Web Editor and What's Wrong with contenteditable?
57mDeveloping a Rich Text Editor: Problems and Solutions
35mBuilding a Browser Based Code Editor
37mBuilding a Collaborative Text Editor
29mAuthor Anything with Universal Editor
33mBuilding a Browser Based Code Editor
34mBuilding a Browser Based Code Editor
46mAmbitious Editorial Experiences with Headless Drupal