If I have a component that includes a parsys, and is editable, eg a JSP:
<%@include file="/libs/foundation/global.jsp"%> <%@page session="false" %> <%@ taglib prefix="wcm" uri="http://www.adobe.com/consulting/acs-aem-commons/wcm" %> <% // TODO add you code here %> <cq:include path="par" resourceType="foundation/components/parsys" />
and editConfig
<?xml version="1.0" encoding="UTF-8"?> <jcr:root xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0" xmlns:nt="http://www.jcp.org/jcr/nt/1.0" cq:actions="[text:Something here,-,delete,copymove,-,insert, edit]" cq:layout="editbar" jcr:primaryType="cq:EditConfig"> </jcr:root>
And I include this component in a page component, eg
<%@include file="/libs/foundation/global.jsp"%> <%@page session="false" %> <body> <header> <div class="content_wrapper"> <cq:include path="mainContent" resourceType="joel-test/components/content/parsysContainer" /> </div> </header> <section> <div class="content_wrapper"> <cq:include path="mainContent1" resourceType="joel-test/components/content/parsysContainer" /> </div> </section> <footer> <div class="content_wrapper"> <cq:include path="mainContent2" resourceType="joel-test/components/content/parsysContainer" /> <cq:include path="mainContent3" resourceType="joel-test/components/content/parsysContainer" /> </div> </footer> <cq:include path="mainContent4" resourceType="joel-test/components/content/parsysContainer" /> </body>
Then I am able to drag components outside of any of these parsysContainers. See this screenshot from CRXDE Lite, which shows two components that were dragged onto the parsys correctly, and a third which was dragged between mainContent and mainContent1.
[img]drag.png[/img]
I can only reproduce this in Touch UI. Is this a bug, or intentional? I think it will create some confusion for my authors.
Solved! Go to Solution.
Views
Replies
Total Likes
If you are seeing two different behavior between Touch and Classic, then it should be a bug. Please a raise a support ticket for the same
Views
Replies
Total Likes
If you are seeing two different behavior between Touch and Classic, then it should be a bug. Please a raise a support ticket for the same
Views
Replies
Total Likes