Rich Text Editor Component

IMPORTANT: Select component plug-ins are experiencing issues due to a recent browser update. If you encounter any problems with previously functional component plug-ins, please create a support case. If you notice other component plug-ins that are not functioning correctly, please create additional support cases for each instance.

Overview

Starting in 24.2, the Styled Text Editor Component is available directly in the product. Consider using this in place of the plug-in moving forward. For more information, review: https://docs.appian.com/suite/help/latest/Styled_Text_Editor_Component.html

Displays a field that allows for users to type text and format it with a variety of style options.
Output is saved as HTML. To get the raw character output, designers can use the Appian function fn!stripHtml() on the output.
HTML output can be passed into Send E-Mail node or document generation smart services. Note that not all formats supported by the Rich Text Editor component may be supported by e-mail or document generation.
Allows uploading of images which get stored in the specified Appian folder (requires separate install of the Rich Text Editor Connected System Plugin from https://community.appian.com/b/appmarket/posts/rich-text-editor-image-upload-connected-system).

Visit https://community.appian.com/w/the-appian-playbook/1378/end-user-rich-text-editor-component for more information. If you have any problems installing or using the component, please see the https://community.appian.com/w/the-appian-playbook/1603/rich-text-editor-component-plug-in-troubleshooting-guide

Key Features & Functionality

Component: fn!richTextField()
Allows for size validation
Allows for adjustable height
Allows for read-only / editable view
Supported font formats: "header", "size", "bold", "italic", "underline", "strike", "color", "background", "link", "align", "indent", "list"
Designer control over the allowed formats

Supported Browsers: Chrome, Firefox, Edge, Safari
Supported on Mobile

Parents

Jose Carlos Jarquin over 2 years ago

Hello,

Recently, we have noticed that hyperlinks created within the rich text editor component have been getting an additional string attached in the HTML code. The additional string added is 'rel="noopener noreferrer"'. Is this behavior expected? The additional string is causing some issues in interfaces where we extract the HTML links from the component value and display them separately.

Any information is appreciated!
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Dan Tobias over 2 years ago in reply to Jose Carlos Jarquin

What component are you using? richTextField or richTextFieldWithTables ?
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Dan Tobias over 2 years ago in reply to Jose Carlos Jarquin

This is done intentionally by the underlying library that is used, and is done to prevent a phishing vulnerability: https://www.jitbit.com/alexblog/256-targetblank---the-most-underestimated-vulnerability-ever/

We aren't going to be able to make an update to remove this attribute. I'd suggest just enhancing your logic to account for that string. When you are doing the extraction in Appian, you can probably just remove that substring from the full richTextValue variable and pretend it doesn't exist for the purposes of your logic.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel

Comment

Dan Tobias over 2 years ago in reply to Jose Carlos Jarquin

This is done intentionally by the underlying library that is used, and is done to prevent a phishing vulnerability: https://www.jitbit.com/alexblog/256-targetblank---the-most-underestimated-vulnerability-ever/

We aren't going to be able to make an update to remove this attribute. I'd suggest just enhancing your logic to account for that string. When you are doing the extraction in Appian, you can probably just remove that substring from the full richTextValue variable and pretend it doesn't exist for the purposes of your logic.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel

Children

No Data