Search Issue Tracker
Won't Fix
Won't Fix in 6000.3.X
Votes
1
Found in
2022.3.64f1
6000.0.52f1
6000.1.9f1
6000.2.0b8
6000.3.0a1
Issue ID
UUM-110449
Regression
No
Rich Text Tag "<alpha>" does not work when used with Style Sheet property "text-shadow"
How to reproduce:
1. Extract and open the attached “IN-104897.zip“ project
2. Open Assets → Scenes → SampleScene
3. Enter Play mode
4. Observe the text in the top left of the Game View
Expected Result: “typed” text is fully visible, “typing” text is half transparent, and “to be typed” text is invisible
Actual Result: “typedtypingtobetyped” is fully visible and unaffected by <alpha> Rich Text Tag
Reproducible with: 2022.1.0a7, 2022.3.64f1, 6000.0.52f1, 6000.1.9f1, 6000.2.0b8, 6000.3.0a1
Not reproducible with: 2022.1.0a6
Reproducible on: MacOS 15.5 Silicon
Not reproducible on: Not tested in other environments
Note: Removing the “text-shadow” property from “mystyle.uss” fixes the issue
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:
After further investigation and prototyping, we determined it is not practical to fix this issue without causing major regressions and/or regressing performance. Given the minor nature of the bug and the available workarounds, I'll close this as Won't Fix.
Resolution Note (6000.3.X):
After further investigation and prototyping, we determined it is not practical to fix this issue without causing major regressions and/or regressing performance. Given the minor nature of the bug and the available workarounds, I'll close this as Won't Fix.