Search Issue Tracker
Fixed in 1.0.0
Votes
3
Found in [Package]
1.0.0
Issue ID
1332917
Regression
No
Hover state resets when there is another UI Toolkit element in the same UIDocument that is rotated or moved
Reproduction steps:
1. Open user's project "FontTest.zip"
2. Open "SampleScene" Scene
3. Enter Play Mode
4. Notice how the "Rotate me!" label rotates
5. Hover the mouse cursor over the "Hover over me" label and notice how it acts
6. Click on the "Stop rotation" button, notice how the "Rotate me!" label stops rotating, and repeat 5th step
Expected result: "Hover over me" label gets stable red background when hovering over it both when the "Rotate me!" label is rotating and when it's stationary
Actual result: "Hover over me" label gets red background that flickers and is not stable when the "Rotate me!" label is rotating and is stable when it's stationary
Reproducible with: 1.0.0-preview.14 (2020.3.9f1, 2021.1.8f1), 1.0.0 (2022.1.0a2)
Couldn't test with: 2018.4, 2019.4 (UI Toolkit package is not available), 2021.2 (UI Toolkit package is not supported and breaks the project)
Note: Similar results are observed when the "Rotate me!" label is moved using Transform.position
Comments (1)
-
manuelgoellnitz
Aug 25, 2021 13:12
This also happens when the an element is scaled or the style is changed and the mouse is moved.
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 1.0.0):
Fixed in: 2022.1.0a3