Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.0.67f1
6000.3.8f1
6000.4.0b8
6000.5.0a7
Issue ID
UUM-134885
Regression
No
Context menu item checkmark updates only after reopening twice when using Menu.SetChecked on component context menu items
How to reproduce:
1. Open the attached “IN-130286_6_Test.zip” project
2. Open the “SampleScene” scene (Assets/Repro3/SampleScene)
3. Select the “Test” GameObject in the Hierarchy
4. In the Inspector, navigate to the ContextMenuActionTest script component
5. Open the component's context menu by right clicking
6. Select “Toggle Flag”
7. Notice the flag being set on the component
8. Open the context menu
9. Close the context menu
10. Open the context menu again
11. Observe the context menu
Actual result: The context menu checkmark updates only on the second open after changing the flag
Expected result: The context menu checkmark updates on the first open after changing the flag
Reproducible with: 2023.1.0a3, 6000.0.67f1, 6000.3.9f1, 6000.4.0b9, 6000.5.0a7
Reproducible on: MacOS Sequoia 15.7.3 (M1 Max)
Not reproducible on: No other environments tested
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
- GameObjects made using "GameObject.CreatePrimitive" appear pink in the Player when the default material is used
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.