Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.0.41f1
Issue ID
UUM-99402
Regression
Yes
The ":hover" style remains applied to the buttons from the previously displayed page when switching the display of parent VisualElements
Reproduction steps:
1. Open the attached “IN-95580“ project
2. Open the “SampleScene”
3. Enter Play mode
4. Open the Simulator view
5. Click on different buttons multiple times
6. Observe the buttons in the Simulator view
Expected result: The hover style (red color) only appears while a button is being pressed
Actual result: The hover style stays on the buttons in the previous page
Reproducible with: 6000.0.29f1, 6000.0.41f1
Not reproducible with: 2022.3.59f1, 6000.0.28f1, 6000.1.0b9, 6000.2.0a6
Reproducible environments: macOS 15.3.1 (M3 Max)
Not reproducible environments: No other environments tested
Reproducible with these devices:
VLNQA00516 - samsung Galaxy Fold (SM-F900F), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 10
VLNQA00372 - Galaxy S21 5G (SM-G991U), CPU: Snapdragon 888, GPU: Adreno 660, OS: 12
VLNQA00391 - Xiaomi Redmi 9A (M2006C3LG), CPU: MediaTek Helio G25 (MT6762G), GPU: PowerVR Rogue GE8320, OS: 10
VLNQA00591 - samsung Galaxy S23 (SM-S911B), CPU: Snapdragon 8 Gen 2 (SM8550), GPU: Adreno 740, OS: 14
Note: This is in the discussions here: https://discussions.unity.com/t/incorrect-display-of-the-hover-style-in-the-simulator-and-on-mobile-devices-android/1602656/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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Resolution Note:
This bug was fixed in 6.1 and 6.2 and was considered too risky to backport to 6.0. 6.1 general release is coming soon and it is recommended to update to 6.1.