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.
"sort of" and "not completely aligned" are just right: IMO, the mark navigation feature is just clunky/broken compared to the alternatives.
You don't want to iterate between the marks in the current buffer in a loop, or somehow keep track of whether each of the last three navigations changed the buffer or not (which would affect which one of the mark rings you'll have to use to go back or forward).
> I'd like to have an analogue to jump back with my C-x stuff like I do with M-. and M-, - any emacs people have suggestions on how to do that?
If you use Xref UI for "Find References/Implementations/Type", M-, should work in those cases too.
There is a more general question: how to "jump forward" again, without re-invoking the previous navigation command with the exact arguments. IDEA, already mentioned in comments, has key bindings for that.
There are several third-party packages which attempt to solve it as well. I'm using this one:
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.