Ned Holbrook
Ned Holbrook
I am uncomfortable with any solution where the geometry of the gradient is influenced by its color stops or vice versa. COLRv1 implementations should clip or ideally not draw any...
I believe COLRv1 radial gradients with r1 > r0 can be expressed as a CSS radial gradient by extrapolating to the starting point, at least geometrically. But my point (of...
> From the [drawRadialGradient](https://developer.apple.com/documentation/coregraphics/cgcontext/1455923-drawradialgradient) documentation I find that the CoreGraphics API also expects 0 and 1 normalized color stops. Core Graphics doesn't support repeated gradients at all, so I wouldn't...
Let me put it differently: if it is a choice between compromising the geometry or the color line, we would rather compromise the color line.
One thing to note is that all vendors depict oyster on the half shell, which is clearly food.
I guess I still don’t understand how the Github PR workflow applies.
This is still on my list, yes.
Deprecated or not, the behavior when combined with `ConditionSet` should be defined.
> The behavior is well-defined. The `ConditionSet` is AND of conditions, and will remain so. I’m probably missing something, then: how is `ConditionAnd` different from `ConditionSet`?
I guess the mention of deprecation threw me off, then. So this is proposing additional formats for use within a `ConditionSet` of a `FeatureVariationRecord`?