Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2018.3.0f2
2019.1.0a1
2019.2.0a1
Issue ID
1126150
Regression
No
Button is still intractable if second level parent canvas is disabled during runtime
Steps to reproduce:
1. Download and open the attached project
2. Enter Playmode
3. Disable Canvas component on top level Canvas gameobject
4. Click in the area where the button was
Expected result: button does not activate
Actual result: button gets activated even though it is not visible
Reproduced on 2017.4.0f1, 2017.4.20f2, 2018.3.5f1, 2019.1.0b3, 2019.2.0a5
Notes:
- This does not happen if the Canvas component is disabled before running, but will happen again if disabled during runtime
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (2019.2.X):
Low priority defect for the moment. This bug is unlikely to be fixed in the near future.