Search Issue Tracker
Duplicate
Votes
0
Found in
2018.1.0b7
2018.1.0f2
Issue ID
1035491
Regression
Yes
Scriptable object inspector auto unlocks when entering play mode
How to reproduce:
1. Create empty Unity project
2. Create ScriptableObject script with at least one public field and make it creatable from the menu
3. Create ScriptableObject
4. Lock it in the inspector
5. Make sure game window is checked maximize on play
6. Enter play mode
7. Pause the game
8. Inspector is unlocked
Expected result: Inspector should remain locked all the time
Actual result: Inspector became unlocked after entering the play mode
Regression first introduced in: 2018.1.0b7
Reproducible with: 2018.3.0a1, 2018.2.0b4, 2018.1.0f2,
Not reproducible with: 2017.4.3f1, 2017.3.2f1, 2017.2.2p2, 2017.1.4f1
Note:
Bug similar to 1031140 but it can be reproduced with different versions
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
- [Build Callbacks] Build is not failing when BuildFailedException is thrown in the PostProcessScene Callback
- [Terrain] The function TerrainData.GetDetailLayer only returns 0 or 1
- [Windows 7] VideoPlayer.Prepare causes a stack overflow crash if Video is loaded from asset bundle
- [WebGL] Mouse input is blocked after a few moves when using Edge browser
- Builds that contain terrain using the Nature/Terrain/Standard shader produce errors when run in headless mode
This is a duplicate of issue #1031140