Editor Events

Equivalent Trix Events: https://github.com/basecamp/trix/blob/main/README.md#observing-editor-changes

• rhino-before-initialize fires when the <rhino-editor> element is attached to the DOM just before Rhino installs its editor object.

• rhino-initialize fires when the <rhino-editor> element is attached to the DOM and its editor object is ready for use.

• rhino-change fires whenever the editor’s contents have changed.

• rhino-paste fires whenever text is pasted into the editor. The paste property on the event contains the pasted string or html, and the range of the inserted text.

• rhino-selection-change fires any time the selected range changes in the editor.

• rhino-focus and rhino-blur fire when the editor gains or loses focus, respectively.

• rhino-file-accept fires when a file is dropped or inserted into the editor. You can access the DOM File object through the file property on the event. Call event.preventDefault() on the event to prevent attaching the file to the document.

• rhino-attachment-add fires after an attachment is added to the document. You can access the Rhino attachment object through the attachment property on the event. If the attachment object has a file property, you should store this file remotely and set the attachment’s URL attribute. See the attachment example for detailed information.

• rhino-attachment-remove fires when an attachment is removed from the document. You can access the Rhino attachment object through the attachment property on the event. You may wish to use this event to clean up remotely stored files.

Direct Upload Events

(Thank you Matheus Rich for the inspiration!)

https://github.com/rails/rails/pull/52680

Direct Uploads now have the following events you can listen to in the editor. All of the events have the event.attachmentUpload property which should have all the information you need to react appropriately.

• - rhino-direct-upload:start - called when the upload starts.
• - rhino-direct-upload:progress - Called periodically as the editor progesses.
• - rhino-direct-upload:error - Called when the upload errors.
• - rhino-direct-upload:success - Called when the upload has finished. This will get NOT get called if there is an error.
• - rhino-direct-upload:complete - Called when the upload has finished. This will get called even if there is an error.

All of the above have a event.attachmentUpload which will contain various properties you need. Such as .progress, .attachment, etc.

For example, here’s how you would grab the progress of a direct upload:

document.querySelector("rhino-editor").addEventListener("rhino-direct-upload:progress", (event) => {
  console.log(event.attachmentUpload.progress)
})

Waiting to submit a form until direct uploads finish

Also of note, the direct-upload attachments will also add a .pendingAttachmentUploads to Rhino Editor.

This can be useful for stopping form submissions until all uploads have finished.

Here’s an example of how you could stop form submissions:

form.addEventListener("submit", (e) => {
  if (rhinoEditor.pendingAttachmentUploads.length > 0) {
    // There are still pending uploads, so preventDefault() to stop the submission
    e.preventDefault()
  }
})