Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X
Votes
0
Found in
2019.1.0b10
2020.3
2021.1
2021.1.3f1
2021.2
Issue ID
1335344
Regression
Yes
Serialized attribute cannot be focused and written in when it goes just before Dropdown field
How to reproduce:
1. Open the user's attached "DropdownBug" project
2. Open the Scene "SampleScene"
3. In the Hierarchy select the "TextAreaText" GameObject
4. In the Inspector press on the "Unfocusable" variable's field
Expected results: The field gets highlighted
Actual results: The field does not get highlighted
Reproducible with: 2019.1.0b10, 2019.4.26f1, 2020.3.8f1, 2021.1.7f1, 2021.2.0a17
Not reproducible with: 2018.4.35f1, 2019.1.0b9
Note:
- It was previously stated that any serialized field before "TextArea" can be focused and written into, any field after "TextArea" cannot, but it's actually the presence of the Dropdown right below it that causes the problem in this case. I managed to reproduce it without a TextArea, only with string fields before the Dropdown field.
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
- Multiple exceptions are thrown after exiting Play mode when Layout Group component is displayed in Debug Inspector and Padding section is expanded
- ScrollView elements are not restored to their original positions after removing a Layout Group with Undo action
- "Assembly with name already exists" errors are thrown when two packages with different technical names resolve to the same namespace
- A Select Scene Entry is added to Undo History when Deleting while a Scene is selected in the Hierarchy
- The Add Component Menu's back arrow accumulates phantom levels when the Menu is repeatedly opened into a Category and closed without selecting
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a20
Resolution Note (fix version 2021.1):
Fixed in 2021.1.13f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.14f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.30f1