Bug #66542
closed
Drag & Drop can not be stopped without really dropping an element into a dropzone
0%
Description
While dragging elements around sometimes it can happen that the user clicked on the wrong element and now wants to just stop dragging to select another element.
Currently this seems to be not possible anymore, since as soon as there is an active dropzone you can not stop dragging without really dropping the element.
Updated by Jo Hasenau about 9 years ago
It seems that the source of the problems with this issue and the one described in #66541 is the fact that D&D functionality has been switched from draggable to sortable.
Now the triggers for a drop action are not the dropzones anymore but the other items of the sortable container.
This means you can be either on the upper or the lower half of an item, which will then trigger the dropzone accordingly, but there is nothing in between anymore.
This again means, you can not stop dragging without sorting/dropping, since there will always be at least one active dropzone.
Updated by Gerrit Code Review about 9 years ago
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/38865
Updated by Gerrit Code Review about 9 years ago
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/38865
Updated by Gerrit Code Review about 9 years ago
Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/38865
Updated by Gerrit Code Review about 9 years ago
Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/38865
Updated by Gerrit Code Review about 9 years ago
Patch set 5 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/38865
Updated by Gerrit Code Review about 9 years ago
Patch set 6 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/38865
Updated by Gerrit Code Review about 9 years ago
Patch set 7 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/38865
Updated by Gerrit Code Review almost 9 years ago
Patch set 8 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/38865
Updated by Jo Hasenau almost 9 years ago
Can be fixed by switching back to draggable instead of sortable.
Sortable should be used for the list module, while the page module should be switched back to draggable.
Updated by Benni Mack almost 9 years ago
- Target version changed from 7.2 (Frontend) to 7.4 (Backend)
Updated by Susanne Moog over 8 years ago
- Target version changed from 7.4 (Backend) to 7.5
Updated by Benni Mack over 8 years ago
- Target version changed from 7.5 to 7 LTS
Updated by Nicole Cordes over 8 years ago
- Status changed from Under Review to Needs Feedback
The patch was abandoned. Can this issue be closed?
Updated by Benjamin Kott over 8 years ago
- Status changed from Needs Feedback to Closed
Unable to reproduce, seems to be resolved.
Updated by Coders.Care Extension Team about 6 years ago
- Related to deleted (Task #67134: The core must provide structured content elements which are configurable similar to backend layouts out of the box)