#107970Drag & Drop page-module issue with latest Chrome version
Description
Since latest Chrome update, it’s not possible to drag & drop content in the page module – the mouse cursor is showing the + (for copy content) by default and is creating copies instead of moving the content elements.
Pressing “Control” the cursor looks like “moving content”, but it’s nothing happening (event though the inspector console is empty + no request in network tab).
Tested on different TYPO3 13 versions and different browsers on Mac (Chrome, Firefox, Safari) – it’s only happening in Chrome.
One of our customers recognized the same issue with Chrome on Windows, so it seems not to be depending on the OS.
TYPO3 issue or do we have to wait for a new Chrome version?
Thanks in advance,
David
Reviews 5
- 13.4 97422[BUGFIX] Properly recognize Ctrl+Drag and Drop on Windows Chrome
- 14.3 97421[BUGFIX] Properly recognize Ctrl+Drag and Drop on Windows Chrome
- main 97177[BUGFIX] Properly recognize Ctrl+Drag and Drop on Windows Chrome
- main 91580[BUGFIX] Prevent unexpected drag & drop element duplication in Chrome
- main 91667[BUGFIX] Correction of moving and copying of content elements
Related issues 1
Files 1
History 1730
Show 5 earlier messages
-
Jens Engelmann commented <span data-processor="relativetime" data-value="2025-11-04T09:45:38+00:00" > 11/04/25, 09:45 </span>
-
Pierre Frumillon commented <span data-processor="relativetime" data-value="2025-11-04T14:36:54+00:00" > 11/04/25, 14:36 </span>
Hello, Bug since chromium 142 (tested on mac).
Problem found in vendor/typo3/cms-backend/Resources/Public/JavaScript/utility/drag-drop-utility.jsFixed form me with overiding this method like this :
DragDropUtility.isCopyModifierFromEvent = function (event) { // Correction pour Chromium 142+ // Vérifie manuellement les touches de modification if (event.ctrlKey || event.metaKey) { return true; // copier } // SHIFT ou rien -> move if (event.shiftKey || (!event.ctrlKey && !event.altKey && !event.metaKey)) { return false; // déplacer } }; -
Rony Khoury commented <span data-processor="relativetime" data-value="2025-11-05T09:27:53+00:00" > 11/05/25, 09:27 </span>
Hello @hoeckele:
Thanks for opening this issue. I’m also experiencing the same issue. I tested it with the following two browsers:- Google Chrome browser (142.0.7444.59): Drag&Drop is broken
- Firefox (144.0): Drag&Drop works as expected
Hello @pistil-studio:
In which browsers did you test your code? Is this a viable solution for this issue?
-
Christoph Dietrich commented <span data-processor="relativetime" data-value="2025-11-05T10:49:08+00:00" > 11/05/25, 10:49 </span>
Can confirm the problem in MacOS Chrome 142.0.7444.60.
-
Rony Khoury commented <span data-processor="relativetime" data-value="2025-11-05T15:15:48+00:00" > 11/05/25, 15:15 </span>
I totally forgot that I’ve opened a ticket to the same issue a couple of month ago.
See this ticket: https://forge.typo3.org/issues/106403
-
Riccardo De Contardi changed Related to #106403 <span data-processor="relativetime" data-value="2025-11-05T15:26:34+00:00" > 11/05/25, 15:26 </span>
-
Pavitro Papadopoulos commented <span data-processor="relativetime" data-value="2025-11-05T16:14:45+00:00" > 11/05/25, 16:14 </span>
@Rony Khoury Bug #106403 has just the opposite effect.
But I can confirm the drag&drop issue without key in Chrome only.
I tried Pierre’s fix and it worked well. -
Julian Mair commented <span data-processor="relativetime" data-value="2025-11-10T12:39:48+00:00" > 11/10/25, 12:39 </span>
Can confirm the problem in Ubuntu Chrome 142.0.7444.59 and on the latest Windows Chrome builds
-
Max Frerichs commented <span data-processor="relativetime" data-value="2025-11-12T10:27:05+00:00" > 11/12/25, 10:27 </span>
You can reproduce the issue here, outside of TYPO3:
https://jsfiddle.net/fqj8a20r/4/tl;dr: the dropEffect property of the DragEvent is always changed to “copy” when the dragenter event is fired, regardless of its previous property value (dropEffect is only once set to ‘move’ when dragstart event is fired) – which causes TYPO3 to create copies instead of moving the element in turn.
Edit: Looks like it’s a regression in Chromium:
https://issues.chromium.org/issues/434151262 -
Gerrit Code Review pushed patch set 1 for main to change 91580 status
NewUnder Review <span data-processor="relativetime" data-value="2025-11-12T12:51:34+00:00" > 11/12/25, 12:51 </span> -
Gerrit Code Review pushed patch set 2 for main to change 91580 <span data-processor="relativetime" data-value="2025-11-12T13:45:56+00:00" > 11/12/25, 13:45 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 91580 <span data-processor="relativetime" data-value="2025-11-12T21:20:06+00:00" > 11/12/25, 21:20 </span>
-
Česlav Przywara commented <span data-processor="relativetime" data-value="2025-11-13T08:41:53+00:00" > 11/13/25, 08:41 </span>
Related Chromium bug report: https://issues.chromium.org/issues/458071607
It’s a bit unclear to me from the discussion there whether this is going to be treated as regression or they just keep it that way.
-
Friedemann Altrock commented <span data-processor="relativetime" data-value="2025-11-13T10:49:26+00:00" > 11/13/25, 10:49 </span>
JSBin example (same code as the JSFiddle posted by Max Frerichs): https://jsbin.com/joqafixuwe/edit?html,js,console,output
-
Gerrit Code Review pushed patch set 4 for main to change 91580 <span data-processor="relativetime" data-value="2025-11-13T13:24:32+00:00" > 11/13/25, 13:24 </span>
-
Gerrit Code Review pushed patch set 5 for main to change 91580 <span data-processor="relativetime" data-value="2025-11-13T13:33:10+00:00" > 11/13/25, 13:33 </span>
-
Tung Ngo commented and changed attached Screen Recording 2025-11-13 at 15.22.26.mov <span data-processor="relativetime" data-value="2025-11-13T14:46:33+00:00" > 11/13/25, 14:46 </span>
Added a video illustrating the issue, which I also encountered today.
-
Gerrit Code Review pushed patch set 6 for main to change 91580 <span data-processor="relativetime" data-value="2025-11-13T15:13:48+00:00" > 11/13/25, 15:13 </span>
-
Gerrit Code Review pushed patch set 7 for main to change 91580 <span data-processor="relativetime" data-value="2025-11-13T15:35:22+00:00" > 11/13/25, 15:35 </span>
-
Gerrit Code Review pushed patch set 8 for main to change 91580 <span data-processor="relativetime" data-value="2025-11-14T09:38:40+00:00" > 11/14/25, 09:38 </span>
-
Gerrit Code Review pushed patch set 1 for main to change 91667 <span data-processor="relativetime" data-value="2025-11-14T12:44:04+00:00" > 11/14/25, 12:44 </span>
-
Gerrit Code Review pushed patch set 2 for main to change 91667 <span data-processor="relativetime" data-value="2025-11-14T13:24:15+00:00" > 11/14/25, 13:24 </span>
-
Friedemann Altrock commented <span data-processor="relativetime" data-value="2025-11-17T19:42:15+00:00" > 11/17/25, 19:42 </span>
FTR, the Chromium change that caused this is https://issues.chromium.org/issues/434151262
The linked specification page https://html.spec.whatwg.org/multipage/dnd.html is rather long, but does not seem to mandate any kind of consistent
effectAllowed/@dropEffect@ behavior which must be derived from keyboard modifiers. Chromium’s new (current) default to"copy"fordropEffect(as seen on this test page: https://wpt.live/html/editing/dnd/platform/modifiers/all.html) may be consistent with the spec.Also FTR, this is our documentation relevant to this feature: https://docs.typo3.org/m/typo3/tutorial-editors/main/en-us/ContentElements/Content/Index.html#copy-and-paste-content-elements :
> You can also copy content elements by pressing Ctrl during drag and drop. -
Gerrit Code Review pushed patch set 3 for main to change 91667 <span data-processor="relativetime" data-value="2025-11-20T10:47:51+00:00" > 11/20/25, 10:47 </span>
-
Gerrit Code Review pushed patch set 9 for main to change 91580 <span data-processor="relativetime" data-value="2025-11-26T18:33:45+00:00" > 11/26/25, 18:33 </span>
-
Gerrit Code Review pushed patch set 10 for main to change 91580 <span data-processor="relativetime" data-value="2025-11-26T18:35:37+00:00" > 11/26/25, 18:35 </span>
-
Josef Glatz commented <span data-processor="relativetime" data-value="2025-11-28T11:27:37+00:00" > 11/28/25, 11:27 </span>
Chrome 142.0.7444.176 → problem does not appear
but for example: Arc browser based on Chromium 142.0.7444.176 → problem does still appear. -
Benjamin Franzke commented <span data-processor="relativetime" data-value="2025-11-28T12:37:13+00:00" > 11/28/25, 12:37 </span>
Very likely related to https://issues.chromium.org/issues/458617018 which has been fixed upstream.
-
Friedemann Altrock commented <span data-processor="relativetime" data-value="2025-11-28T13:07:55+00:00" > 11/28/25, 13:07 </span>
Test page for verification: https://projects.faltrock.de/typo3/drag-drop.html
Buggy, always copy:- Windows 10 (22H2), Google Chrome 142.0.7444.176
- Windows 10 (22H2), Microsoft Edge 142.0.3595.94
- Ubuntu 24.04.3, Chromium Stable 142.0.7444.175
- Windows 11 (25H2), Google Chrome 142.0.7444.176
- Windows 11 (24H2), Microsoft Edge 142.0.3595.94
- Windows 11 (25H2), Vivaldi 7.7.3851.56 = Chromium 142.0.7444.220
- Windows 10 (22H2), Google Chrome Beta 143.0.7499.40
- macOS 15.7.1, Firefox 145.0.2
- macOS 15.7.1, Google Chrome 142.0.7444.176
- macOS 15.7.1, Vivaldi 7.7.3851.56 = Chromium 142.0.7444.220
- Windows 10 (22H2), Firefox 145.0.2
- Ubuntu 24.04.3, Firefox 145.0.2
🔜 Microsoft Edge 143 is scheduled for release on December 4th, 2025
🔜 Google Chrome will release 143 on December 2nd, 2025. -
Georg Ringer commented and changed status
Under ReviewClosed <span data-processor="relativetime" data-value="2026-02-04T20:24:50+00:00" > 02/04/26, 20:24 </span>closing issue as this has been fixed in chromium.
Are you sure that’s a Chrome issue? Do you have a touchscreen device? I encounter the same problem, but only on my touch-enabled laptop… when using another device (without touchscreen) it works as expected.
EDIT: Nevermind… I had different Chrome versions on the devices.