Sure. Unfortunately this is still unanswered. I believe this is a bug with the policies code.

After some playing around with this issue, I found a hack / workaround by doing the following:I cannot click "Drag components here" on my drawer's child parsysHowever, I can add a component as a sibling to my drawer component (i.e. a text component)I am able to drag this component into my drawer's c...

I can upload my package if that is helpful. I've tested this in fresh instances of 6.2, 6.3, and 6.4This did not work in any environment.

When I drop it onto an editable template, I configure it with "x" number of drawers.When the component renders, I have to manually define the policy for each parsys that gets created.In the policy selection dialog, I am able to select the policy that I defined on the parent component (omc-Drawer).Ha...

Hi Scott, I'll share with you the static template version that leverages /etc/designs/Here is my component:This component has a multi-field which creates "x" number of parsys nodes and dynamically adds a unique node name to them.<div class="omc-Drawer-parsys" data-sly-resource="${['drawer-content', ...

Hello,I am working on creating editable templates in AEM 6.2. I have an accordion-like component that leverages a multi-field to create tabs with parsys containers. In order to preserve the content that gets dragged into each of these parsys nodes, and to preserve the re-orderability that the multi-...

Use granite/ui/components/coral/foundation/form/select instead

Please ignore, problem solved.

Hello,I just finished watching this presentation: https://seminars.adobeconnect.com/p43ucnv6655/?proto=trueI am trying to add a granite:class property to my granite/ui/components/foundation/form/select widget.I was able to add this to a textfield, but it doesn't appear to be working for the select f...