- Issue created by @prashant.c
- 🇳🇿New Zealand quietone
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → .
When managing fields on an entity type or bundle, field configuration forms currently open in a modal pop-up by default. While this is helpful for quick edits, it becomes cumbersome for longer field forms with multiple settings. The modal often limits space, can be confusing to navigate, and does not offer the full context of the page.
It would improve usability to provide a configuration option at the entity type or bundle level to disable modal windows for field configuration forms. This would allow the field settings form to open in the full page context instead of a modal.
For complex field types or settings, navigating within the modal becomes difficult and restrictive.
Introduce a checkbox setting at the entity type or bundle level:
Label: "Open field settings in a modal window"
Default: Enabled (to preserve current behavior)
When unchecked, clicking "Create a new field" or "Edit" will open the field settings form in a full page rather than a modal.
Add a configuration setting to entity type or bundle definitions.
Update the UI form rendering logic in Field UI to respect this setting.
Provide a checkbox in the UI at the entity type/bundle level for enabling/disabling modal pop-ups for field settings.
Add tests for both behaviors.
Update help text and documentation.
A new checkbox in the entity type or bundle configuration form:
"Open field settings in a modal window"
When unchecked, field settings open in a full-page form.
Field settings modal toggle — A configuration option at the entity type or bundle level controlling how field settings forms are opened.
None expected unless we expose helper methods to access the new setting programmatically.
Add a new boolean configuration item to the entity type or bundle config schema.
TBD
Active
11.0 🔥
field system
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → .