Unable to see CQ decoration tag/Editable div in Chrome - Sightly data-sly-resource | Community
Skip to main content
Level 2
January 6, 2016
Solved

Unable to see CQ decoration tag/Editable div in Chrome - Sightly data-sly-resource

  • January 6, 2016
  • 5 replies
  • 1253 views

I have included a component through data-sly-resource. I am able to get the cq decoration tags on firefox and IE; able to edit the component where as I am unable to see the decoration on Chrome.

 

        <li class="apply-btn">
            <div data-sly-resource="${ @path='applybtn', resourceType='theironyard/components/content/button'}" data-sly-unwrap></div>
        </li>

Please let me know your thoughts.

Thanks,

Ramakrishna

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by kautuk_sahni

Hi 

As mentioned by Jitendera, it could be CSS issue. Please have a look at the similar kind of case reporter earlier.

Link:- http://stackoverflow.com/questions/25460407/chrome-not-displaying-divs

I hope this would help you.

Thanks and Regards

Kautuk Sahni 

5 replies

Jitendra_S_Toma
Level 10
January 6, 2016

Is it happening in Touch or Classic UI?. If it is in classic UI, this might be a CSS issue very similar to the one where parsys appears on top of the page though editing is supposed to be done on the page body.

--

Jitendra

kautuk_sahni
Community Manager
kautuk_sahniCommunity ManagerAccepted solution
Community Manager
January 6, 2016

Hi 

As mentioned by Jitendera, it could be CSS issue. Please have a look at the similar kind of case reporter earlier.

Link:- http://stackoverflow.com/questions/25460407/chrome-not-displaying-divs

I hope this would help you.

Thanks and Regards

Kautuk Sahni 

Kautuk Sahni
Feike_Visser1
Adobe Employee
Adobe Employee
January 6, 2016

can you remove the data-sly-unwrap?

kchs_rkAuthor
Level 2
January 6, 2016

I have tried removing data-sly-unwrap. But of no change in it. Let me try the CSS fix.

kchs_rkAuthor
Level 2
January 6, 2016

It is working as expected in Touch UI in all the browsers. Only problem here is in Chrome - Classic UI.