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
Cursor is getting reset to the end of text if user is trying to edit the already existing text in the editor.For Example: If "Hello World" is already existing text, and user wants to update it to "Hello wonderful World". While trying to type in wonderful, cursor is getting rest to the end of the text.Please fix the issue.
We have found 2 accessibility concerns with this plugin. Would it be possible to get a bug fix for these issues?
1. The default color value for background text (yellow) does not meet contrast requirements.
2. The table feature does not appear to be keyboard accessible. You are able to tab to and select the icon (using 'Enter' key) but there doesn't seem to be a way to navigate to selecting columns/rows and actually inserting the table using the keyboard.
Thank you!
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.