Search Issue Tracker
Feature Request
Feature Request in 6000.5.X
Votes
0
Found in
6000.0.66f2
6000.3.7f1
6000.4.0b7
6000.5.0a6
Issue ID
UUM-133741
Regression
No
[Linux] Drag-and-drop functionality doesn’t work in Editor when using touchscreen
Steps to reproduce:
1. Create new Unity project
2. Using a touchscreen, try to drag “Scenes” folder into the “Settings” folder in Project window
3. Observe the Editor
Actual results: Touchscreen drag-and-drop functionality in the Editor doesn’t work
Expected results: Touchscreen drag-and-drop functionality in the Editor works
Reproducible with versions: 6000.0.66f2, 6000.3.7f1, 6000.4.0b7, 6000.5.0a6
Tested on (OS): Ubuntu 24.04
Device used for testing: Dell XPS 15 9510
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note:
Thank you for sharing your idea with Unity.
We reviewed your report and determined that it's a feature request rather than a bug. We've logged this request in our system so it can be evaluated for future roadmap planning.
We will close this case as a feature request. While we can't guarantee timelines, your feedback is important and helps us prioritize enhancements. If you have additional context or use cases, please share them.
Resolution Note (6000.5.X):
Thank you for sharing your idea with Unity.
We reviewed your report and determined that it's a feature request rather than a bug. We've logged this request in our system so it can be evaluated for future roadmap planning.
We will close this case as a feature request. While we can't guarantee timelines, your feedback is important and helps us prioritize enhancements. If you have additional context or use cases, please share them.