A rich editor is a document model with a browser input surface, not a contenteditable element alone. The browser may insert text, fragments, spell corrections, and composition updates through different paths. This track follows a private case note with headings and emphasis. It covers input and IME boundaries, selection positions across transforms, safe pasted content, bounded undo history, and revisioned autosave. The note remains usable as plain text when advanced formatting fails, and rendered output follows the same server-side content policy.
Topics in this track
- Editable Input, Composition, and Document Model — Accept browser edits and IME composition without treating the live DOM as the authoritative document.
- Selection Bookmarks and Transaction Mapping — Represent caret and range positions in model coordinates that survive DOM replacement.
- Paste Import, Sanitization, and Link Policy — Convert clipboard fragments into a narrow document schema before they can reach storage or rendered HTML.
- Undo History, Autosave, and Revision Conflicts — Bound local edit history and save a document through conditional revisions without erasing newer work.
Prerequisite paths
Forms and Data Entry Workflows; Browser Security and Data Stewardship.
Neighbor track
Interactive Graphics and Canvas Boundaries.
Practice path
Build Project: versioned case note editor and check decisions in Web Development: graphics and editor decisions quiz.