Google docs paints all black (with bug 1771374)
Categories
(Core :: Graphics: CanvasWebGL, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr91 | --- | unaffected |
firefox-esr102 | --- | unaffected |
firefox102 | --- | unaffected |
firefox103 | --- | unaffected |
firefox104 | + | verified |
People
(Reporter: RyanVM, Assigned: jgilbert)
References
(Regression)
Details
(Keywords: regression)
Attachments
(3 files)
Annoyingly, this didn't reproduce for me in mozregression unless I used my regular profile for it, but I was eventually able to bisect this to bug 1771374.
Updated•2 years ago
|
Reporter | ||
Comment 1•2 years ago
|
||
Reporter | ||
Comment 2•2 years ago
|
||
Confirmed via local backout that bug 1771374 was the regressor.
Comment 3•2 years ago
|
||
about:support from another affected machine.
Reporter | ||
Comment 4•2 years ago
|
||
Looks like we're both on nVidia with the latest drivers.
Comment 5•2 years ago
|
||
Maybe related: My google docs seems to be one change behind the current state. When I type, the page displays the N-1 change in the document (I type "dog" and see "do"). Clicking outside the document sometimes reveals the latest change.
I'm on Fedora with an nvidia card and the nouveau drivers.
Reporter | ||
Comment 6•2 years ago
|
||
That's bug 1779410 most likely.
Reporter | ||
Comment 7•2 years ago
|
||
FWIW, the behavior reproduces already with https://hg.mozilla.org/mozilla-central/rev/ef52a6c462b6.
Assignee | ||
Comment 8•2 years ago
•
|
||
Workaround: gfx.webrender.dcomp-video-overlay-win:false and restart browser
Testcase: https://jsfiddle.net/gspfr4x2/2/
It looks like alpha!=1.0 pixels from canvas (2d or webgl) with dcomp broke.
Assignee | ||
Updated•2 years ago
|
Comment 10•2 years ago
|
||
I can confirm that the workaround works, thanks.
Assignee | ||
Comment 12•2 years ago
|
||
This was fixed by reverting bug 1771374.
Updated•2 years ago
|
Updated•2 years ago
|
Comment 13•2 years ago
|
||
Reproduced the dark background in in Google doc and the dark areas from the demopage from comment 8, verified that using latest Firefox 104.0b5 on Windows 10 (Nvidia GTX1070 TI) the issue is no longer reproducible.
Description
•