Search Issue Tracker
Won't Fix
Won't Fix in 2021.3.X
Votes
0
Found in
2021.3.36f1
Issue ID
UUM-66007
Regression
No
Button triggers another Button when multiple displays are used
How to reproduce:
1. Open the “bug-uitoolkit-multidisplay“ project
2. Make sure you have at least an additional display connected
3. Build And Run
4. In the secondary display’s Player select one of the buttons
5. Observe the primary display’s Player
Expected result: Both button events are independent of each other
Actual result: The buttons from “Display 2” trigger the buttons from “Display 1”
Reproduced with: 2021.3.36f1, 2022.3.20f1
Not reproduced with: 2023.2.14f1, 2023.3.0b10
Fixed in: 2022.3.21f1
Reproduced on: Windows 11
Not reproduced on: No other environment tested
Notes:
1. Running a 3-display setup, the tertiary display’s Player buttons don’t respond at all
2. Could not test in the Editor → Could not find a way to display multiple scenes on different displays
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
- 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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (2021.3.X):
Porting this fix to 2021.3 requires porting more important changes that go with it, which are too risky to include in 2021.3, given the value of keeping this release as stable as possible.