In Smart Edit after scrolling, I am not able to edit the components

[former_member628933]

Hello Team,

Really appreciate if someone could help with the below issue.

I am having problems for editing the components after scrolling the page down. Let's say:

When the page is loaded, we have list of components displayed one below the other. I can see initially two components in the page without scrolling down which am able to edit it, Screenshot below

Now after scrolling down the page to view other components, I am not able to edit components. Screenshot attached below

Once the issue occurred, even I am not able to edit the components of the first screenshot after scrolling up again.

Any help is much appreciated.

Thanks in Advance.

[Former Member · Accepted solution]

The issue is strange and vague to fix the problem. I have listed some options to check:

• Actually the console error here means that it is not able to add the component to the overlay because the slot is not in the overlay. It could be specific to Chrome version. Please check by updating the chrome version and also check if it is reproducible it other browsers.

• Here in screenshot-1, "…" has all the options for that component. Usually "…" has all the options only if the component is smaller in size. But the image seems to be bigger. That is strange though. It could be that the dimension of the component in the overlay do not reflect the one in actual storefront. If you are developer, you could put breakpoints in the intersection observer callback (mutationObserverCallback) in SmartEditContractChangeListener.ts file and please check if the callback is called when the component appears/disappears from the viewport.

Can i know what version of smartEdit are you using ?

[former_member628933]

Hi Bargavi,

Thanks for your response and you are right! It was browser issue and I didn't think of that way and didn't try with other browser My Bad! It is working fine in IE now. We are using Hybris 6.6

I have updated the Chrome browser now but still am getting the same exception.

But anyways, thanks for your help.