CKEditor 5 Rails Integration ✨

Unofficial CKEditor 5 Ruby on Rails integration gem. Provides seamless integration of CKEditor 5 with Rails applications through web components and helper methods.

Installation 🛠️

Add this line to your application's Gemfile:

gem 'ckeditor5'

In your config:

# config/initializers/ckeditor5.rb

CKEditor5::Rails.configure do |config|
  config.presets.override :default do
    version '43.3.0'
  end
end

In your view:

<!-- app/views/demos/index.html.erb -->

<% content_for :head do %>
  <%= ckeditor5_assets %>
<% end %>

<%= ckeditor5_editor %>

Voilà! You have CKEditor 5 integrated with your Rails application. 🎉

Table of Contents 📚

• CKEditor 5 Rails Integration ✨
  • Installation 🛠️
  • Table of Contents 📚
  • Presets 🎨
  • Available Configuration Methods ⚙️
    • cdn(cdn = nil, &block) method
    • version(version) method
    • gpl method
    • license_key(key) method
    • premium method
    • translations(*languages) method
    • ckbox method
    • type(type) method
    • toolbar(*items, should_group_when_full: true, &block) method
    • menubar(visible: true) method
    • language(ui, content:) method
    • configure(name, value) method
    • plugin(name, premium:, import_name:) method
    • plugins(*names, **kwargs) method
    • inline_plugin(name, code) method
  • Including CKEditor 5 assets 📦
  • Lazy loading 🚀
  • GPL usage 🆓
  • Commercial usage 💰
  • Editor placement 🏗️
  • Setting Initial Content 📝
  • Watchdog 🐕
  • Classic editor 📝
  • Multiroot editor 🌳
  • Inline editor 📝
  • Balloon editor 🎈
  • Decoupled editor 🌐
  • How to access editor instance? 🤔
  • Common Tasks and Solutions 💡
  • Setting Editor Language 🌐
  • Integrating with Forms 📋
    • Rails form builder integration
    • Simple form integration
  • Custom Styling 🎨
  • Custom plugins 🧩
  • Events fired by the editor 🔊
  • editor-ready event
  • editor-error event
  • License 📜

Presets 🎨

Presets are predefined configurations of CKEditor 5, allowing quick setup with specific features. The gem includes a :default preset with common features like bold, italic, underline, and link for the classic editor.

You can create your own by defining it in the config/initializers/ckeditor5.rb file using the config.presets.define method. The example below illustrates the setup of a custom preset with a classic editor and a custom toolbar:

# config/initializers/ckeditor5.rb

CKEditor5::Rails.configure do |config|
  config.presets.define :custom
    gpl
    type :classic

    menubar
    toolbar :undo, :redo, :|, :heading, :|, :bold, :italic, :underline, :|,
            :link, :insertImage, :mediaEmbed, :insertTable, :blockQuote, :|,
            :bulletedList, :numberedList, :todoList, :outdent, :indent

    plugins :AccessibilityHelp, :Autoformat, :AutoImage, :Autosave,
            :BlockQuote, :Bold, :CloudServices,
            :Essentials, :Heading, :ImageBlock, :ImageCaption, :ImageInline,
            :ImageInsert, :ImageInsertViaUrl, :ImageResize, :ImageStyle,
            :ImageTextAlternative, :ImageToolbar, :ImageUpload, :Indent,
            :IndentBlock, :Italic, :Link, :LinkImage, :List, :ListProperties,
            :MediaEmbed, :Paragraph, :PasteFromOffice, :PictureEditing,
            :SelectAll, :Table, :TableCaption, :TableCellProperties,
            :TableColumnResize, :TableProperties, :TableToolbar,
            :TextTransformation, :TodoList, :Underline, :Undo, :Base64UploadAdapter

    configure :image, {
      toolbar: ['imageTextAlternative', 'imageStyle:inline', 'imageStyle:block', 'imageStyle:side']
    }
  end
end

