[#74552] Wrong pane (Backlog/Buckets, not Sprints) autoscrolls#23117
Merged
myabc merged 2 commits intorelease/17.4from May 8, 2026
Merged
[#74552] Wrong pane (Backlog/Buckets, not Sprints) autoscrolls#23117myabc merged 2 commits intorelease/17.4from
myabc merged 2 commits intorelease/17.4from
Conversation
myabc
changed the title
Contributor
There was a problem hiding this comment.
Pull request overview
This PR fixes a Backlogs drag-and-drop regression where dragging from the backlog/buckets pane into a sprint could autoscroll the wrong pane by reverting the mirrorContainer customization and letting Dragula use its default mirror container behavior again.
Changes:
- Removed the optional
mirrorContainerStimulus target and the corresponding Dragula option fromgeneric-drag-and-drop. - Updated Backlogs inbox and backlog buckets to no longer declare themselves as
mirrorContainertargets (now onlycontainer). - Removed specs that asserted the old
mirrorContainerbehavior.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| modules/backlogs/spec/requests/backlogs/backlog_spec.rb | Removes request-level assertions around mirrorContainer rendering for inbox/buckets. |
| modules/backlogs/app/components/backlogs/inbox_component.rb | Stops rendering mirrorContainer as a drag-and-drop target on the inbox BorderBox. |
| modules/backlogs/app/components/backlogs/backlog_bucket_component.rb | Stops rendering mirrorContainer as a drag-and-drop target on backlog bucket BorderBoxes. |
| frontend/src/stimulus/controllers/dynamic/generic-drag-and-drop.controller.ts | Removes mirrorContainer target support and no longer passes mirrorContainer to Dragula. |
| frontend/src/stimulus/controllers/dynamic/generic-drag-and-drop.controller.spec.ts | Removes unit tests for the deleted resolveMirrorContainer behavior. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ticket
https://community.openproject.org/wp/74552
What are you trying to accomplish?
Fix a Backlogs drag-and-drop regression where dragging a work package from the backlog/bucket pane into a sprint can autoscroll the backlog side instead of the sprint side (seen in Firefox and Crome).
This effectively reverts the drag-preview/mirror-container behavior introduced or expanded in:
Screenshots
What approach did you choose and why?
Remove the optional
mirrorContainertarget from the generic drag-and-drop Stimulus controller and stop marking the Backlogs inbox/buckets as mirror containers. This lets Dragula append the drag mirror to its default container again, which avoids the wrong pane being selected for autoscroll while dragging backlog items into sprint lists.Merge checklist