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
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
Supported Browsers: Chrome, Firefox, Edge, SafariSupported on Mobile
Hello Appian Team, Appian AppMarket
We also have the same use case and want to use this component in an editable grid. Can we expect this future in your upcoming release?Thanks
Thanks for releasing 'Styled Text Editor Component' component, very much excited to use.
In one of the business use case, i was looking to use this component in editable grid but it is not supporting like richTextField function.
Should i expect editable grid support in future release. Thanks for your support like always.
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.