In order to override existing presets, you can use the config.presets.override method. The method takes the name of the preset you want to override and a block with the old configuration. The example below shows how to hide the menubar in the default preset:

# config/initializers/ckeditor5.rb

CKEditor5::Rails.configure do |config|
  config.presets.override :default do
    menubar visible: false

    toolbar do
      remove :underline, :heading
    end
  end
end

Configuration of the editor can be complex, and it's recommended to use the CKEditor 5 online builder to generate the configuration. It allows you to select the features you want to include and generate the configuration code in JavaScript format. Keep in mind that you need to convert the JavaScript configuration to Ruby format before using it in this gem.

Available Configuration Methods ⚙️

Expand to show available methods 📖

#### `cdn(cdn = nil, &block)` method Defines the CDN to be used for CKEditor 5 assets. The example below shows how to set the CDN to `:jsdelivr`: ```rb # config/initializers/ckeditor5.rb config.presets.define :custom do # ... other configuration cdn :jsdelivr end ``` It also allows you to define a custom CDN by passing a block with the bundle, version, and path arguments. The example below shows how to define it for the `jsdelivr` CDN: ```rb # config/initializers/ckeditor5.rb config.presets.define :custom do # ... other configuration cdn do |bundle, version, path| base_url = "https://cdn.jsdelivr.net/npm/#bundle@#version/dist" "#base_url/#? '' : 'browser/'#path" end end ``` #### `version(version)` method Defines the version of CKEditor 5 to be used. The example below shows how to set the version to `43.2.0`: ```rb # config/initializers/ckeditor5.rb config.presets.define :custom do # ... other configuration version '43.2.0' end ``` #### `gpl` method Defines the license of CKEditor 5. The example below shows how to set the license to GPL: ```rb # config/initializers/ckeditor5.rb config.presets.define :custom do # ... other configuration gpl end ``` #### `license_key(key)` method Defines the license key of CKEditor 5. It calls `premium` method internally. The example below shows how to set the license key: ```rb # config/initializers/ckeditor5.rb config.presets.define :custom do # ... other configuration license_key 'your-license-key' end ``` #### `premium` method Defines if premium package should be included in JS assets. The example below shows how to add `ckeditor5-premium-features` to import maps: ```rb # config/initializers/ckeditor5.rb config.presets.define :custom do # ... other configuration premium end ``` #### `translations(*languages)` method Defines the translations of CKEditor 5. You can pass the language codes as arguments. The example below shows how tell integration to fetch Polish and Spanish translations: ```rb # config/initializers/ckeditor5.rb config.presets.define :custom do # ... other configuration translations :pl, :es end ``` ⚠️ You need to use `language` method to set the default language of the editor, as the `translations` only fetch the translations files and makes them available to later use. ```rb # config/initializers/ckeditor5.rb config.presets.define :custom do translations :pl language :pl end ``` #### `ckbox` method Defines the CKBox plugin to be included in the editor. The example below shows how to include the CKBox plugin: ```rb # config/initializers/ckeditor5.rb config.presets.define :custom do # ... other configuration ckbox '2.5.4', theme: :lark end ``` #### `type(type)` method Defines the type of editor. Available options: - `:classic` - classic edytor - `:inline` - inline editor - `:decoupled` - decoupled editor - `:balloon` - balloon editor - `:multiroot` - editor with multiple editing areas The example below sets the editor type to `multiroot` in the custom preset: ```rb # config/initializers/ckeditor5.rb config.presets.define :custom do # ... other configuration type :multiroot end ``` #### `toolbar(*items, should_group_when_full: true, &block)` method Defines the toolbar items. You can use predefined items like `:undo`, `:redo`, `:|` or specify custom items. There are a few special items: - `:_` - breakpoint - `:|` - separator The `should_group_when_full` keyword argument determines whether the toolbar should group items when there is not enough space. It's set to `true` by default. ```rb # config/initializers/ckeditor5.rb config.presets.define :custom do # ... other configuration toolbar :undo, :redo, :|, :heading, :|, :bold, :italic, :underline, :|, :link, :insertImage, :ckbox, :mediaEmbed, :insertTable, :blockQuote, :|, :bulletedList, :numberedList, :todoList, :outdent, :indent end ``` Keep in mind that the order of items is important, and you should install the corresponding plugins. You can find the list of available plugins in the [CKEditor 5 documentation](https://ckeditor.com/docs/ckeditor5/latest/framework/architecture/plugins.html). If you want to add or prepend items to the existing toolbar, you can use the block syntax: ```rb # config/initializers/ckeditor5.rb config.presets.override :default do # ... other configuration toolbar do append :selectAll, :|, :selectAll, :selectAll # Or prepend: prepend :selectAll, :|, :selectAll, :selectAll end end ``` If you want to remove items from the toolbar, you can use the `remove` method: ```rb # config/initializers/ckeditor5.rb config.presets.override :default do # ... other configuration toolbar do remove :selectAll, :heading #, ... end end ``` #### `menubar(visible: true)` method Defines the visibility of the menubar. By default, it's set to `true`. ```rb # config/initializers/ckeditor5.rb config.presets.define :custom do # ... other configuration toolbar :undo, :redo, :|, :heading, :|, :bold, :italic, :underline, :|, :link, :insertImage, :ckbox, :mediaEmbed, :insertTable, :blockQuote, :|, :bulletedList, :numberedList, :todoList, :outdent, :indent end ``` #### `language(ui, content:)` method Defines the language of the editor. You can pass the language code as an argument. Keep in mind that the UI and content language can be different. The example below shows how to set the Polish language for the UI and content: ```rb # config/initializers/ckeditor5.rb config.presets.define :custom do # ... other configuration language :pl end ``` In order to set the language for the content, you can pass the `content` keyword argument: ```rb # config/initializers/ckeditor5.rb config.presets.define :custom do # ... other configuration language :en, content: :pl end ``` #### `configure(name, value)` method Allows you to set custom configuration options. You can pass the name of the option and its value as arguments. The example below show how to set the default protocol for the link plugin to `https://`: ```rb # config/initializers/ckeditor5.rb config.presets.define :custom do # ... other configuration configure :link, { defaultProtocol: 'https://' } end ``` #### `plugin(name, premium:, import_name:)` method Defines a plugin to be included in the editor. You can pass the name of the plugin as an argument. The `premium` keyword argument determines whether the plugin is premium. The `import_name` keyword argument specifies the name of the package to import the plugin from. The example below show how to import Bold plugin from the `ckeditor5` npm package: ```rb # config/initializers/ckeditor5.rb config.presets.define :custom do # ... other configuration plugin :Bold end ``` In order to import a plugin from a custom ESM package, you can pass the `import_name` keyword argument: ```rb # config/initializers/ckeditor5.rb config.presets.define :custom do # ... other configuration plugin :YourPlugin, import_name: 'your-package' end ``` In order to import a plugin from a custom Window entry, you can pass the `window_name` keyword argument: ```rb # config/initializers/ckeditor5.rb config.presets.define :custom do # ... other configuration plugin :YourPlugin, window_name: 'YourPlugin' end ``` #### `plugins(*names, **kwargs)` method Defines the plugins to be included in the editor. You can specify multiple plugins by passing their names as arguments. The keyword arguments are identical to the configuration of the `plugin` method defined below. ```rb # config/initializers/ckeditor5.rb config.presets.define :custom do # ... other configuration plugins :Bold, :Italic, :Underline, :Link end ``` #### `inline_plugin(name, code)` method Use with caution as this is an inline definition of the plugin code, and you can define a custom class or function for the plugin here. The example below shows how to define a custom plugin that highlights the text: ```rb # config/initializers/ckeditor5.rb config.presets.define :custom do # ... other configuration inline_plugin :MyCustomPlugin, <<~JS import { Plugin } from 'ckeditor5'; export default class MyCustomPlugin extends Plugin { static get pluginName() { return 'MyCustomPlugin'; } init() { // ... Your plugin code } } JS end ```

