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
Per the changes to Chrome and Edge, the plugin will not load and gets blocked by CORS in certain situations. See here https://developer.chrome.com/blog/local-network-access
Please add Access-Control-Request-Private-Network: true to the response so that it will pop a message requesting it be allowed.
We are using richTextTable function on Appian version 25.4 and plugin version 1.16 but we are not able to see font size 16.
Earlier we were using Appian version 24.3 where we were able to see the font size 16 but now only 10 , 14 , 18, 32 are available .
Is there any hot fix for this .
Plugin does not render with Chrome version 1.42. We have verified with several users before and after. Appears that chrome is doing aways with a certain type of dynamic link and they are telling developer to migrate to a new deep-linking solution instead.
The label/instructions framework of component plugins is not specific to this plugin, nor does any plugin have any control over it. I would recommend opening a ticket with Appian Support along the lines of "Common Parameters of Component Plugins do not adhere to Accessibility Standards (one example Rich Text Editor Plugin)".
Our application got flagged for some accessibility/508 violations related to this component, due to the instructions and label not being read by a screen reader when navigating via keyboard tabbing into the field. Are there any plans to address this? Note that we cannot use the native styled text editor because we need the additional formatting options that are available on this plugin.
Can you give an example of "noise" that isn't stripped today? Either an HTML tag or attribute.We don't use a library for this, but the underlying component should only allow a specific whitelist of tags and attributes which match the same ones that can be applied manually, using the buttons/keyboard shortcuts of the component.
Hi team, are there any plans to update the summernote editor to include a summernote cleaner plugin to handle additional HTML "noise" copy and pasted text from external sources like MS Word? Something similar to https://www.jsdelivr.com/package/npm/summernote-cleaner.