Google maps has never worked well for me on FF. The "old"/basic interface for Gmail works fine, but the new one was noticeably slower.
It doesn't seem exclusive to Google, however. Many PWA sites (including bank websites!) have, from time to time, inexplicably failed to load certain elements on FF, while loading them without fail on GC.
I don't really fault FF for this, but it is what it is.
The good news is it seems to be getting better. Every month or so, I try these trouble sites in FF, and every month I have fewer "trouble sites".
Using chrome once it loads with everything else shutdown seems fast.
Firefox is overall faster because of those issues. But firefox will use too much memory and kill itself in time. But has gotten better at killing itself without killing everything else.
https://megous.com/dl/tmp/33d9622c7e53e3bc.png
https://megous.com/dl/tmp/8b3e50856a913236.png
I still use it as a primary browser even for development, but with issues like this being unresolved for almost a year, it's really hard.
Ever since the rewrite in React, it's really bad. First a massive performance regression (which improved over time, thankfully), but it still has major issues like the above.
For reasons I cannot understand, firefox on my 8GB RAM windows surface eats up huge amounts of memory. But it uses very little RAM with the same profile on my much more powerful desktop.
It’s the only thing that keeps pulling me back to Chrome, as well as many others I’ve seen discuss it in forums over the years.
There’s no Firefox extension to add it and as Firefox users don’t have it they don’t miss it.
Really, sort this, you’ll quietly unlock a bunch more switches.
You can add things like YouTube etc as well so long as they have "OpenSearch" metadata. (Presumably what Chrome is using for "tab to search"?) [1]
[1] https://support.mozilla.org/en-US/kb/add-or-remove-search-en...
What you're describing is a bookmark substitution search feature that's independent of OpenSearch, and Mozilla calls the feature keyword searches[2].