When using the Field UI Manage Display interface with the contrib Field Group → module enabled, moving child fields from their parent groups to the "ground level" (content region) via drag-and-drop does not properly update the parent-child relationship. The field appears visually at the ground level, but programmatically still retains its disabled group as its parent.
The root cause is that Drupal core's field_ui.js only handles region changes through the regionChange() method, but lacks equivalent logic for parent changes. When a field is dragged to a different parent or to ground level, the onChange() and onDrop() methods only check for region changes but ignore parent relationship updates.
The field group module is very special, as some core functionalities only exist, to make the field_group even possible. One of these things is the existence of the "parent" select in the "Manage form / view display" and the general logic of a "parent" on form / view display.
There is even an issue on trying to delete this functionality, see
🐛
Parent setting on Form display cannot be changed for custom Content type
Needs review
. That's why I think this functionality should also be merged into core (or even the whole "field_group" module should be part of core through
✨
Add field grouping to core
Needs work
).
Add parent change detection and handling to the field_ui.js file.
Active
11.0 🔥
field_ui.module
Done, this fixes the issue. Unsure on how to continue here. As said in the issue summary, field_group is very special and there is already code for it in core, might be time to reactivate ✨ Add field grouping to core Needs work , and get the whole thing in core finally.