Search Issue Tracker
Won't Fix
Won't Fix in 6000.4.X
Votes
0
Found in
6000.3.8f1
6000.4.0b8
Issue ID
UUM-133943
Regression
No
UI Document Element Tooltip does not display whole text when using vOffset label
Reproduction steps:
1. Create a new project and make sure new Hierarchy window is enabled
2. Enable Hierarchy Integration in Project Settings (Edit > Project Settings… > UI Toolkit)
3. GameObject > UI Toolkit > UI Document
4. Press "New" button in Source Asset field in the Inspector of UIDocument GameObject
5. Open UI Builder window by double-clicking on newly created UI Document
6. Drag and drop Label Element into Hierarchy
7. Enter Label text wit vOffset label (e.g. "Up <voffset=1em>up <voffset=2em>UP</voffset> and <voffset=-0.5em>down</voffset> we go again.Up <voffset=1em>up <voffset=2em>UP</voffset> and <voffset=-0.5em>down</voffset> we go again.Up <voffset=1em>up <voffset=2em>UP</voffset> and <voffset=-0.5em>down</voffset> we go again.")
8. Change Overflow to "hidden" and Text Overflow to "ellipsis"
9. Hover over Label Element in the Editor Hierarchy
Actual result: Some parts of the text at the bottom are cut off
Expected result: Whole text is displayed
Reproducible with: 6000.3.8f1, 6000.4.0b8
Not reproducible with: 6000.5.0a6
Couldn’t reproduce with: 6000.0.67f1 (No Enable Hierarchy Integration option)
Reproduced on: macOS Sequoia 26.2 (M4)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.4.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.