OverviewStarting 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.
Key Features & Functionality
Supported Browsers: Chrome, Firefox, Edge, SafariSupported on Mobile
It should be (the Styled Text Editor has a few less format options though). If any of it isn't please let us know.
Will richText entered via this component be compatible with the out-of-the-box Styled Text Editor Component - Appian 24.2, or will we need to make edits to the formatted text so that it can work in the new component?
Hello,
We are experiencing issues where images uploaded to the component refuse to render on custom-branded mobile apps for iOS. If an image was added to the component, it appears as a blue box with a question mark to users on the iOS device
We have this vulnerability reported on latest May 2024 scan. Can we have a resolution for this issue.
BDSA-2021-1834
Quill is vulnerable to stored cross-site scripting (XSS) because it does not correctly sanitize user input before it is processed. An attacker could exploit this flaw to execute malicious JavaScript code in a victim's browser, which can result in the theft of session tokens or cookies. **Note**: the vendor disputes this issue, asserting that potentially dangerous content should be sanitized before being passed and loaded into the Quill editor.
We have this same vulnerability reported on latest May 2024 scan. Can we have a resolution for this issue.
We found issue where the nested bullets formatting is not getting formed correct.
The nested bullets getting formatted like this
<ul> <li>myItem 1</li> <li>myItem 2</li> <li style="list-style-type:none"> <li>myItem 2a</li> <li>myItem 3</li></ul>
instead of getting formatted like this is which is preferred
<ul> <li>myItem 1</li> <li>myItem 2</li> <li style="list-style-type:none"> <ul> <li>myItem 2a</li> </ul> </li> <li>myItem 3</li></ul>
Thank you for your patience. This behavior should be fixed in v1.12.2 that was just released.
We are facing strange behaviour in the plugin, where while typing random users across different environment having problem with cursor moving back to the beginning. You can see the behaviour in the attached video. Anybody facing this issue and could tell me more .