@kchaurasiya - I'm using v6.5.5.0. The Configure (wrench) icon has been disabled/removed so the only way to edit is the Edit (pencil) icon, and since the script in question bypasses the 'normal' editing screen the only option I have is the full-screen editor.

Hi @kchaurasiya - I don't see anything in error.log related to editing the Text component. There's only the error in the browser console.

Hi all - I recently implemented the 'fix' for opening the RTE in full-screen mode by default, by following these instructions - http://experience-aem.blogspot.com/2016/07/aem-62-touch-ui-rich-text-editor-inplace-editing-open-in-fullscreen-editing-start-event.html - but it seems to be causing issues ...

Thanks for posting @jordanl32063034 - are you working with a 'webpack setup' too?Yes, this is basically what I experienced. I had eventually tracked down the initial error related to the deep-linking function and 'disabled' it so I could continue testing (knowing that I would need to re-enable it la...

Hi @Ritesh_Mittal - thank you for your response. I'm trying to keep the proxy component as clean and simple as possible. I get the 'CQ' JS errors in both editor and preview (see my other response to vmdala), and am just hoping to get the OOB component working as intended - then I may look into custo...

Thanks @vmadala - I haven't added any files besides webpack.include.js (which I notice none of the Adobe 'proxy component' documentation mentions). As I mentioned, even just creating the single node (below) produces the 'CQ' JS errors in editor and preview - when it seems like this should basically ...

Hi - I've been struggling with my proxy Accordion component for a few days now. I've tested many different scenarios with varying degrees of success. From the simplest setup with only the single component node (allowing everything from /libs to be referenced), to copying all files (from GitHub) to m...