Dominik Röttsches

We have a change where we do this in the font-func override that we have in Chromium: https://chromium-review.googlesource.com/c/chromium/src/+/4581187/8/third_party/blink/renderer/platform/fonts/shaping/harfbuzz_face.cc - we were just thinking as this seems to be common behavior,...

> the current surface is always clear. Do you mean by that that there are no pixels drawn at the start of every paint call, or only at the root...

My current thinking is, perhaps this could be simplified if we would want to introduce a backwards compat break, and introduce a `PaintCompositeWithOnlyOneLayer` that saves a layer creation and always...

> which suggests that each layer should be drawn in its own group then composited using SRC_OVER. But I think with SRC_OVER the results will always be the same, hence...

> The last sentence needs to be removed to match what we are discussing here. I agree the sentence is a bit misleading. It would be clearer and cause less...

I think the change of the radius depending on the color line would need to be explicitly explained or specified, as otherwise that is suprising and not clear from the...

> Given that odd behaviour, it might make more sense to use the absolute value of radii for circ0 and circ1, but not for the projected circles. I agree with...

Up to date FF nightly and Chrome Canary now have the same behavior, I checked this morning.

If the implied suggestion in the [previous comment](https://github.com/googlefonts/colr-gradients-spec/issues/367#issuecomment-1241053905) is to restrict to [0,1] for color stops, or restrict to >= 0 for radii, I don't think that will work without...

@nedley thanks for commenting and looking into this issue. I agree the geometry impact is suboptimal, however, we've from various angles hit the barrier of then having to change fundamentally...