Issue Bug Resolved

#111191Context menu actions in the contextual edit sheet navigate behind the sheet

Oliver Bartsch 10/21/26, 14:13 updated 11/01/26, 16:40

Description

In the Layout module, records can be edited in the contextual edit sheet. Fields in that sheet can show other records, for example a page in “Show content from this page instead” or the records of an “Insert records” element. Their context menus work from inside the sheet, but the actions run against the content frame behind it.

Steps to reproduce:

1. Open the Layout module on a page.
2. Open the page properties in the contextual edit sheet (the edit
button in the module header), tab “Appearance”.
3. Select a page in “Show content from this page instead” and save.
4. Open the context menu of the selected page in the sheet.
5. Choose “Edit”.

Expected: the record opens where the editor is working, i.e. in a sheet above the current one.

Actual: the edit form loads in the content frame behind the sheet.
Nothing visible happens until the sheet is closed. The editor then finds a different form than the one they were working on.

The same applies to other actions:

  • Actions that change the record, e.g. “Disable”, reload the content frame behind the sheet. The sheet stays open and keeps showing the old state of the record.
  • Actions that navigate the content frame, e.g. “Show in Records module”, load their target behind the open sheet.

Reloading the content frame also breaks the open sheet. The sheet is opened from the content frame, and after that frame reloads, the sheet has no event handlers left.

Unsaved changes in the sheet are not confirmed before any of these actions run.

Reviews 2

History 48

  1. Oliver Bartsch commented <span data-processor="relativetime" data-value="2026-10-28T07:42:15+00:00" > 10/28/26, 07:42 </span>

    In the Layout module, records can be edited in the contextual edit sheet. Fields in that sheet can show other records, for example a page in “Show content from this page instead” or the records of an “Insert records” element. Their context menus work from inside the sheet, but the actions run against the content frame behind it.

    Steps to reproduce:

    1. Open the Layout module on a page.
    2. Open the page properties in the contextual edit sheet (the edit
    button in the module header), tab “Appearance”.
    3. Select a page in “Show content from this page instead” and save.
    4. Open the context menu of the selected page in the sheet.
    5. Choose “Edit”.

    Expected: the record opens where the editor is working, i.e. in a sheet above the current one.

    Actual: the edit form loads in the content frame behind the sheet.
    Nothing visible happens until the sheet is closed. The editor then finds a different form than the one they were working on.

    The same applies to other actions:

    • Actions that change the record, e.g. “Disable”, reload the content frame behind the sheet. The sheet stays open and keeps showing the old state of the record.
    • Actions that navigate the content frame, e.g. “Show in Records module”, load their target behind the open sheet.

    Reloading the content frame also breaks the open sheet. The sheet is opened from the content frame, and after that frame reloads, the sheet has no event handlers left.

    Unsaved changes in the sheet are not confirmed before any of these actions run.

  2. Oliver Bartsch commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-11-01T16:40:14+00:00" > 11/01/26, 16:40 </span>

    Applied in changeset commit:fd25ec1e9e6d90a4ceb1e3cb906a14774d8b233d.