Bug #66541
closed
Content droppable in dropzones outside of the viewport
0%
Description
When using drag & drop the drop zones before or after elements are activated even when the dropzone itself is outside of the view port.
This leads to unwanted move actions, when the user stops dragging the element around without noticing the dropzone that is currently active.
IMHO dropzones should not be activated when hovering a content element but when hovering the dropzone itself only.
Updated by Jo Hasenau about 9 years ago
Same issue here as with #66542: The change from draggable to sortable introduced the current behaviour. Instead of using the drop zones as trigger, now hovering the elements themselves triggers the dropzones. So a larger element with a lot of preview content inside can trigger a dropzone which is not visible in the viewport.
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/38861
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/38861
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/38861
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/38861
Updated by Gerrit Code Review about 9 years ago
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 about 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 Daniel Goerz almost 9 years ago
- Status changed from Under Review to Needs Feedback
Since the patch was abandoned, can this issue be closed or does it need a new patch?
Updated by Jo Hasenau almost 9 years ago
Well - there is #67134 which provides a solution for this problem, but maybe we should cut that part off that issue and provide a separate patch for it here.
The actual problem has been the switch from droppable to sortable, which changes some behaviours to the worse, while some other problems have been fixed by it.
I discussed that already with Andreas Fernandez and we came to the conclusion, that sortable should be used for list like structures only, while the page module should be switched back to droppable.
To finally have structure containers in the core, we will have to switch to droppable anyway, since this would be a real PITA for editors with sortable.
So maybe it would be a good idea to change D&D now, while containers will have to wait for upcoming versions.
Updated by Susanne Moog almost 9 years ago
- Target version changed from 7.4 (Backend) to 7.5
Updated by Alexander Opitz over 8 years ago
- Status changed from Needs Feedback to New
- TYPO3 Version changed from 7 to 8
Updated by Riccardo De Contardi about 7 years ago
- Status changed from New to Closed
- Assignee deleted (
Jo Hasenau)
The core is back on Droppable with CMS 8: the dropzones become green and are activated when an element is placed upon them
so I think that this could be safely closed.
If you experience the issue again then please reopen it or open a new issue with a reference to this one. Thank you
Updated by Coders.Care Extension Team over 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)