Affected Version
2026.2
Affected capability
Documents
Steps to reproduce
- In an areabrick implementing
EditableDialogBoxInterface, add a dialog field with a description via the documented fluent setter (or the 'description' array key):
(new Editable\Select())
->setName('media_position')
->setLabel('Media position')
->setDialogDescription('Choose on which side the media is displayed');
- Edit a document that uses the brick and open the brick's edit dialog in the Studio UI document editor.
Actual Behavior
The description is not displayed. The backend serializes it correctly (Pimcore\Model\Document\Editable::getDialogDescription() written as the description key in Document\Editable\Area / Document\Editable\Areablock), but the Studio UI renderer drops it: the DialogConfigItem type (editables-dialog/types.ts) declares only type, title, items, label, name, and editable-dialog.tsx renders each field as <Card title={configItem.label}> with no description output.
Expected Behavior
The dialog field description is rendered in the dialog (as in the classic admin UI), matching the documented setDialogDescription() / description behavior.
Affected Version
2026.2
Affected capability
Documents
Steps to reproduce
EditableDialogBoxInterface, add a dialog field with a description via the documented fluent setter (or the'description'array key):Actual Behavior
The description is not displayed. The backend serializes it correctly (
Pimcore\Model\Document\Editable::getDialogDescription()written as thedescriptionkey inDocument\Editable\Area/Document\Editable\Areablock), but the Studio UI renderer drops it: theDialogConfigItemtype (editables-dialog/types.ts) declares onlytype,title,items,label,name, andeditable-dialog.tsxrenders each field as<Card title={configItem.label}>with no description output.Expected Behavior
The dialog field description is rendered in the dialog (as in the classic admin UI), matching the documented
setDialogDescription()/descriptionbehavior.