Dominik Röttsches

For code-archeology background, original discussions when adding `PaintSweepGradient` in #217 and #253.

For defining where do we start and end drawing from, i.e. what is painted, and what is discarded as overlap, we need to also take into account the definitions of...

To summarize, we have at least the following issues: 1) The spec text is too strictly tied to the [0,1] interval. Spec text: "but only color values for the range...

For reference, updated test cases in https://github.com/googlefonts/color-fonts/pull/99/files - with example renderings in https://github.com/googlefonts/color-fonts/pull/99#issuecomment-1117357643 (to be used with caution, work-in-progress).

Summary from virtual f2f (please correct me if anything from the meeting is inaccurately reflected): - We meet again in roughly a week, after reading more on CSS spec definition,...

Draft in https://github.com/googlefonts/colr-gradients-spec/pull/362/files

Updated issue description with those.

Moving `ic-height` tests in that case to guarded by `CSS.supports` works for me, thanks for the suggestion. Our shipping decision for the `ic-height` value depends on if and what we...

Following https://github.com/w3c/csswg-drafts/issues/6384 I can foresee two possible outcomes: 1) We do base the adjustments on unreliable heuristics, in which tests we can only WPT test situations in which the relevant...

In CSS WG resolutions https://github.com/w3c/csswg-drafts/issues/10292 and https://github.com/w3c/csswg-drafts/issues/6384 it was decided to keep using heuristics in the case where the font lacks a metric, which means we arrive at > 1....