Rich Text Editors Reenabled for LockerService

You can now use rich text editors and edit fields with rich text when the LockerService critical update is active. Previously, rich text editors were disabled in sandboxes and Developer Edition orgs when the LockerService critical update was active. This change applies to Lightning Experience and all versions of the Salesforce1 mobile app.
Available in: All Editions

Most rich text editors in Salesforce are now using Quill, and a few continue to use CKEditor in an iframe. The move to Quill enables the rich text editors to be compliant with LockerService, but there are minor visual and formatting differences compared to previous releases.

Note

Note

The availability of toolbar buttons varies across features. For example, the code snippet button is available in Chatter publisher but not in custom fields.

Custom Fields

Rich text editors in fields with the rich text area type are back. Some formatting appear different when you save a record in Salesforce Classic and edit it in Lightning Experience. For more information, see Rich Text Editors for Custom Fields Get a New Look.

Chatter Feeds

The rich text editor in the composer has changed slightly. For example, the @mention button is next to the Insert Image button. For more information, see Get a Richer Experience with the New Editor in Chatter.

Chatter Questions

The changes to the rich text editor in Chatter Questions are similar to the changes for Chatter Feeds.

Community Builder

The Rich Content Editor component in the community builder has changed. The Underline button is now available, and the Code Snippet button is no longer available. For more information, see Refine Your Content with a Streamlined Rich Content Editor and Dedicated HTML Editor.

Groups
The toolbar in the Information field provides more support for rich text formatting. Give your group’s information a boost using these new toolbar features:
  • Change the font face
  • Underline or strike out text
  • Create a numbered list
  • Add or remove indentation
  • Remove formatting
We recommend using the toolbar as much as you can to format your content. If you copy formatted content from another source and paste into the editor, unsupported tags are removed and text within those tags are preserved as plain text. Only formatting available in the toolbar is supported. For example, if you paste red bold text, the bold formatting is preserved but not the color.
Sales Path

The rich text editor in the Guidance for Success field has changed. The undo and redo buttons are no longer available. You can use the Edit menu in your browser to undo or redo your changes. We recommend using the toolbar as much as you can to format your content. If you copy formatted content from another source and paste into the editor, unsupported tags are removed and text within those tags are preserved as plain text. Only formatting available in the toolbar is supported.

forceChatter:publisher Component

The changes to the rich text editor in forceChatter:publisher are similar to the changes for Chatter Feeds.

Note

Note

We recommend using the toolbar to format your content. The rich text editor provides only a WYSIWYG interface. You can’t edit HTML tags. When you copy content from a web page or another source and paste it into the editor, unsupported tags are removed. Text that was enclosed in unsupported tags is preserved as plain text.

Rich Text Editors Using CKEditor

Rich text editors in Salesforce Classic continue to use CKEditor. In Lightning Experience and Salesforce1, the following features have rich text editors that continue to use CKEditor.

  • Email Composer, using the Send Email action
  • Lightning Knowledge
  • Lightning App Builder
  • ui:inputRichText component
Note

Note

The ui:inputRichText component is no longer supported for LockerService. Use lightning:inputRichText instead.

These features load the rich text editor in an iframe, so they don’t load correctly if your browser doesn’t have the appropriate security settings. Refer to your browser’s instructions to configure the settings. For example, in Internet Explorer, the Launching programs and files in an IFRAME security setting must be set to Enable or Prompt. In Safari, we recommend changing your Privacy settings for cookies to Allow from websites I visit (1). In Chrome, make sure that Block third-party cookies and site data is not selected in the Content settings.

Additionally, to start typing in the rich text editor on Internet Explorer 11 on touch-enabled devices running Windows, you must click the rich text area field and tab into the editor first.

Safari privacy settings