Search Issue Tracker
Fixed
Fixed in 2021.3.37f1, 2022.3.22f1, 2023.2.15f1, 6000.0.0b11
Votes
0
Found in
2021.3.34f1
2022.3.17f1
2023.2.6f1
2023.3.0b3
6000.0.0b11
Issue ID
UUM-60655
Regression
No
The “>” indicator is not shown for expandable menus when opening a submenus in the “Add Component” menu
How to reproduce:
1. Open the user’s attached “sw-2024-vr-take2.zip” project
2. Select any GameObject in the Hierarchy window
3. In the Inspector window, press the “Add Component” button
4. Select “Scripts”
5. Observe the result
Expected result: Expandable menus don't have a “>” indicator
Actual result: Expandable menus have a “>” indicator
Reproducible with: 2021.3.34f1, 2022.3.17f1, 2023.2.6f1, 2023.3.0b3
Reproduced on: macOS 13.6.3 (Intel)
Not reproducible on: No other environment 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
- Crash on mecanim::SetValueWeight when switching the AnimationMixerPlayable connection with Animator's UpdateMode set to "Animate Physics"
- The "StringComparer.InvariantCultureIgnoreCase.GetHashCode()" returns different Hash Codes for the same word with the only difference being case sensitivity in WebGL
- 2D Light Textures show the lights of any 'blend style' index higher than theirs (if present) when they aren't visible by the Camera using Render Graph
- [SpeedTree] Wireframe mode not rendering correctly ST assets
- Light2D affecting only the Default Sorting Layer will also affect any Custom Lit Sprite not on that Layer when using Render Graph
Resolution Note (fix version 6000.0.0b11):
Fixed in: 6000.0.0b11
Resolution Note (fix version 2023.2.15f1):
Fixed in: 2023.2.15f1
Resolution Note (fix version 2022.3.22f1):
Fixed in: 2022.3.22f1
Resolution Note (fix version 2021.3.37f1):
Fixed in: 2021.3.37f1