Open Bug 1889095 Opened 1 year ago Updated 1 month ago

[meta] Hard gradient stops are too hard

Categories

(Core :: Graphics: WebRender, defect)

defect

Tracking

()

People

(Reporter: nical, Unassigned)

References

(Depends on 5 open bugs, Blocks 1 open bug)

Details

(Keywords: meta)

We did our best ensure that hard stops aren't "fuzzy". In other words that the separation between the stop is crisp and we don't blend between the two colors.
Turns out people generally want hard stop to be "fuzzy" (read: anti-aliased) at least when the separation is not an axis aligned line.

Depends on: 1717934
Depends on: 1881665
Depends on: 1708030

Corresponding skia bug: https://issues.chromium.org/issues/40035288
Some of their backend have the same fundamental issue (1 sample per pixel). Looks like ganesh (at some point in time) doesn't/didn't have the problem, IIUC because it renders the gradient in two steps: 1D ramp and then the gradient primitive. Sampling from the ramp with linear interpolation smooths out the hard stops, but it comes with "other downsides" which I suspect are https://issues.chromium.org/issues/40037678.

Depends on: 1860310
Depends on: 1767182
You need to log in before you can comment on or make changes to this bug.