Search Issue Tracker
Duplicate
Votes
0
Found in
2018.4
2019.4
2020.2.1f1
2020.3
2021.1
2021.2
Issue ID
1315737
Regression
No
Event Trigger uses only the first component in the stack
Reproduction steps:
1. Open the user's attached project and SampleScene scene
2. In the Hierarchy window, select Canvas/Button
3. In the Inspector window, drag the Test (Script) component (the one that has the Proof field set to "Second") into PointerEnter event field
4. In the PointerEnter event, set Test/LogProof() as a function
5. Enter the Play mode
6. In the Game view, hover over the button and observe the Console window
Expected result: "Second" is logged
Actual result: "First" is logged
Reproducible with: 2018.4.32f1, 2019.4.20f1, 2020.3.0f1, 2021.1.0b9, 2021.2.0a7
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
This is a duplicate of issue #1309997