Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.1.0a6
Issue ID
1093894
Regression
No
Removing Packages causes custom Windows which depend on the Package to become unresponsive
How to reproduce:
1. Create a new Unity project
2. Make sure TextMeshPro is imported
3. Open up TextMeshPro's "Sprite Importer" Window
4. Uninstall/Remove TextMeshPro
5. Notice how the "Sprite Importer" Window becomes unresponsive
Expected result: The Window can be moved and has a Close button
Actual result: The Window cannot be moved and does not have a Close button
Reproducible with: 2017.4.0f1, 2017.4.14f1, 2018.1.9f2, 2018.2.14f1, 2018.3.0b7, 2019.1.0a6
Notes: This seems to reproduce with every custom Window. The Window can still be closed via the drop-down menu accessible at the top right of the window.
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
- 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
Resolution Note:
this was marked in the product board. it needs a discussion at the N* level.