How We Built a Web Document Editor
summary
A case study of how the MyOffice team built a web document editor: the talk describes the global architecture and key design decisions, focusing on a shared native "core" used by editors on multiple platforms and how the web frontend integrates with it using Wasm and Emscripten. It covers canvas-based rendering and engineering challenges the web editor faces—fonts, links, focus and selection handling, and performance—and ends with current problems and possible solutions.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:31Editor requirements
- 4:18Cross-platform core
- 10:03Core pros and cons
- 13:35Integrating core
- 18:18Document rendering
- 26:55Font handling
- 33:17Rendering problems
- 36:49Architecture pyramid
- 37:53Q&A
related talks
44mThe document’s journey from file to editing: processing 1,000 pages and not dying
24mYet Another Text Web Editor and What's Wrong with contenteditable?
31mPrevent Default — The Future of Authoring Tools
04mONLYOFFICE Online Editors collaborate on documents in real time
37mBuilding a Collaborative Text Editor
44mDeveloping a good editor experience with Microsoft 365 / Google Workspace
57mDeveloping a Rich Text Editor: Problems and Solutions
37mWeb Application Architecture -- Lessons Learned from Brackets