Issue Bug Closed

#106403Copying a content element by holding down CTRL key does not work in Google Chrome on Gnome/wayland/linux

Rony Khoury 03/20/25, 15:39 updated 10/06/26, 08:04

Description

After upgrading to TYPO3 v13.4.7, copying content elements in the backend by pressing and holding down the CTRL key on the keyboard while dragging the content element no longer works. The content element will just be dragged to the new location without creating a copy of it.

Usually I work on a Linux laptop (currently running Fedora 41 with latest Gnome Desktop). Before upgrading to TYPO3 v13.4.7, dragging and dropping as well as copying content elements did work. Now, after the upgrade, it seems like the CTRL key on my keyboard is not recognized at all. I can only drag&drop but not copy anymore.

When I try it on a Windows laptop, the state of the CTRL key is recognized. I can drag&drop a content element and when I simultaneously hold down the CTRL key, I am able to create a copy of that content elmenet.

Reviews 3

History 6

  1. Benjamin Franzke commented and changed status New Needs Feedback <span data-processor="relativetime" data-value="2025-03-21T06:32:39+00:00" > 03/21/25, 06:32 </span>

    Yes, we are aware of this. (I’m running Fedora 41 with Gnome as well)
    …but it didn’t work in 13.4.6 with Chrome on Fedora 41 either.
    This is a chrome bug on wayland/linux: https://issues.chromium.org/issues/40068941

    Did you use Chrome/Chromium on Fedora/Gnome or another Browser?
    Please specifiy the browser in use and please recheck if it really worked in v13.4.6 on that browser.

  2. Rony Khoury commented and changed assigned to Benjamin Franzke <span data-processor="relativetime" data-value="2025-03-21T08:41:01+00:00" > 03/21/25, 08:41 </span>

    Hi Benjamin,

    I’m using the offical google-chrome-stable package, currently on version 134.0.6998.117 (64-Bit), on Gnome Wayland.

    I tried to recreate with a fresh TYPO3 installation with versions v13.4.5 and v13.4.6, but copying a content element also didn’t work in either of these versions. I’m also using the extensions b13/container and friendsoftypo3/content-blocks but installing these packages didn’t change anything (tested newer and older versions of the extensions).

    Very strange. I’m sure that the copy-feature did work prior to the upgrade. I upgraded to each Patch-Version separatly (13.4.5, 13.4.6, 13.4.7). Only after upgrading to v13.4.7 did I notice that I can’t use the copy feature any longer.

    Looking through my dnf install history, the last of google chrome update was a couple of weeks ago. So, I’m not sure if this has anything to do with my experience because I must have been on version 130 and newer while I was still able to use the copy-feature.

    The chrome issue report (your link) talks about older chrome versions (v120)? But it seems like it is still present in the latest version.

    Long story short: I can’t reproduce the behavior. But if you’re already aware of this problem, then it’s all good :-).
    Maybe you can just mark this bug report as a duplicate and link it to an older one that already handles this issue?

  3. Benjamin Franzke commented and changed subject Copying a content element by holding down CTRL key no longer works after upgrading to TYPO3 v13.4.7 Copying a content element by holding down CTRL key does not work in Google Chrome on Gnome/wayland/linux status Needs Feedback Accepted priority Should have Could have <span data-processor="relativetime" data-value="2025-03-21T09:07:50+00:00" > 03/21/25, 09:07 </span>

    Thanks for you feedback. I’ll mark this as an accepted bug (although it is an upstream issue), but not as a regression, as I’m not aware of another bug report (we only noticed this problem during our tests, but didn’t file an explicit bug report).
    I’ll also try to test to get some older chrome version installed.

    Another triggerpoint could be “chrome://flags/#ozone-platform-hint” – I’ve been using “Wayland” here since ages (for proper resolution scaling), but it seems it’s “auto” value switched to use wayland-if-possible by default nowadays.

  4. Georg Ringer commented and changed status Accepted Closed <span data-processor="relativetime" data-value="2026-10-06T08:04:56+00:00" > 10/06/26, 08:04 </span>

    as #107970 has been fixed because fixed in upstream chromium, I close it here as well