Hi @Raam AJRTE is not officially supported for such use-cases yet in Touch UI.See Configure the Rich Text Editor

The fix for that would be to modify the XSS config to allow it from here -/libs/cq/xssprotection/config.xmlBut, please note that it's not recommended to modify it. This html is not allowed as per the XSS config (I am not aware of the reason). So, best is to avoid using this. You could try to search ...

Hi Matt-H- I would like to get answers to a few questions from your side to better understand your issue.Can you specify which AEM version are you using ?Whichever version you are one, can you check after installing the latest SP and CFP for that one ?This seems to work fine for OOTB Text component ...

Hi Matt-H-​I think you are mixing two things here.The error/warning is browser console that you see is not related to your use-case/issue. I think this shows up, in general, if you edit any OOTB Text component and seems like a minor bug.Your issue seems like something we fixed some time back.The iss...

Hi @vasudevaraog73192255Did you check my last comment related to XSS Antisamy rules ?Because this is also happening because of the same reason. The reason is not RTE, but XSS.If this is not clear, Checkout Page 28 of the Slides from my recent Gem session -https://helpx.adobe.com/content/dam/help/en/...

Hi @manikanthar12951933I see some examples for the same on the public github spaces for Adobe-Consulting-Services and Adobe-Marketing-Cloud.e.g.https://github.com/search?q=org%3AAdobe-Consulting-Services+cq%3Alisteners&type=Code https://github.com/search?q=org%3AAdobe-Consulting-Services+afterdelete...

Can you try to re-structure your configuration as specified here and check -aem-authoring-hybrideditors/_cq_editConfig.xml at master · Adobe-Marketing-Cloud/aem-authoring-hybrideditors · GitHub Configuring Multiple In-Place Editors

HiI can confirm that this issue was fixed in 6.4.3.0It's mentioned in AEM 6.4 Service Pack Release Notes as -When the rich text editor is combined with multiple fields, the Uncaught TypeError: fieldAPI.getName is not a function at foundation.js error occurs. NPR-27146: Hotfix for CQ-4253155