The top part of the images on the left and right sides are glitching while scrolling on Connect-Homes webpage
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox106 | --- | wontfix |
firefox107 | --- | wontfix |
firefox108 | --- | fixed |
People
(Reporter: csasca, Assigned: gw)
References
(Regression)
Details
(Keywords: regression)
Found in
- Firefox 107.0b2
Affected versions
- Firefox 107.0b2
- Firefox 108.0a1
Tested platforms
- Affected platforms: Windows 11, Ubuntu 22.04, macOS 13
- Unaffected platforms:
Steps to reproduce
- Launch Firefox
- Access Connect-Homes page
- Scroll down the page and look for pictures
Expected result
- The pictures are rendered correctly
Actual result
- The top part of the images on the left and right sides are glitching while scrolling
Regression range
- Will see for a regression
Additional notes
- The issue can be seen in the following attachment
Reporter | ||
Updated•2 years ago
|
Comment 1•2 years ago
•
|
||
I can reproduce the issue on Windows10, see screencast https://youtu.be/E-wd2glcWg8
Regression window on Windows10:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=06e5cdccdd8c2ee8b9465a6a93b5c7111aed38a7&tochange=68ec3db74342eb63fc142f2d28675ad698ba0062
Comment 2•2 years ago
|
||
:emilio, since you are the author of the regressor, bug 1661147, could you take a look?
For more information, please visit auto_nag documentation.
Comment 3•2 years ago
|
||
Seems like a clip not getting applied consistently, but somehow only while async-scrolling? I think this probably is a WebRender bug given that... Glen maybe you can take a look? I'm a bit swamped right now but if you can't please redirect the ni? back and I can take a look. Thanks!
Updated•2 years ago
|
Assignee | ||
Comment 4•2 years ago
|
||
Unlikely I'll have time to look at it any time soon, but I can put it on my list for now, anyway. Emilio, if / when you get a chance to look at it, feel free to reassign.
Comment 5•2 years ago
|
||
I believe bug 1799216 fixes this as well.
Updated•2 years ago
|
Updated•2 years ago
|
Description
•