Web is getting increasingly integrated in real life so bridges and apps may take the spotlight (just a guess).
If it's not broken why do so many devs refuse to support it because things they code in Chrome don't work in it.
Not that I condone that, but it's what I experience working with dev teams the past few years they all just complain that features are missing from Chrome so it will be too much work to test/support FF.
You'll surely meet a lot of people doing what you mention. I would bet most of them are young enough to not have gone through the so-called "browser wars" [1], at least what they now call the first one, the one that ultimately led to the creation of Firefox.
Their attitude does not mean at all that there's something actually broken in Firefox, just that it is so much easier -and lazier- supporting a single browser's quirks and ignoring the rest. Even if that means discarding standards and compatibility. Specially if it means that, because you will take advantage of those particularities.
This mentality is exactly why Internet Explorer was dominant for so long. Embrace, Extend, Extinguish. There are many differences between 2000s Microsoft and 2020s Google but there are also quite a few similarities, even down to funding their opposition to avoid the appearance of a monopoly.
I was under the impression that most things were stable or that most major browsers implemented things at a similar pace.