Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X
Votes
29
Found in
2019.4.13f1
2021.1.0a2
Issue ID
1287702
Regression
Yes
Double-clicking a script in the Inspector window does not open the External Script Editor
How to reproduce:
1. Create a new Unity project
2. Create a new script and attach it to any GameObject
3. In the Inspector window double-click the Script field
Expected result: the external script editor is opened
Actual result: nothing happens
Reproducible with: 2019.4.13f1, 2021.1.0a2
Not reproducible with: 2018.4.28f1, 2019.4.12f1, 2020.1.0a1, 2020.1.11f1, 2020.2.0b9, 2021.1.0a1
-
Rodolfo-Rubens
Oct 27, 2020 20:27
Not only the script object field, all the disabled object fields stopped being interactable, I have a lot of systems that shows disabled object fields and that bug broke them...
-
AcidArrow
Oct 27, 2020 10:12
What are you changing in an LTS version that breaks basic functionality like this?
Why wasn't this caught by QA before release?
Or was it caught but you decided it's not a blocker?
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] Build fails with built-in PAD custom asset(s) when using sample Addressable
- [iOS] nw_read_request_report crash
- The serialized field value cannot be changed when trying to set it back to "None"
- The dropdown component breaks when the 31st Layer is used
- Silent crash when GameObjects collide when transform.SetParent is used
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0a5
Resolution Note (fix version 2019.4):
Fixed in 2019.4.14f1