Search Issue Tracker
Won't Fix
Votes
2
Found in [Package]
1.9.0
Issue ID
ISXB-415
Regression
Yes
InputSystem Hover function gets triggered when Standalone Builds are un-focused and hovering over GameObjects
How to reproduce:
1. Open the attached “IN-29317.zip” project
2. Open the Player Settings (Edit → Project Settings → Player)
3. Set the Fullscreen Mode setting to Windowed in the “Resolution and Presentation” section
4. Build the project with the “SampleScene” Scene added
5. Open any other application and place it next to the Player window
6. Focus the opened application and try to hover over the UI elements visible in the Build
Expected result: The Hover function does not get triggered
Actual result: The Hover function is triggered
Reproducible with: 1.1.1 (2020.3.46f1), 1.5.0 (2020.3.46f1, 2021.3.20f1, 2022.2.9f1, 2023.1.0b7, 2023.2.0a5), 1.8.3 (6000.0.3f1)
Not reproducible with: 1.0.2 (2020.3.46f1)
Reproducible on: Windows 11
Not reproducible on: macOS Ventura 13.1 (Intel)
Notes:
- “Reset And Disable Non-Background Devices” setting should prevent this issue from happening, but it does not
- To verify the regressed version, build the project in new folders for every build
- Only reproducible in Standalone Builds
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
- UnityLinker causes crash when outputting snapshot data for very large projects
- Camera Preview does not detect multiple cameras with same GameObject name
- Crash on TypeTreeIterator::Children() when renaming a corrupted asset while Asset Serialization is set to Mixed
- Cameras (Camera.targetDisplay) render only to Display 0 in the Player when Multi-Display setup is used and DX12 API is set
- [Vulkan] _CameraOpaqueTexture produces a feedback effect on Android Adreno devices when using Vulkan
Resolution Note:
There are no fixes planned for this Bug