Overlapping drop shadows causing strange artifacts in Firefox only
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr91 | --- | unaffected |
| firefox-esr102 | --- | affected |
| firefox101 | --- | wontfix |
| firefox102 | --- | wontfix |
| firefox103 | --- | wontfix |
| firefox104 | --- | wontfix |
| firefox105 | --- | fix-optional |
People
(Reporter: conor4arms, Assigned: gw)
References
(Blocks 3 open bugs, Regression)
Details
(Keywords: css3, parity-chrome, regression)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:100.0) Gecko/20100101 Firefox/100.0
Steps to reproduce:
Having multiple elements that cast drop-shadows overlap causes strange artifacts. Specifically when both these elements have their geometries defined by 3D transformations of child objects. Live example at https://conorpo.github.io/ (my portfolio that i am working on.
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:100.0) Gecko/20100101 Firefox/100.0
Actual results:
https://gyazo.com/55a0814dc10ec9f8d45216c768cfd16d
Overlapping drop shadows caused artifacts
Expected results:
Overlapping drop shadows should overlay properly
| Reporter | ||
Comment 1•4 years ago
|
||
These artifacts do not appear in chrome.
Updated•4 years ago
|
Comment 2•4 years ago
|
||
Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=c6f1243c3ba45a4ad3cfd1cacdbf12ad377b4a81&tochange=fc2b3d6448bcc3575fffb1abc923e7e703aeef54
Comment 3•4 years ago
|
||
:gw, since you are the author of the regressor, bug 1749380, could you take a look?
For more information, please visit auto_nag documentation.
Updated•4 years ago
|
Updated•4 years ago
|
| Assignee | ||
Updated•4 years ago
|
Updated•4 years ago
|
Comment 4•4 years ago
|
||
The severity field is not set for this bug.
:gw, could you have a look please?
For more information, please visit auto_nag documentation.
| Assignee | ||
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Comment 5•2 months ago
|
||
This looks to be correct now, from a quick look at the existing linked site?
Comment 6•2 months ago
|
||
Redirect a needinfo that is pending on an inactive user to the triage owner.
:gw, since the bug has recent activity, could you please find another way to get the information or close the bug as INCOMPLETE if it is not actionable?
For more information, please visit BugBot documentation.
| Reporter | ||
Comment 7•2 months ago
|
||
Hello! I git switched to my site as it was when I made this post and the issue is completely gone. I can send code or create minimal example if needed.
| Assignee | ||
Updated•2 months ago
|
Description
•