You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In discussion with Google, it was found that the spec for sweep gradients was potentially confusing because of ways in which it diverged from the way sweep gradients are expressed in CSS and also in Skia. This was due to misunderstanding of the (unfortunately vague) Skia spec when COLR v1 formats were being defined. To minimize confusion, and since implementations for COLR v1 are still very early in their development, Microsoft and Google agreed to make a breaking change in the semantics for representation of sweep gradients.
Note: The formats for representing sweep gradients (PaintSweepGradient, PaintVarSweepGradient) do not need to change. The only change is to how member values are interpreted.
In discussion with Google, it was found that the spec for sweep gradients was potentially confusing because of ways in which it diverged from the way sweep gradients are expressed in CSS and also in Skia. This was due to misunderstanding of the (unfortunately vague) Skia spec when COLR v1 formats were being defined. To minimize confusion, and since implementations for COLR v1 are still very early in their development, Microsoft and Google agreed to make a breaking change in the semantics for representation of sweep gradients.
Note: The formats for representing sweep gradients (PaintSweepGradient, PaintVarSweepGradient) do not need to change. The only change is to how member values are interpreted.
The draft changes from googlefonts/colr-gradients-spec#362 need to be incorporated into OT 1.9.1.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: