The usual explanation by Firefox team is that the drivers are not uniformly compliant and/or working well. There had been progress, though.
For your specific system, you can open about:support and search the page for the word "Blocklisted" - that section of the page includes failure codes that can be then passed to web search (or interpreted by name).
I don't know all the details of what works well or not, but the Chrome team logically should have more manpower to implement workarounds for driver problems, and Vivaldi reuses the engine.
Speaking of the other applications though, most of them don't have to use the dma-buf subsystem, to embed hardware rendered content inside a "regular" application. That imposes a certain limitation on the driver capabilities.
For your specific system, you can open about:support and search the page for the word "Blocklisted" - that section of the page includes failure codes that can be then passed to web search (or interpreted by name).
I don't know all the details of what works well or not, but the Chrome team logically should have more manpower to implement workarounds for driver problems, and Vivaldi reuses the engine.
Speaking of the other applications though, most of them don't have to use the dma-buf subsystem, to embed hardware rendered content inside a "regular" application. That imposes a certain limitation on the driver capabilities.