Expand my Community achievements bar.

Enhance your AEM Assets & Boost Your Development: [AEM Gems | June 19, 2024] Improving the Developer Experience with New APIs and Events
SOLVED

Colspan property missing sometimes and other odd behavior

Avatar

Level 4

In AEM 6.2 been using Colspan property to make forms easier to read.

colspanOK.JPG

However, I am trying to create a new form, and I thought I was following my previous steps but when I try to configure the properties, Colspan is missing from the properties list if I am in a panel. The only time the Colspan property is available is if the field is directly under guideRootPanel.

colspanMissing.JPG

Thanks!

1 Accepted Solution

Avatar

Correct answer by
Level 4

I think we found the problem...

If we drag a child panel component from the side bar into the form and set it up with columns, then direct child fields/panels will have the Colspan property.

1498130_colspanOK.JPG

However, if we try to use "Add Child Panel" from a panel's edit toolbar (ellipsis, then "Add Child Panel"), direct child fields/panels will not have the Colspan property.

panel.jpg--> 1498131_colspanMissing.JPG

So we apparently have two ways of doing the same thing that have different results. I am opening a bug ticket with Adobe.

View solution in original post

2 Replies

Avatar

Level 2

Colspan property is available for the fields / panels which are a direct child of a panel with responsive layout. You can add a wrapper responsive panel to achieve the desired behavior.

Avatar

Correct answer by
Level 4

I think we found the problem...

If we drag a child panel component from the side bar into the form and set it up with columns, then direct child fields/panels will have the Colspan property.

1498130_colspanOK.JPG

However, if we try to use "Add Child Panel" from a panel's edit toolbar (ellipsis, then "Add Child Panel"), direct child fields/panels will not have the Colspan property.

panel.jpg--> 1498131_colspanMissing.JPG

So we apparently have two ways of doing the same thing that have different results. I am opening a bug ticket with Adobe.