Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X, 2021.2.X
Votes
0
Found in
2019.3.0a11
Issue ID
1174816
Regression
Yes
[Editor] Highlighter does not work well
Hightlighter Feature does not work anymore
0. Using the default layout, select a game object in the Hiearchy window
1. Open Bug> Hightlighter Test
2. Enter Window Title "Inspector", Search Text "Scale", Seach Mode "Auto"
3. Click "Start Highlight"
2018.4: Scale component is correctly highlighted in the inspector window
2019.3:
- Highlight is seems to be displayed under the content (we only see the part that overlaps the scene View)
- Highlight position is not properly offsetted (worse if you hightlight stuff in components that are displayed lower)
The InspectorWindow was modified to use UIToolkit in 2019.1. It was broken down in sub ImguiContainers, that's why the offset is no right
The documentation also mention that the scrollview should scroll if the content is not in the view, that's probably broken as well
These other combinations show additional failures:
"Hierarchy", "Main Camera" -> console log "Item Main Camera not found in window Hiearchy
"Project", "Editor" -> console log "Item Editor not found in window Project
These all work as expected in 2018.4
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
- Manual reference page for Grid Selection is missing
- Awaitable.NextFrameAsync causes GC Alloc 0.7 KB when using CancellationToken
- Prefab "Overrides" list item popups are overridden when navigating with keyboard arrow keys
- Alpha Tolerance setting does not affect generated outlines when generating Custom Physics Shape in the Sprite Editor
- The information/help message section misses a margin in the "Profiler" window
Resolution Note (fix version 2020.2):
This is a duplicate of case 1281354 which contains more repro steps/information.
Resolution Note (fix version 2021.1):
Fixed in 2021.1.23f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.32f1