Including CKEditor 5 assets 📦

To include CKEditor 5 assets in your application, you can use the ckeditor5_assets helper method. This method takes the version of CKEditor 5 as an argument and includes the necessary resources of the editor. Depending on the specified configuration, it includes the JS and CSS assets from the official CKEditor 5 CDN or one of the popular CDNs.

Keep in mind that you need to include the helper result in the head section of your layout. In examples below, we use content_for helper to include the assets in the head section of the view.

Lazy loading 🚀

Loading JS and CSS Assets

All JS assets defined by the `ckeditor5_assets` helper method are loaded **asynchronously**. It means that the assets are loaded in the background without blocking the rendering of the page. However, the CSS assets are loaded **synchronously** to prevent the flash of unstyled content and ensure that the editor is styled correctly. It has been achieved by using web components, together with import maps, which are supported by modern browsers. The web components are used to define the editor and its plugins, while the import maps are used to define the dependencies between the assets.

GPL usage 🆓

If you want to use CKEditor 5 under the GPL license, you can include the assets using the ckeditor5_assets without passing any arguments. However you can pass the version keyword argument with the version of CKEditor 5 you want to use:

<!-- app/views/demos/index.html.erb -->

<% content_for :head do %>
  <%= ckeditor5_assets version: '43.3.0' %>
