Search Issue Tracker
By Design
By Design in 6000.4.X, 6000.5.X
Votes
0
Found in
2022.3.62f1
6000.0.49f1
6000.1.3f1
6000.2.0b1
6000.3.0a1
6000.5.0a1
Issue ID
UUM-105144
Regression
No
The font for the Position and Rotation Transform of the Prefab is bold when it is added to the Hierarchy
How to reproduce:
1. Open the “2172788PrefabIssues“ project
2. Open the “SampleScene”
3. Drag and drop the “GameObject“ Prefab from the Assets folder into the Scene view
4. Observe the font of the “GameObject“ Prefab’s Position and Rotation in the Inspector
Expected result: The font is not bold
Actual result: The font is bold
Reproducible with: 2022.1.0a6, 2022.3.62f1, 6000.0.49f1, 6000.1.3f1, 6000.2.0b1
Reproducible on: Windows 10
Not reproducible on: no other environment tested
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
- Video preview in the Inspector freezes shortly after the first play and does not recover until paused and replayed
- MSB3277 conflicts between different versions of "System.Numerics.Vectors" when using DotNet 11.0
- "Cannot create Settings Providers for: CreateAllChildSettingsProviders" error is thrown in the Console after fixing PolySpatial visionOS package validation error after installing XR Interaction Toolkit VisionOS Sample
- "Unable to find style 'VideoClipImporterLabel' in skin 'GameSkin' " warning thrown when converting the Video Clip Inspector to a floating window in Play mode
- Unclear "Failed to start primary listening socket" error when launching the Multiplayer Play Mode second player and many Unity instances are running
Resolution Note:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
The observed behavior is due to some overrides function as implicit defaults. At this time, we cannot safely implement this UX enhancement.
However, we acknowledge the impact and aim to consider this in a future software update.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
The observed behavior is due to some overrides function as implicit defaults. At this time, we cannot safely implement this UX enhancement.
However, we acknowledge the impact and aim to consider this in a future software update.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
The observed behavior is due to some overrides function as implicit defaults. At this time, we cannot safely implement this UX enhancement. However, we acknowledge the impact and aim to consider this in a future software update.
Resolution Note (6000.4.X):
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
The observed behavior is due to some overrides function as implicit defaults. At this time, we cannot safely implement this UX enhancement. However, we acknowledge the impact and aim to consider this in a future software update.