Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2019.1.X
Votes
0
Found in
2019.1.0a5
2019.2.0a1
Issue ID
1115796
Regression
Yes
The UI Scrollbar component blocks Prefab Mode in Play Mode
If you attempt to edit a prefab with a UI Scrollbar component attached while in playmode, you'll get the following warning:
Prefab Mode in Play Mode was blocked by the script 'Scrollbar' to prevent the script accidentally affecting Play Mode. See the documentation for [ExecuteInEditMode] and [ExecuteAlways] for info on how to make scripts compatible with Prefab Mode during Play Mode.
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)
Looks like this first appeared in 2019.1.0a5
1. Install Unity
2. Open the attached project
3. Enter Play Mode
3. Navigate to Assets > Canvas.prefab
4. Attempt to open Canvas.prefab in isolation mode
Expected Result:
The prefab is opened in isolation mode for editing.
Actual Result:
Isolation mode is blocked from opening due to the Scrollbar component being present on the prefab.
Tested on Windows.
Occurs on 2019.2.0a1, 2019.1.0a14, 2019.1.0a5
Does not occur on 2018.3.0f2, 2019.1.0a4
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