<% end %>

It'll include the necessary assets for the GPL license from one of the most popular CDNs. In our scenario, we use the jsdelivr CDN which is the default one.

Version is optional as long as you defined it in the config/initializers/ckeditor5.rb file. If you want to use the default version, you can omit the version keyword argument:

<!-- app/views/demos/index.html.erb -->

<% content_for :head do %>
  <%= ckeditor5_assets %>
<% end %>

Set the version in the config/initializers/ckeditor5.rb file:

# config/initializers/ckeditor5.rb

CKEditor5::Rails.configure do
  presets.override :default do
    version '43.3.0'
  end
end

In order to use unpkg CDN, you can pass the cdn keyword argument with the value :unpkg:

<!-- app/views/demos/index.html.erb -->

<% content_for :head do %>
  <%= ckeditor5_assets cdn: :unpkg %>
<% end %>

or using helper function:

<!-- app/views/demos/index.html.erb -->

<% content_for :head do %>
  <%= ckeditor5_jsdelivr_assets %>
<% end %>

Translating CKEditor 5 is possible by passing the translations keyword argument with the languages codes array. The example below shows how to include the Polish translations:

<!-- app/views/demos/index.html.erb -->

<% content_for :head do %>
  <%= ckeditor5_assets translations: [:pl] %>
<% end %>

Keep in mind, that you need to include the translations in the config/initializers/ckeditor5.rb file:

# config/initializers/ckeditor5.rb

CKEditor5::Rails.configure do
  presets.override :default do
    language :pl
  end
end

Commercial usage 💰

If you want to use CKEditor 5 under a commercial license, you can include the assets using the ckeditor5_assets helper method with the license_key keyword argument. The example below shows how to include the assets for the commercial license:

<!-- app/views/demos/index.html.erb -->

<% content_for :head do %>
  <%= ckeditor5_assets license_key: 'your-license-key' %>
<% end %>

In this scenario, the assets are included from the official CKEditor 5 CDN which is more reliable and provides better performance, especially for commercial usage.

Editor placement 🏗️

The ckeditor5_editor helper renders CKEditor 5 instances in your views. Before using it, ensure you've included the necessary assets in your page's head section otherwise the editor won't work as there are no CKEditor 5 JavaScript and CSS files loaded.

Setting Initial Content 📝

You can set the initial content of the editor using the initial_data keyword argument or by passing the content directly to the ckeditor5_editor helper block.

The example below shows how to set the initial content of the editor using the initial_data keyword argument:

<!-- app/views/demos/index.html.erb -->

