Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
1
Found in
2020.3.36f1
2021.3.6f1
2022.1.8f1
2022.2.0b1
2023.1.0a3
2023.2.0a1
Issue ID
UUM-8492
Regression
No
Button is getting a "hover" state if the cursor is near when the Player is "Windowed" and full-screen size
How to reproduce:
1. Build And Run the “Qweasd.zip” project
2. Move the cursor near the top right towards the “Button” button
3. Observe the button
Expected result: Button doesn’t get hover state
Actual result: Button gets hover state
Reproducible with: 2020.3.36f1, 2021.3.6f1, 2022.1.8f1, 2022.2.0b1, 2023.1.0a3
Reproduced on: macOS 12.4 (Intel)
Notes:
- Not reproducible in the Editor
- Reproducible with macOS and Windows (user’s info) Standalone Players
- Reproducible just with “Windowed” Fullscreen Mode
- With Windows “Resizable Windows” setting should be set to true to be able to reproduce (user’s info)
- Reproducible when hovering from the bottom
- Reproducible when the windowed Player window is the same or a bit smaller than the screen size
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note:
The issue seems to have been fixed already: it can no longer be reproduced in 2021.3.11f1.
In addition, the problem also does not occur on 2022.2.6f1, neither on future 2023 versions.
Resolution Note (2023.2.X):
The issue seems to have been fixed already: it can no longer be reproduced in 2021.3.11f1.
In addition, the problem also does not occur on 2022.2.6f1, neither on future 2023 versions.