exec_command and exec_command_* event

The exec_command_* event fires whenever an ExecCommand is executed.

A specific event such as exec_command_newdoc fires when that individual command runs.

Syntax

function(state,cmd,value)

Example usage

Code example

editor1.attachEvent("exec_command_newdoc", function (state, cmd, value) {
    state.returnValue = true;//handled, don't execute default action
    this.setHTMLCode("<p>NewDoc...</p>");
});

Calling the exec_command event from your app

the exec_command event belongs to the editor instance. Every integration below works the same way: keep the object that new RichTextEditor(...) returns, and call it on that object.

Plain JavaScript

Code example

var editor1 = new RichTextEditor("#div_editor1");
// The constructor is synchronous: the editor is ready on the next line.
editor1.attachEvent("exec_command_newdoc", function () { /* ... */ });

React and Next.js

Code example

// editorRef is filled by the RichTextEditor wrapper from the React guides.
const editorRef = useRef(null);

function onClick() {
  editorRef.current?.attachEvent("exec_command_newdoc", function () { /* ... */ });
}

return <RichTextEditor editorRef={editorRef} />;

In Vue and Angular, the wrapper components in the guides keep the instance in a component variable (editor), so the call is the same. See the React, Vue and Angular pages, or download a tested project from the guides.

If the editor is undefined

The call ran before the component mounted. Call it from an event handler or after the mount effect has run.
In React development mode, Strict Mode mounts, unmounts and mounts again, so the wrapper sets editorRef.current to null in between. Use editorRef.current?. rather than storing the instance elsewhere.
The editor was destroyed (editor.destroy()) when its component unmounted.

All methods: method reference · all events: event reference.