>>1021426 (OP)
Except for Firefox? Yes.
Countless independent browser engines (iCab, Arachne, Omniweb, AWeb, NetPositive, Voyager, etc.) died years ago
Opera's engine died in 2013
Internet Explorer/Edge engine died just last year:
https://techcrunch.com/2018/12/06/microsoft-edge-goes-chromium-and-macos/
There is literally nothing else left.
>>1021428
>>1021431
>>1021528
>safari isn't a chrome clone
Safari and Chrome are the same largely indistinguishable source tree, derived from Konqueror, with the vast majority of code constantly shared between Google and Apple.
>Firefox have been chasing chrome for a while.
True but that's all fluff at the browser rather than engine level, and can trivially be fixed by forks. In fact, by far the greatest problem with Mozilla right now is the one feature Apple/Google have that Mozilla hasn't since 2011: The ability to embed Firefox's engine inside other programs, completely separate from Firefox. Although, Palemoon has the reimplementation of this embedding functionality as a low-priority goal.
>At this point, the only thing that differentiates firefox and chrome is muh web freedom
No, it's the fact that Firefox's engine (and Servo's, for the future) is a completely separate codebase, implementing the HTML/CSS/JS specification in a completely independent fashion from Chrome+clones.
Imagine for a moment what happens if Mozilla throws in the towel, and there is only one single implementation of WHATWG's "standard"? Remember there hasn't even been a testbed reference browser/editor like Arena/Amaya for years. It would be completely impossible to specify standard features separate from Google/Apple's source tree, likewise rendering it impossible for Google/Apple to distinguish between implementation bugs and poorly specified/documented features.
If Firefox dies, the web is permafucked.