Search Issue Tracker
Won't Fix
Votes
1
Found in [Package]
1.19.19
1.21.21
2.1.0
Issue ID
ADDR-3720
Regression
No
DragUpdatedEvent and DragPerfomeEvent messages are printed when dragging and dropping an asset into an AssetReference field
Reproduction steps:
1. Open the attached “BugRepro” project
2. From the menu navigate to BugRepo > Test
3. From the Project window drag and drop “Assets/GameObject.prefab” into the Asset Reference field in the Test Window
4. Observe the Console window
Expected result: No messages are printed
Actual result: DragUpdatedEvent and DragPerfomeEvent messages are printed
Reproducible with: 1.19.19, 1.21.21 (2021.3.40f1, 2022.3.37f1), 2.1.0 (6000.0.10f1)
Reproducible on: Windows 11
Not reproducible on: No other environment tested
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
- Crash on PluginManager::RefreshPlugins when closing the Editor without making any changes with JetBrains Rider selected as the External Code Editor and Google Mobile Ads third-party plugin imported
- GetMainLight() returns incorrect distanceAttenuation value for a Custom Shader when URP Forward+ Rendering Path is used
- Standalone Profiler crash on GuidReservations::Reserve when it is opened on a specific project
- m_RenderPipelineGlobalSettingsMap or m_SRPDefaultSettings is pointing to UnityEngine.Rendering.HighDefinition.HDRenderPipeline when High Definition RP package is removed
- Rendering Debugger fields have no padding at the bottom of the fields list
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.