Search Issue Tracker
By Design
Votes
0
Found in
5.3.1p1
Issue ID
757828
Regression
No
Deleting a component doesn't break a prefab
Steps to reproduce the issue:
1. Create a new project
2. Add a component to an existing game object
3. Prefab the game object
4. Delete the component - no warning message appears that component is broken
vice versa:
It does show warning message when reordering a component - case 759447
Reproduced in 5.3.1p2 (9f9ed864cba4), 5.3.1p1 (7d3d8e90548b), 5.4.0b1 (3137382c8e08), 5.2.2p4 (93d0b2db7c56), 5.2.1p4 (9a78a9ce1e6c), 5.1.2p2 (207c2b8718a4)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment