Search Issue Tracker
By Design
Votes
0
Found in
6000.1.0a6
6000.2.0a1
7000.0.0a11
Issue ID
UUM-90164
Regression
No
Weird behaviour in TextMeshPro Link Example sample when hovering over single letters after hovering over a word
Steps to reproduce:
- Open a Unity Project
- Import TextMeshPro Essential Resources via Window > TextMeshPro > Import TMP Essential Resources
- Import TextMeshPro Examples & Extras via Window > TextMeshPro > Import TMP Examples and Extras
- Open the '12 - Link Example.unity' scene at Assets > TextMesh Pro > Examples & Extras > Scenes
- Enter playmode
- Hover over a word in the game
- Observe how the word goes darker. This is expected behaviour
- Stop hovering over a word
- Hold down shift and hover over a letter in the game
- Observe how the letter gets bigger and turns yellow. This is expected behaviour
- Stop hovering over the letter
- Hover over a word while not holding shift
- While still hovering over the word, hold shift and start hovering over different letters of that word
Actual results: The hovering over a word style is still applied to the word and every letter is darker, however, as you hover over letters, when you stop hovering over them, they go back to their normal style.
Expected results: Either the hover style (darker) for hovering over a word stops when you hold shift, or when you stop hovering over a letter than that letter goes back to being darker and not back to their normal style.
Reproducible with versions: 7000.0.0a11, 6000.1.0a6, 6000.0.30f1, 2022.3.53f1, 2021.3.45f1
Not reproducible with versions: -
Can't test with versions: -
Tested on (OS): Windows 11
Notes: -
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
The sample as always been like this, if we don't have any real use case issue this won't be changed.