Search Issue Tracker
Fixed
Fixed in 6000.0.7f1, 6000.1.0b12, 6000.2.0a8
Votes
5
Found in
6000.0.0b12
6000.1.0a7
6000.2.0a1
7000.0.0a1
Issue ID
UUM-67390
Regression
No
Property Attributes don't affect regular fields when "ApplyToCollection" is set to true
Steps to reproduce:
1. Open the “CollectionAttributesBug.zip” project
2. Open the "SampleScene"
3. Open the "ReadOnlyAttribute” script (Assets > Scripts)
4. Confirm that the “PropertyAttribute.applyToCollection” flag is set to true
5. In the Hierarchy window, select the “AttributeExample” GameObject
6. Observe the fields in the Inspector window
Expected results: regular fields are read-only
Actual results: regular fields lose the read-only attribute when applyToCollection is true
Reproducible with: 6000.0.b12
Couldn’t test with: 2021.3.36f1, 2022.3.21f1, 2023.2.13f1 ({{Assets\Scripts\ReadOnlyAttribute.cs(5,31): error CS1729: 'PropertyAttribute' does not contain a constructor that takes 1 argument}})
Reproducible on: Windows 10 (by reporter), Windows 11
Not reproducible on: No other environment tested
Comments (1)
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
v0lt1369
Dec 08, 2024 03:01
The bug has only been fixed in Unity 6 for regular fields but nested fields still have this issue.