<%= ckeditor5_editor initial_data: "<p>Initial content</p>" %>

The example below shows how to set the initial content of the editor using the ckeditor5_editor helper block.

<!-- app/views/demos/index.html.erb -->

<%= ckeditor5_editor do %>
  <p>Initial content</p>
<% end %>

Watchdog 🐕

CKEditor 5 uses a watchdog utility to protect you from data loss in case the editor crashes. It saves your content just before the crash and creates a new instance of the editor with your content intact. It's enabled by default in the gem.

If you want to disable the watchdog, you can pass the watchdog keyword argument with the value false:

<!-- app/views/demos/index.html.erb -->

<%= ckeditor5_editor watchdog: false %>

Classic editor 📝

The classic editor is the most common type of editor. It provides a toolbar with various formatting options like bold, italic, underline, and link.

It looks like this:

The example below shows how to include the classic editor in your view:

<!-- app/views/demos/index.html.erb -->

<% content_for :head do %>
  <%= ckeditor5_assets %>
<% end %>

<%= ckeditor5_editor style: 'width: 600px' %>

You can pass the style keyword argument to the ckeditor5_editor helper to define the editor's style. The example above shows how to set the width of the editor to 600px. However you can pass any HTML attribute you want, such as class, id, data-*, etc.

While example above uses predefined :default preset, you can use your custom presets by passing the preset keyword argument:

<!-- app/views/demos/index.html.erb -->

<% content_for :head do %>
  <%= ckeditor5_assets %>
<% end %>

<%= ckeditor5_editor preset: :custom, style: 'width: 600px' %>

If your configuration is even more complex, you can pass the config and type arguments with the configuration hash:

<!-- app/views/demos/index.html.erb -->

<% content_for :head do %>
  <%= ckeditor5_assets %>
<% end %>

<%= ckeditor5_editor type: :classic, config: { plugins: [:Bold, :Italic], toolbar: [:Bold, :Italic] }, style: 'width: 600px' %>

If you want to override the configuration of the editor specified in default or custom preset, you can pass the extra_config keyword argument with the configuration hash:

<!-- app/views/demos/index.html.erb -->

<% content_for :head do %>
  <%= ckeditor5_assets %>
<% end %>

<%= ckeditor5_editor extra_config: { toolbar: [:Bold, :Italic] }, style: 'width: 600px' %>

Multiroot editor 🌳

The multiroot editor allows you to create an editor with multiple editable areas. It's useful when you want to create a CMS with multiple editable areas on a single page.

• ckeditor5_editor: Defines the editor instance.
• ckeditor5_editable: Defines the editable areas within the editor.
• ckeditor5_toolbar: Defines the toolbar for the editor.

If you want to use a multiroot editor, you can pass the type keyword argument with the value :multiroot:

<!-- app/views/demos/index.html.erb -->

<% content_for :head do %>
  <%= ckeditor5_assets %>
<% end %>

<%= ckeditor5_editor type: :multiroot, style: 'width: 600px' do %>
  <%= ckeditor5_toolbar %>
  <br>
  <%= ckeditor5_editable 'toolbar', style: 'border: 1px solid var(--ck-color-base-border);' do %>
    This is a toolbar editable
  <% end %>
  <br>
  <%= ckeditor5_editable 'content', style: 'border: 1px solid var(--ck-color-base-border)' %>
  <br>
<% end %>

Roots can be defined later to the editor by simply adding new elements rendered by ckeditor5_editable helper.

Inline editor 📝

Inline editor allows you to create an editor that can be placed inside any element. Keep in mind that inline editor does not work with textarea elements so it might be not suitable for all use cases.

If you want to use an inline editor, you can pass the type keyword argument with the value :inline:

<!-- app/views/demos/index.html.erb -->

<% content_for :head do %>
  <%= ckeditor5_assets %>
<% end %>

<%= ckeditor5_editor type: :inline, style: 'width: 600px' %>

Balloon editor 🎈

