Search Issue Tracker
By Design
By Design in 2023.1.X
Votes
0
Found in
2021.3.30f1
2022.3.9f1
2023.1.12f1
Issue ID
UUM-47804
Regression
No
Delegate registered through ListView.RegisterCallback<ClickEvent> method gets passed an incorrect target
Reproduction steps:
1. Open the "IN-53068.zip" project
2. Open "Assets/Scenes/SampleScene"
3. Enter Play mode
4. Press on the "hello0" Button and observe the Console
Expected results: "target: Button" is printed to the Console
Actual results: "target: ListView" is printed to the Console
Reproducible with: 2021.3.30f1, 2022.3.9f1, 2023.1.12f1, 2023.2.0a5
Not reproducible with: 2023.2.0b8, 2023.3.0a4
Fixed in: 2023.2.0a6
Reproducible on: macOS 13.4.1 (M1, Intel)
Not reproducible on: No other environment tested
Note: Reproducible in Standalone Player
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
Resolution Note:
ListView is a composite root, which makes the event set its target to it before trggering its callbacks. The composite root mechanisms are still internal in UI Toolkit so there is no way right now to go around this ambiguity, unfortunately. This is changed in 2023.2 and beyond.
Resolution Note (2023.1.X):
ListView is a composite root, which makes the event set its target to it before trggering its callbacks. The composite root mechanisms are still internal in UI Toolkit so there is no way right now to go around this ambiguity, unfortunately. This is changed in 2023.2 and beyond.