(In reply to linuxusernonadmin from comment #0) Is WebRender now enabled by default for you in https://nightly.mozilla.org? I assume "No qualified hardware" might have been fixed by bug 1794722. R600 is only blocked below Mesa 17.3: https://searchfox.org/mozilla-central/rev/9423bbd90c59ef7739c8453c265d04d8cf07ce73/widget/gtk/GfxInfo.cpp#754 (In reply to Andrew Osmond [:aosmond] (he/him) from comment #23) > The user doesn't get HW-WR because of bug 1673939. I'm not sure if newer drivers have fixed the issue, there seems to have been some related changes mentioned in the upstream issue: > https://gitlab.freedesktop.org/mesa/mesa/-/issues/3720 * bug 1679681 (small random boxes) was an R600 bug and has been fixed: (Kestrel from bug 1679681 comment #12) > The artifacts no longer appear anywhere in the browser, PDFs or WebGL after Bug 1694909. * Both have the same regressing bug: bug 1673939 (which added the blocklist entry) looks rather like bug 1726431 which has been a general WR bug I could reproduce on Intel back then. Is https://gitlab.freedesktop.org/mesa/mesa/-/issues/3720 really a driver bug?
Bug 1798360 Comment 33 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
DriverVendor::MesaR600 is blocked below Mesa 17.3: https://searchfox.org/mozilla-central/rev/9423bbd90c59ef7739c8453c265d04d8cf07ce73/widget/gtk/GfxInfo.cpp#754 DeviceFamily::AmdR600 is blocked for all drivers: https://searchfox.org/mozilla-central/rev/738b761bb2847f609f9cacc550680071cdc53637/widget/gtk/GfxInfo.cpp#778 (In reply to Andrew Osmond [:aosmond] (he/him) from comment #23) > The user doesn't get HW-WR because of bug 1673939. I'm not sure if newer drivers have fixed the issue, there seems to have been some related changes mentioned in the upstream issue: > https://gitlab.freedesktop.org/mesa/mesa/-/issues/3720 * bug 1679681 (small random boxes) was an R600 bug and has been fixed: (Kestrel from bug 1679681 comment #12) > The artifacts no longer appear anywhere in the browser, PDFs or WebGL after Bug 1694909. * Both have the same regressing bug: bug 1673939 (which added the blocklist entry) looks rather like bug 1726431 which has been a general WR bug I could reproduce on Intel back then. Is https://gitlab.freedesktop.org/mesa/mesa/-/issues/3720 really a driver bug?
DriverVendor::MesaR600 is blocked below Mesa 17.3: https://searchfox.org/mozilla-central/rev/9423bbd90c59ef7739c8453c265d04d8cf07ce73/widget/gtk/GfxInfo.cpp#754 DeviceFamily::AmdR600 is blocked for all drivers: https://searchfox.org/mozilla-central/rev/738b761bb2847f609f9cacc550680071cdc53637/widget/gtk/GfxInfo.cpp#778 (In reply to Andrew Osmond [:aosmond] (he/him) from comment #23) > The user doesn't get HW-WR because of bug 1673939. I'm not sure if newer drivers have fixed the issue, there seems to have been some related changes mentioned in the upstream issue: > https://gitlab.freedesktop.org/mesa/mesa/-/issues/3720 * bug 1679681 (small random boxes) was an R600 bug and has been fixed: (Kestrel from bug 1679681 comment #12) > The artifacts no longer appear anywhere in the browser, PDFs or WebGL after Bug 1694909. * To me it looks like the blocklist entry can be removed because bug 1726431==bug 1673939 (caused by bug 1545006) is a bug that affects Intel as well. Is https://gitlab.freedesktop.org/mesa/mesa/-/issues/3720 really a driver bug?