Balloon editor is a floating toolbar editor that provides a minimalistic interface. It's useful when you want to create a simple editor with a floating toolbar.

If you want to use a balloon editor, you can pass the type keyword argument with the value :balloon:

<!-- app/views/demos/index.html.erb -->

<% content_for :head do %>
  <%= ckeditor5_assets %>
<% end %>

<%= ckeditor5_editor type: :balloon, style: 'width: 600px' %>

Decoupled editor 🌐

Decoupled editor is a variant of classic editor that allows you to separate the editor from the content area. It's useful when you want to create a custom interface with the editor.

If you want to use a decoupled editor, you can pass the type keyword argument with the value :decoupled:

<!-- app/views/demos/index.html.erb -->

<% content_for :head do %>
  <%= ckeditor5_assets %>
<% end %>

<%= ckeditor5_editor type: :decoupled, style: 'width: 600px' do %>
  <div class="menubar-container">
    <%= ckeditor5_menubar %>
  </div>

  <div class="toolbar-container">
    <%= ckeditor5_toolbar %>
  </div>

  <div class="editable-container">
    <%= ckeditor5_editable %>
  </div>
<% end %>

How to access editor instance? 🤔

You can access the editor instance using plain HTML and JavaScript, as CKEditor 5 is a web component with defined instance, instancePromise and editables properties.

For example:

<!-- app/views/demos/index.html.erb -->

<% content_for :head do %>
  <%= ckeditor5_assets %>
<% end %>

<%= ckeditor5_editor style: 'width: 600px', id: 'editor' %>

⚠️ Direct access of instance property of the web component. Keep in mind it's unsafe and may cause issues if the editor is not loaded yet.

document.getElementById('editor').instance

👌 Accessing the editor instance using instancePromise property. It's a promise that resolves to the editor instance when the editor is ready.

document.getElementById('editor').instancePromise.then(editor => {
  console.log(editor);
});

✅ Accessing the editor through the runAfterEditorReady helper method. It's a safe way to access the editor instance when the editor is ready.

document.getElementById('editor').runAfterEditorReady(editor => {
  console.log(editor);
});

Common Tasks and Solutions 💡

This section covers frequent questions and scenarios when working with CKEditor 5 in Rails applications.

Setting Editor Language 🌐

You can set the language of the editor using the language method in the config/initializers/ckeditor5.rb file. The translations method fetches the translations files, while the language method sets the default language of the editor.

config.presets.override :default do
  translations :pl, :es
  language :pl
end

Integrating with Forms 📋

You can integrate CKEditor 5 with Rails form builders like form_for or simple_form. The example below shows how to integrate CKEditor 5 with a Rails form using the form_for helper:

Rails form builder integration

<!-- app/views/demos/index.html.erb -->

<%= form_for @post do |f| %>
  <%= f.label :content %>
  <%= f.ckeditor5 :content, required: true, style: 'width: 700px', initial_data: 'Hello World!' %>
<% end %>

Simple form integration

<!-- app/views/demos/index.html.erb -->

<%= simple_form_for :demo, url: '/demos', html: { novalidate: false } do |f| %>
  <div class="form-group">
    <%= f.input :content, as: :ckeditor5, initial_data: 'Hello, World 12!', input_html: { style: 'width: 600px' }, required: true %>
  </div>

  <div class="form-group mt-3">
    <%= f.button :submit, 'Save', class: 'btn btn-primary' %>
  </div>
<% end %>

Custom Styling 🎨

You can pass the style, class and id keyword arguments to the ckeditor5_editor helper to define the styling of the editor. The example below shows how to set the height, margin, and CSS class of the editor:

<!-- app/views/demos/index.html.erb -->

<%= ckeditor5_editor style: 'height: 400px; margin: 20px;', class: 'your_css_class', id: 'your_id' %>

Custom plugins 🧩

You can create custom plugins for CKEditor 5 using the inline_plugin method. It allows you to define a custom class or function inside your preset configuration.

