Rendering artifacts on a Codepen demo on pinch-zoom (split off from bug 1892018)
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox126 | --- | unaffected |
firefox127 | --- | unaffected |
firefox128 | --- | verified |
firefox129 | --- | verified |
People
(Reporter: mayankleoboy1, Assigned: nical)
References
(Regression, )
Details
(Keywords: regression)
Attachments
(10 files)
1.26 MB,
video/mp4
|
Details | |
45.00 KB,
text/plain
|
Details | |
33.77 KB,
image/png
|
Details | |
2.06 MB,
video/mp4
|
Details | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review |
Go to https://codepen.io/thomasrye/pen/VaRoYv
Pinch-zoom
AR: The bottom corners get some sort of renderign artifacts.
ER: Not so
Bisection:
Bug 1892398 - Supply local space coords to compositing quads when drawing patterns. r=gw
The quad primitive info takes a scale+offset transform which is applied to the coordinate space of the pattern. This allows the quad coorinates to be optionally specified in device space while the pattern remains in layout space.
Differential Revision: https://phabricator.services.mozilla.com/D209694
Reporter | ||
Comment 1•9 months ago
|
||
Reporter | ||
Comment 2•9 months ago
|
||
Reporter | ||
Comment 3•9 months ago
|
||
This is the actual regression from the above bisection : Without doing any pinch-zoom, the edges have this squircle thingy and the colors are all wrong.
Reporter | ||
Comment 4•9 months ago
|
||
Comment 5•9 months ago
|
||
Set release status flags based on info from the regressing bug 1892398
:nical, since you are the author of the regressor, bug 1892398, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Reporter | ||
Updated•9 months ago
|
Reporter | ||
Updated•9 months ago
|
Reporter | ||
Updated•9 months ago
|
Reporter | ||
Comment 6•9 months ago
|
||
Partially fixed by:
Bug 1896979 - Handle matrix transforms that simplify into 2d scale + offset. r=gfx-reviewers,gw
Differential Revision: https://phabricator.services.mozilla.com/D210612
Reporter | ||
Updated•9 months ago
|
Reporter | ||
Updated•9 months ago
|
Updated•9 months ago
|
Assignee | ||
Updated•9 months ago
|
Reporter | ||
Comment 7•9 months ago
|
||
Also occurs on https://codepen.io/alvaromontoro/pen/OJwWPOB
Assignee | ||
Comment 8•9 months ago
|
||
Assignee | ||
Comment 9•9 months ago
|
||
There was an undocumented assumption that the raster node is the root spatial node if raster node != surface node which was very confusing because this function can be called in cases the raster node is different. This patch cleans up the local/picture terminology, replaces the use of the root node with the surface's raster node (which are assumed to be equal) since that is more generally correct and asserts the assumption about the root node. There should be no behavior change in the patch (unless the working assumption does not hold true and the added assertion is hit).
Depends on D211830
Assignee | ||
Comment 10•9 months ago
|
||
Depends on D211849
Assignee | ||
Comment 11•9 months ago
|
||
Depends on D211850
Assignee | ||
Comment 12•9 months ago
|
||
Depends on D211851
Assignee | ||
Comment 13•9 months ago
|
||
This is purely a stylistic choice, feel free to reject if you disagree. I have a much easier time reading the math this way. This patch does not change the behavior of the code.
Depends on D211852
Assignee | ||
Updated•9 months ago
|
Comment 14•9 months ago
|
||
Comment 15•9 months ago
|
||
bugherder |
Reporter | ||
Comment 16•9 months ago
|
||
This is fixed for me with the latest nightly https://hg.mozilla.org/mozilla-central/rev/e1da1893a0c56d2752be4e6eb1efa16c58723a55
Comment 18•9 months ago
|
||
Comment 19•9 months ago
|
||
bugherder |
Assignee | ||
Comment 21•9 months ago
|
||
No, let's close it.
Updated•9 months ago
|
Updated•9 months ago
|
Comment 22•9 months ago
|
||
Issue is reproducible on a 2024-05-17 Nightly build on Windows 10.
Verified as fixed on Firefox 128.0b2 and Firefox Nightly 129.0a1 on Windows 10, Ubuntu 22, macOS 14.
Description
•