Unity Issue Tracker - Rich Text Tag "<alpha>" does not work when used with Style Sheet property "text-shadow"

Won't Fix

6.3.X

6.2.X

6.1.X

6.0.X

2022.3.X

This is not a regression. The bisection found something unrelated. We never supported this capability before. That said, we'll still try to fix it properly, but only in the latest version. No backports are planned.

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

Rich Text Tag "<alpha>" does not work when used with Style Sheet property "text-shadow"

Unity: UI Toolkit Graphics

Won't Fix

Prioritise and Follow this issue

Have a workaround or additional info about this issue?

Rich Text Tag "<alpha>" does not work when used with Style Sheet property "text-shadow"

Unity: UI Toolkit Graphics

Statuses

Won't Fix

Resolution Notes

6.2.XWon't FixThis is not a regression. The bisection found something unrelated. We never supported this capability before. That said, we'll still try to fix it properly, but only in the latest version. No backports are planned.

6.1.XWon't FixThis is not a regression. The bisection found something unrelated. We never supported this capability before. That said, we'll still try to fix it properly, but only in the latest version. No backports are planned.

6.0.XWon't FixThis is not a regression. The bisection found something unrelated. We never supported this capability before. That said, we'll still try to fix it properly, but only in the latest version. No backports are planned.

2022.3.XWon't FixThis is not a regression. The bisection found something unrelated. We never supported this capability before. That said, we'll still try to fix it properly, but only in the latest version. No backports are planned.

Description

Prioritise and Follow this issue

Have a workaround or additional info about this issue?