The example below shows how to define a custom plugin that allows toggling the highlight of the selected text:

# config/initializers/ckeditor5.rb

config.presets.define :custom do
  # ... other configuration

  # 1. You can also use "window_name" option to import plugin from window object:

  # plugin :MyPlugin, window_name: 'MyPlugin'

  # 2. Create JavaScript file in app/javascript/custom_plugins/highlight.js,
  #    add it to import map and then load it in initializer:

  # plugin :MyCustomPlugin, import_name: 'my-custom-plugin'

  # 3 Create JavaScript file in app/javascript/custom_plugins/highlight.js
  #   and then load it in initializer:

  # In Ruby initializer you can also load plugin code directly from file:
  inline_plugin :MyCustomPlugin, File.read(
    Rails.root.join('app/javascript/custom_plugins/highlight.js')
  )

  # 4. Or even define it inline:
  # inline_plugin :MyCustomPlugin,  <<~JS
  #    import { Plugin } from 'ckeditor5';
  #
  #    export default class MyCustomPlugin extends Plugin {
  #      // ...
  #    }
  # JS

  # Add item to beginning of the toolbar.
  toolbar do
    prepend :highlight
  end
end

Example of Custom Highlight Plugin 🎨

```js // app/javascript/custom_plugins/highlight.js import { Plugin, Command, ButtonView } from 'ckeditor5'; export default class MyCustomPlugin extends Plugin { static get pluginName() { return 'MyCustomPlugin'; } init() { const editor = this.editor; // Define schema for highlight attribute editor.model.schema.extend('$text', { allowAttributes: 'highlight' }); // Define conversion between model and view editor.conversion.attributeToElement({ model: 'highlight', view: { name: 'span', styles: { 'background-color': 'yellow' } } }); // Create command that handles highlighting logic // Command pattern is used to encapsulate all the logic related to executing an action const command = new HighlightCommand(editor); // Register command in editor editor.commands.add('highlight', command); // Add UI button editor.ui.componentFactory.add('highlight', locale => { const view = new ButtonView(locale); // Bind button state to command state using bind method // bind() allows to sync button state with command state automatically view.bind('isOn').to(command, 'value'); view.set({ label: 'Highlight', withText: true, tooltip: true }); view.on('execute', () => { editor.execute('highlight'); editor.editing.view.focus(); }); return view; }); } } // Command class that handles the highlight feature // isEnabled property determines if command can be executed class HighlightCommand extends Command { execute() { const model = this.editor.model; const selection = model.document.selection; model.change(writer => { const ranges = model.schema.getValidRanges(selection.getRanges(), 'highlight'); for (const range of ranges) { if (this.value) { writer.removeAttribute('highlight', range); } else { writer.setAttribute('highlight', true, range); } } }); } refresh() { const model = this.editor.model; const selection = model.document.selection; const isAllowed = model.schema.checkAttributeInSelection(selection, 'highlight'); // Set if command is enabled based on schema this.isEnabled = isAllowed; this.value = this.#isHighlightedNodeSelected(); } // Check if the highlighted node is selected. #isHighlightedNodeSelected() { const { model } = this.editor const { schema } = model const selection = model.document.selection if (selection.isCollapsed) { return selection.hasAttribute('highlight') } return selection.getRanges().some(range => Array .from(range.getItems()) .some(item => schema.checkAttribute(item, 'highlight') && item.hasAttribute('highlight') ) ); } } ```

Events fired by the editor 🔊

editor-ready event

The event is fired when the initialization of the editor is completed. You can listen to it using the editor-ready event.

document.getElementById('editor').addEventListener('editor-ready', () => {
  console.log('Editor is ready');
});

editor-error event

The event is fired when the initialization of the editor fails. You can listen to it using the editor-error event.

document.getElementById('editor').addEventListener('editor-error', () => {
  console.log('Editor has an error');
});

License 📜

This project is licensed under the terms of the GNU General Public License v2.0. See the LICENSE file for details.