When a Cards view has no properties configured to display (image + title only), each card renders as a single, correctly-nested element — image and title both inside one . The moment any property is added to the view's order/properties list, the DOM structure changes: the image and the .bases-card-body (title + properties) become separate sibling elements directly under .bases-cards, rather than the body being nested inside the same card anchor as the image. A markup-generation difference, not a styling one.
This breaks CSS Grid layouts that rely on each card being one grid item (.bases-cards { display: grid }), since the grid now receives twice as many top-level items as there are cards, with no reliable way to re-pair image+body siblings back into visual units via CSS alone once the set needs to wrap across multiple rows.
When a Cards view has no properties configured to display (image + title only), each card renders as a single, correctly-nested element — image and title both inside one . The moment any property is added to the view's order/properties list, the DOM structure changes: the image and the .bases-card-body (title + properties) become separate sibling elements directly under .bases-cards, rather than the body being nested inside the same card anchor as the image. A markup-generation difference, not a styling one.
This breaks CSS Grid layouts that rely on each card being one grid item (.bases-cards { display: grid }), since the grid now receives twice as many top-level items as there are cards, with no reliable way to re-pair image+body siblings back into visual units via CSS alone once the set needs to wrap across multiple rows.