Bug #50576
closed
Page view should scroll when using drag&drop on pages higher than the viewport
Added by Benjamin no-lastname-given over 10 years ago. Updated over 6 years ago.
100%
Description
When reaching bottom or top of the page while dragging a content element the page should scroll to make it possible to drop the content anywhere on the page.
Updated by Ernesto Baschny over 10 years ago
- Category set to Backend User Interface
- Status changed from New to Accepted
- Priority changed from Must have to Should have
- Complexity set to medium
Indeed would be a nice enhancement to the page module.
Updated by Ernesto Baschny over 10 years ago
Jigal is working on that here at the CMS Sprint in Essen. Not so easy as the ExtJS drag&drop is difficult to configure, but he is trying hard. :)
Updated by Jo Hasenau over 10 years ago
We already got that for Gridelements 1.x and 2.x so maybe we can do something about it during the Gridelements weekend.
Otherwise Jigal might want to take a look at the code and just copy the appropriate parts.
IIRC one of the workarounds for a usable D&D + scrolling was to define a surrounding container as "display:table", since the D&D area was restricted to 100% width and height of the currently visible part, which made it impossible to drop anything outside that area, even though scrolling itself worked fine.
Updated by Ernesto Baschny over 10 years ago
- Tracker changed from Feature to Bug
This is indeed not solved yet, I think Jigal has not managed to finish his work on this. It would be great - Joey - if you could provide some patch for fixing this in the core. thanks!
Updated by Jo Hasenau over 9 years ago
Will be a task for the user experience week - should be easy to implement.
Updated by Jo Hasenau over 9 years ago
On the other hand: It's ACME - so maybe we can even tackle that here in Munich ;-)
Updated by Gerrit Code Review over 9 years ago
- Status changed from Accepted 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/32681
Updated by Gerrit Code Review over 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/32681
Updated by Gerrit Code Review over 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/35807
Updated by Gerrit Code Review over 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/35807
Updated by Gerrit Code Review over 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/35807
Updated by Gerrit Code Review over 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/35807
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/35807
Updated by Benni Mack about 9 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset e90d3d7d36fa438697b7acbe3024087738756d72.
Updated by Denis Mir about 9 years ago
This bug is still available in the 6.2 LTS which makes it awful to work with.
Updated by Riccardo De Contardi over 6 years ago
- Status changed from Resolved to Closed