Check your editor
Exercise real editing, file recovery and cleanup workflows.
After embedding the editor, complete the tasks your users will perform. Group checks by editing, files and resource lifecycle to locate problems more easily.
Editing and controls
Type text, drag to select, make it bold and undo. Button state should follow selection. Read-only mode must block both controls and keyboard edits. Switching Canvas/SVG should keep content and history.
For custom containers, test typing inside, selecting across boundaries, copying, replacing, saving and reopening.
Saving and restoring
Save, refresh and restore the actual saved content. Continue typing during saving: an older completion must not clear new unsaved changes. Edit during file reading: a late result must not replace the draft.
Try unsupported versions, unknown nodes and damaged files. Show errors and preserve both current content and original files. Inspect actual DOCX output and diagnostics; confirm image bytes remain available.
Pages and resources
Drag selections after narrow-screen resizing, zooming and scrolling. Leave and return to the page, checking for duplicate listeners or outdated asynchronous editor creation.
Keep repeatable document fixtures with package versions, model versions, required fonts and media services. Use them again when upgrading.
Find implementations in the complete reference, and methods in Editor API and View API.