Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2020.3.46f1
2021.3.20f1
2022.2.9f1
2023.1.0b6
2023.2.0a4
Issue ID
UUM-28683
Regression
No
ContextMenuItem does not correctly inherit when attempting to use it with child classes
How to reproduce:
1. Open the attached Project "TestProject"
2. In the Project Window select "Assets/ChildSO"
3. In the Inspector Window right-click either an element in the "Items" List, or the "Dummy 1" variable
Expected result: the context menu contains an entry from ContextMenuItem
Actual result: the context menu does not contain any custom entries
Reproducible with: 2020.3.46f1, 2021.3.20f1, 2022.2.9f1, 2023.1.0b6, 2023.2.0a4
Notes:
- The issue also reproduces with child MonoBehaviours
- ContextMenu correctly gets inherited by the child class
- ContextMenuItem does not see methods from a parent class
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
- Font character thickness does not adjust properly in UI Toolkit text when changing Bold Weight in Font Asset
- Multiple "[...] is inaccessible due to its protection level" errors are thrown when opening project with Unity Version Control installed
- Sorting icons are tiny and misaligned in Import Activity window
- The Undo system does not record HideFlags.HideInHierarchy changes
- [Linux] Bug Reporter window is in Light mode when the Editor theme is Dark mode
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, please contact your account manager or PRM if you’d like to discuss this specific case in more detail, or if you would like to provide additional information relating to the severity of this bug.
Resolution Note (2023.2.X):
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, please contact your account manager or PRM if you’d like to discuss this specific case in more detail, or if you would like to provide additional information relating to the severity of this bug.