Search Issue Tracker
Fixed
Fixed in 2022.2.0b10, 2023.1.0a11
Votes
0
Found in
2022.2.0a17
2023.1.0a1
Issue ID
UUM-3532
Regression
No
Highlighted element is not being scrolled to when calling Highlighter.Highlight
How to reproduce:
1. Open the attached project "case_1379559.zip"
2. Open the "SampleScene" Scene
3. Open the HighlighterTest window (Bug > HighlighterTest) and dock it together with the Project window
4. Select the "Directional Light" GameObject in the Hierarchy
5. Make sure that the "Rigidbody 2D" Component is not visible in the Inspector
6. Press "Start Highlight" in the HighlighterTest window
Expected result: The "Rigidbody 2D" Component is first scrolled to and then highlighted
Actual result: The "Rigidbody 2D" Component is highlighted but not scrolled to
Reproducible with: 2019.4.33f1, 2020.3.24f1, 2021.2.5f1, 2022.1.0a16
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Add comment