(In reply to Hugo Osvaldo Barrera from comment #12)
As somebody who's NOT using Mutter, it's kinda annoying that Firefox makes a willing choice to have a feature broken so that compatibility with a broken compositor can stay in place
First of all you are of course right that this should not stay that way. However, please note that it's often not directly clear what's a compositor bug, what's a GTK bug etc. So at the moment, Fedora and Gnome developers are doing by far the most work on the Wayland port and thus occasionally it can happen that a workaround is introduced without the underlying issue being properly debugged. Had it been clear that there's a Mutter bug making the workaround necessary, Martin would have opened in issue about it back then, just how he does quite often when he's sure about the course of a bug. When the problem is understood, things get fixed. The reason why it makes sense here to wait a bit more (IMHO) is that Martin is at the same time the main FF Wayland dev and the Fedora FF maintainer. So any time he could now spend to get the fix out a little bit faster, while carrying an extra patch for Fedora, he can also work on other things and let Mutter devs role out the fix.
Also, please note that the Wayland backend is still experimental - as soon as things are declared stable things look a bit different.
Essentially, Firefox gives a better experience on faulty compositors, at the cost of a worse experience on non-faulty ones. It's also not pushing them to fix the underlying issue either.
See above. Of course we're striving for standard conformity - more helping hands make it easier to archive that :)