[GH-ISSUE #2151] Support drag and drop. #1861

Open
opened 2026-10-03 22:01:42 -06:00 by gitea-mirror · 3 comments
Owner

Originally created by @beedell-roke on GitHub (Oct 3, 2026).
Original GitHub issue: https://github.com/debauchee/barrier/issues/2151

What happened?

issues/855 has been prematurely closed.

If applicable, where did you install Barrier from?

Per the issues that it cites, drag and drop does not appear to work for anyone, irrespective of DE or OS. Consequently, this does not appear to matter.

Originally created by @beedell-roke on GitHub (Oct 3, 2026). Original GitHub issue: https://github.com/debauchee/barrier/issues/2151 ### What happened? [`issues/855`](https://github.com/debauchee/barrier/issues/855#issuecomment-5973693036) has been prematurely closed. <!-- ### Version From Git HEAD or commit (specify below) ### Git commit hash (if applicable) `HEAD` --> ### If applicable, where did you install Barrier from? Per the issues that it cites, drag and drop does not appear to work for anyone, irrespective of DE or OS. Consequently, this does not appear to matter. <!-- ### What OSes are you seeing the problem on? (Check all that apply) Linux ### What OS versions are you using? 〃 ### Relevant log output ```shell ``` ### Any other information _No response_ -->
Author
Owner

@beedell-roke commented on GitHub (Oct 3, 2026):

If this is considered to be an undesirable duplicate, please close it as a duplicate, and close it as a duplicate of the aforecited issue.

<!-- gh-comment-id:5974024447 --> @beedell-roke commented on GitHub (Oct 3, 2026): If this is considered to be an undesirable duplicate, please <em>close it as a duplicate</em>, and close it as a duplicate <em>of the aforecited issue</em>.
Author
Owner

@Rings4 commented on GitHub (Oct 3, 2026):

Thanks for opening a new issue for this. Never seen a dev close an issue without fixing it just because they're not active.

<!-- gh-comment-id:5974566450 --> @Rings4 commented on GitHub (Oct 3, 2026): Thanks for opening a new issue for this. Never seen a dev close an issue without fixing it just because they're not active.
Author
Owner

@beedell-roke commented on GitHub (Oct 3, 2026):

@Rings4, I have, a few times, unfortunately. warpdotdev/warp/issues/2083#issuecomment-4188923436 is a pertinent example.

<!-- gh-comment-id:5974737867 --> @beedell-roke commented on GitHub (Oct 3, 2026): @Rings4, I have, a few times, unfortunately. [`warpdotdev/warp/issues/2083#issuecomment-4188923436`](https://github.com/warpdotdev/warp/issues/2083#issuecomment-4188923436) is a pertinent example.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
github-starred/barrier#1861
No description provided.