Issue Bug Resolved

#111244 Copying a content element by holding down CTRL key does not work in Google Chrome

Peter Wijngaarden 10/26/26, 08:21 updated 11/09/26, 14:15

Description

After upgrading from TYPO3 v12 to TYPO3 v13 (13.4.37), copying content elements in the backend using CTRL + drag-and-drop no longer works in Chromium-based browsers.

When holding down the CTRL key and dragging a content element to a new location, the element is moved instead of copied.

Steps to reproduce:

Open the TYPO3 backend in Google Chrome.

Navigate to a page containing content elements.

Hold down the CTRL key.

Drag a content element to a new location.

The element is moved instead of duplicated.

Expected behavior:

Holding down the CTRL key while dragging a content element should create a copy at the new location.

Actual behavior:

The content element is moved without creating a copy.

Additional information:

The functionality works correctly in Firefox.

The issue occurs in Chromium-based browsers.

Both drag-and-drop and CTRL + drag-and-drop worked correctly in TYPO3 v12.

The issue appeared after upgrading to TYPO3 v13 (13.4.37).

Reviews 3

History 48

  1. Garvin Hicking commented and changed status New Needs Feedback <span data-processor="relativetime" data-value="2026-10-27T08:51:58+00:00" > 10/27/26, 08:51 </span>

    What exact chrome version are you using? There were bugs in Chromes integration of this toggle, so a browser update might help you.

    (It works on my machine, on macOS I need to use my “alt” key though)

  2. Peter Wijngaarden commented <span data-processor="relativetime" data-value="2026-10-27T15:45:49+00:00" > 10/27/26, 15:45 </span>

    Garvin Hicking wrote in #note-1:
    > What exact chrome version are you using? There were bugs in Chromes integration of this toggle, so a browser update might help you.
    >
    > (It works on my machine, on macOS I need to use my “alt” key though)

    I am using the following versions:

    Os: Windows

    Google Chrome: 156.0.8078.48

    TYPO3: 13.4.37

    The issue still occurs with this configuration. Using the Alt key does not work either.

  3. Garvin Hicking commented and changed status Needs Feedback Accepted <span data-processor="relativetime" data-value="2026-10-27T19:07:07+00:00" > 10/27/26, 19:07 </span>

    I can reproduce this on my Windows Chrome 155 browser indeed. I’ll look up what the issue was that I remember, I think some chrome core change caused this.

  4. Gerrit Code Review pushed patch set 1 for main to change 97177 status Accepted Under Review <span data-processor="relativetime" data-value="2026-10-27T19:59:28+00:00" > 10/27/26, 19:59 </span>

  5. Garvin Hicking commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-11-09T14:15:17+00:00" > 11/09/26, 14:15 </span>

    Applied in changeset commit:c0ae2c812cdf17d969c522bad534c70692e2b0f3.