Editor events

Respond to accepted document changes, selection, mode transitions, file operations and authoring dialogs. Events let the host maintain save prompts and application state.

HTML element notifications carry passive snapshots rather than a live COM DOM object.

Use it in your application

Use HtmlChanged for a host-owned dirty indicator and SelectionChanged for coalesced state refresh. File and mode events report acknowledged operations.

Pasting is synchronous policy inspection. Do not start asynchronous mutation from that checkpoint and assume it ran before the paste.

BrowserSessionRestored means the browser session was recreated and its previous undo history is unavailable. Keep the application document and save policy authoritative.

editor.HtmlChanged += (_, _) => errorMessage.Text = "Document has unsaved changes.";
editor.SelectionChanged += (_, _) => commandButton.IsEnabled = !editor.IsReadOnly;

Members

These signatures come from the delivered 1.0.2 assemblies and XML documentation. Cancellation tokens can be supplied to awaited operations. Follow the source-specific notes above when adapting a WPF integration.

Continue with

• Readiness and asynchronous operations