Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Positioning of CEs broken while drag-n-drop is active #490

Open
rr-it opened this issue Apr 4, 2024 · 5 comments
Open

Positioning of CEs broken while drag-n-drop is active #490

rr-it opened this issue Apr 4, 2024 · 5 comments

Comments

@rr-it
Copy link

rr-it commented Apr 4, 2024

CEs from inside a container element are wrongly positioned while drag-n-drop is active.

In this example you can still see the dragged CE. If the CE is further down the page you can't see it at all.
container-ce-dragndrop

@rr-it
Copy link
Author

rr-it commented Apr 4, 2024

Related TYPO3 core issue:
https://forge.typo3.org/issues/103536

@rr-it
Copy link
Author

rr-it commented Apr 4, 2024

@dbruening
Copy link

Unfortunately, the approach in the core issue does not solve the problem. position: relative; is necessary because the top, left, right values are set using JavaScript. I suggest an incorrect value calculation of the top value for the elements within the container.

@rr-it
Copy link
Author

rr-it commented Aug 20, 2024

For TYPO3 v12 there won't be any fix in core - even though v12 is still in "Regular Maintenance" ( https://typo3.org/cms/roadmap#section-support-times ).
So we should implement a fix in b13/container especially for TYPO3 v12.
See https://review.typo3.org/c/Packages/TYPO3.CMS/+/83650/comments/9c008db0_c0de45e8

For TYPO3 v13 core merger doesn't see an actual bug here and only merges a change as 'feature' or 'task'.
See https://review.typo3.org/c/Packages/TYPO3.CMS/+/83650/comments/42950ee1_7e0fccff

If the core needs "fixing" we might want to get any change into TYPO3 v13 before it gets released:

  • 13.3 "Feature freeze": estimated 2024-09-17
  • 13.4 "LTS-release": estimated 2024-10-15

@simonschaufi
Copy link

so can this be fixed in the extension or must this be fixed in the core?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants