Bug 627771 Comment 42 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

(In reply to Glenn Watson [:gw] from comment #40)
> This would be a potentially high impact webcompat bug to solve

We don't really have a good way to quantify this. Our system is supposed to have one site report bug per instance, and we don't have this here. In most cases, we'd triage them as `minor-visual`, which would have a very low priority. We also can't really use telemetry data or anything, because a lot of gradients on websites are on small things like a button, where you wouldn't notice it.

But of course, linear gradients are also used in large backgrounds (Tailwind-based sites are a good example), and you absolutely see the difference there. Nothing is *broken* per-se, but it looks super bad. It also heavily impacts "graphics" web apps like Photoshop for Web or Figma, where it's still "just visual", but the impact is high here. If we had individual site reports for all of these, this bug would probably be a clear P1.

I'll set webcompat-priority P1 for now, because it makes Firefox looks *really* bad. We should at least spend some time checking if we can fix this with a reasonable amount of time.
(In reply to Glenn Watson [:gw] from comment #40)
> This would be a potentially high impact webcompat bug to solve

We don't really have a good way to quantify this. Our system is supposed to have one site report bug per instance, and we don't have this here. In most cases, we'd triage them as `minor-visual`, which would have a very low priority. We also can't really use telemetry data or anything, because a lot of gradients on websites are on small things like a button, where you wouldn't notice it.

But of course, linear gradients are also used in large backgrounds (Tailwind-based sites are a good example), and you absolutely see the difference there. Nothing is *broken* per-se, but it looks super bad. If we had individual site reports for all of these, this bug would probably be a clear P1.

I'll set webcompat-priority P1 for now, because it makes Firefox looks *really* bad. We should at least spend some time checking if we can fix this with a reasonable amount of time.

Back to Bug 627771 Comment 42