Project

General

Profile

Actions

Task #101085

closed

Problems with Drag & Drop in Page layout

Added by Reto Gehrig over 1 year ago. Updated 4 months ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2023-06-15
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
12
PHP Version:
8.2
Tags:
Complexity:
Sprint Focus:

Description

I'm using the «container» extension and have noticed that when drag & drop content elements within the container, the content to be moved is stuck under the cursor by twice the distance. This can be irritating for the user. I identified the reason in the style class .t3-page-ce. Nesting this class moves the starting point for positioning the element.

.t3-page-ce {
  display:block;
  position: relative; /* -> remove to fix the problem */
  margin:var(--pagemodule-grid-spacing) var(--pagemodule-grid-inner-spacing);
  transition:height .4s ease-out;
  overflow:hidden;
}

If the positioning is not urgently needed, I would remove it.

In addition, I noticed that after moving the element, the styles "width, left, top" are set to "unset" in drag-drop.js. This in turn can lead to unwanted display. To counteract this, the following correction would make sense.

  /* Line 165 - 167 */
  e.target.style.width = '';
  e.target.style.left = '';
  e.target.style.top = '';

I hope these suggestions will help someone else.


Files


Related issues 1 (1 open0 closed)

Related to TYPO3 Core - Bug #103536: Backend Page Module - drag-n-drop of Content Elements has display glitch with EXT:containerUnder Review2024-04-04

Actions
Actions #1

Updated by Riccardo De Contardi 7 months ago

I think that this one describes the same issue https://forge.typo3.org/issues/103536

Could you please test the attached patch?

Actions #2

Updated by Riccardo De Contardi 7 months ago

  • Related to Bug #103536: Backend Page Module - drag-n-drop of Content Elements has display glitch with EXT:container added
Actions #3

Updated by Riccardo De Contardi 4 months ago

  • Status changed from New to Closed
  • Target version deleted (next-patchlevel)

I close this issue as a duplicate of #103536 which has already a patch attached.

Please continue the discussion there.

If you think that this is the wrong decision please reopen it or open a new issue with a reference to this one. Thank you.

Actions

Also available in: Atom PDF