Transform scale and filter blur on image shows seams
Categories
(Core :: Graphics, defect, P3)
Tracking
()
People
(Reporter: reg4real, Unassigned)
References
(Regression, )
Details
(Keywords: regression, reproducible)
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:66.0) Gecko/20100101 Firefox/66.0
Steps to reproduce:
Within an onscroll callback function the style properties filter and transform, of an img element are updated in a requestAnimationFrame callback. There are white seams shown during the scaling/blurring present. This was not previously the case as the effect was in production for quite some time.
The seams were noticed first on Firefox 66.0.5 desktop on Windows 10 64Bit. he seams are NOT visible on mobile Firefox 66.0.5 on Android 9.
Codepen example:
https://codepen.io/dbkup/full/WBdOLz
Actual results:
The image has a grid of seams shown during the blurring/scaling effect when scrolling.
Expected results:
No seams should have been shown during blurring/scaling.
Comment 1•6 years ago
|
||
dbkup, Could you please attach a results of about:support?
I was checking the problem on my home desktop with a dedicated graphics card and could not reproduce it. Again tested the same test case on another laptop with a dedicated graphics card also could not reproduce the error. Perhaps this is a related to the integrated graphics card on the laptop I originally tested on.
Comment 4•6 years ago
|
||
I can reproduce the issue on Nightly69.0a1 Windows10 if HWA is disabled.
Comment 5•6 years ago
|
||
Regression window:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=7ea290696af200867042c95b1dfbe7b44ce931fa&tochange=d2a4720d1c334b64d88a51678758c27ba8f03c89
Triggered by : Bug 1454978
Updated•6 years ago
|
Comment 6•6 years ago
|
||
I can reproduce this issue as well. I had to set the following prefs.
layers.acceleration.disabled=true
gfx.webrender.enabled=false
gfx.direct2d.disabled=false
The 'gfx.direct2d.disabled' pref forces us to use skia which enables P-OMTP. This matches the regression range given. Oddly enough, I also have to disable accelerated layers to see the issue as well.
I'm not sure what's going yet.
Updated•3 years ago
|
Hi Gregory,
I can't reproduce the issue anymore with using the preference mentioned in comment#6 on multiple machines.
Seems like the issue is now resolved.
Comment 9•2 years ago
|
||
Thanks for confirming on multiple machines!
Description
•