#110523Form editor: no way to insert an element into a non-empty composite element (Fieldset/GridRow)
Description
Environment: TYPO3 14.3.6 (typo3/cms-form 14.3.6), form editor, abstract stage view.
Steps to reproduce:
1. Open a form in the form editor.
2. Insert a composite element, e.g. a Grid row.
3. Insert one element into it — works, the empty container offers an
“insert inside” drop area.
4. Try to insert a second element into the same container.
Also you can see the problem in the screenshots.
Expected behavior:
The container still offers a way to insert an element into itself, so a
Grid row can be filled with two Grid columns without leaving it.
Actual behavior:
Once a composite element has at least one child, there is no insert
option for the container any more. The only way to add a second child is
to create the element somewhere else and drag it in.
Analysis:
Two places in the current stage rendering:
*Resources/Public/JavaScript/backend/form-editor/stage-component.js*
appends the “inside” insert area only while the composite has no
children:
d = Array.isArray(renderables) && renderables.length > 0;
if (!d && isComposite) { … append(inside) }`
*Resources/Public/JavaScript/backend/form-editor/component/form-element-stage-item-toolbar.js
emits only `toolbar-new-element-before`, `toolbar-new-element-after`
and `toolbar-remove-element`. There is no “inside” counterpart.
The template-based predecessor did offer it:
Resources/Private/Backend/Partials/FormEditor/Stage/_ElementToolbar.fluid.html
renders a split button with `stageElementToolbarNewElementSplitButtonInside`
(“insert inside”) next to “insert after”, and `view-model.js` wires it to
view/insertElements/perform/inside`. That partial is marked
@deprecated since TYPO3 v14.2 … Only used by the legacy template-based
stage rendering`, so the option appears to have been dropped during the
move to the web component based stage.
The `view/insertElements/perform/inside` handler itself still exists in
`form-editor/mediator.js`; only the UI to trigger it is gone.
Workaround (Not preferred, beacuse you jump to top again):
Select an existing child of the container and use “insert after” on that
element — the new element becomes a sibling inside the same container.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Files 2
History 4
-
Josua Vogel changed status
NewNeeds Feedback <span data-processor="relativetime" data-value="2026-08-26T13:47:40+00:00" > 08/26/26, 13:47 </span> -
Lukas Dörr commented <span data-processor="relativetime" data-value="2026-09-08T07:23:46+00:00" > 09/08/26, 07:23 </span>
thanks for the info, i guess that is fair. Lets close it
-
Garvin Hicking changed status
Needs FeedbackClosed <span data-processor="relativetime" data-value="2026-09-10T09:39:58+00:00" > 09/10/26, 09:39 </span>
Hi @lukasdoerr ,
This is a design decision. To save space, we decided not to include a “New Element” button, since it would then have to be rendered before and after every element.
The “workaround” you mentioned is the intended way to add new elements.