Search Issue Tracker
Fixed
Fixed in 2021.3.13f1, 2022.1.23f1, 2022.2.0b15, 2023.1.0a17
Votes
1
Found in
2021.3.11f1
2022.1.17f1
2022.2.0b8
2023.1.0a10
Issue ID
UUM-15518
Regression
Yes
Canvas is still receiving input after the canvas was disabled
How to reproduce:
1. Open the user-attached project “Canvas Click 3.8”
2. Open the “SampleScene” scene and enter the Play Mode
3. Click the “Toggle canvas B” button
4. Click on the “Button A” button
5. Observe the Console
Expected result: “Clicked A” is logged in the Console
Actual result: “Clicked B” is logged in the Console
Reproduced with: 2021.3.5f1, 2021.3.11f1, 2022.1.6f1, 2022.1.17f1, 2022.2.0a4, 2022.2.0b8, 2023.1.0a10
Not reproduced with: 2020.3.40f1, 2021.3.4f1, 2022.1.5f1, 2022.2.0a3
Reproducible on: Windows 11 Pro, macOS 12.4 (M1)
Note: Also reproducible in 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
- 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
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (fix version 2023.1.0a17):
Fixed various issues with Canvas.
Resolution Note (fix version 2022.2.0b15):
Fixed various Canvas issues
Resolution Note (fix version 2022.1.23f1):
Fixed various Canvas issues
Resolution Note (fix version 2021.3.13f1):
Fixed in: 2021.3.13f1