Component edit mode not working

Hi Veena,

Please verify in the browser console. You should see some javascript error. Paste the error stack trace.

Thanks,

Sham

Hi Veena,

Is it happening in chrome or any other browser? In your dialog are you using any cqinclude?

Hi Veena,

    dialog of custom component might be causing it.  There should be file name after "Uncaught Error: IndexSizeError: DOM Exception 1" the exception.

    If you are using oob components then paste your dialog.xml

Thanks,

Sham

@adobe_sham

Hi Sham,

Im seeing a simular issue. In my case the error "DOM Exception 1" is thrown in Chrome latest for CQ5.5

When an authour begins editing the Rich Text Component, this error occurs intermitently. Debugging clientLibs shows the following...

http://localhost:4502/libs/cq/ui/widgets/source/widgets/form/rte/Selection.js
line #2052

For 5.5 chrome is not fully supported[1] & the issue is logged CQ5-29304

[1] https://dev.day.com/docs/en/cq/5-5/deploying/technical_requirements.html

Hi Sham,

Im sure I dont understand, Chrome is correctly implementing W3C spec.

Here's an excerpt from Mozilla concerning the index parameter of the getRangeAt method

https://developer.mozilla.org/en-US/docs/Web/API/Selection/getRangeAt

"The zero-based index of the range [should] return. A negative number or a number greater than or equal to rangeCount will result in an error"

In other words Chrome is correctly throwing an error in accordance with W3C spec.

MS  IE<=8 does not support .getRangeAt(); so it must be using alternate code as it cannot invoke getRangeAt. While I understand that CQ5.5 is not "supporting" Chrome, this defect is in code specifcaly written by Adobe to support modern capable browsers and there is a bug in it.