Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2020.3
2021.1
2021.2
2022.1
2022.1.0a5
Issue ID
1355782
Regression
Yes
No warning dialog is thrown when removing the last element if 2 GOs selected and Material in the Materials list is different
How to reproduce:
1. Open attached project "case_941.zip"
2. Open "Sample" scene
3. Select "Test" and "Test2" GameObjects in the Hierarchy
4. Expand materials list
5. Select last material in the list
6. Delete the selected materials
Expected result: Warning dialog is thrown
Actual result: No warning dialog is thrown
Reproducible with - 2022.1.0a4, 2022.1.0a5
Not reproducible with - 2019.4.28f1, 2020.3.15f1, 2021.1.16f1, 2021.2.0b6, 2022.1.0a3
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 ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note:
The warning dialog has been removed as part of the fix for issue 1277419. Previously removing the last element of a multi-selection array would end up changing all the remaining array elements to match the first object, so a special warning dialog was displayed. Now the correct behavior is implemented which is to only remove the last element and leave the other elements untouched, so the warning is no longer accurate nor needed.