Without containers, I’d probably bite the bullet and start using some chrome fork that doesn’t show me useless ads.
Without containers, I’d probably bite the bullet and start using some chrome fork that doesn’t show me useless ads.
So Chrome and FF are in the same boat: "UX" "designer" taking non-sensical decisions for the whimsical greater good.
I presume grandparent has either hit a bug, has some unusual/untested about:config combination, or, most likely, an addon that broken.
Here is the relevant about:config settings I have these changed for the URL bar:
browser.urlbar.suggest.searches false
browser.urlbar.searchSuggestionsChoice false
browser.urlbar.showSearchSuggestionsFirst false
Also for your urlbar you want to change it so it always shows the scheme and every part of the URL. browser.urlbar.trimURLs false
Stop Firefox trying to help with incomplete urls and loading the wrong site: browser.fixup.alternate.enabled false
Setting the above about:config entries should stop URLS you type being sent to a search engine and also stop some other surprises in the URL bar.* Tips and News from Mozilla and Firefox * Recommendations while surfing * Recommend addons while surfing
I'm not entirely sure what you saw that made you angry, but I'm pretty sure you can switch them off rather than abandon the entire browser.
That goes for a lot of Firefox hate, I find: quite often people are ranting online about some new or removed feature, which they can dis- or enable easily in the settings. Or -a tad harder- in about:config. Or even a tad harder, with an addon.
That makes me think those ranters don't really want their problem solved, but just want to vent some anger about X changing something that they are emotionally not ready to see changed.
Obviously the actual page rendering and JavaScript executing would be Safari. But 99% of the time when I hear people advocating for browser X over browser Y it is not because X has better rendering or a better JS engine. It is because of higher level things, like containers (Firefox over Chrome) or better profile handling (Chrome over Firefox) or better spell checking (everything over Firefox).
Does having to build on top of Safari on iOS also constrain those higher level things?
Yes!
> containers (Firefox over Chrome)
No, they can't install add-ons (https://support.mozilla.org/en-US/kb/add-ons-firefox-ios). Even if they could built this into the browser, they can't (see how the profiles are handled).
> better profile handling (Chrome over Firefox)
No, Chrome does not support this feature on iOS (https://support.google.com/chrome/answer/2364824?hl=en&co=GE...). iOS' WebKit limits this to only one permanent profile and one ephemeral profile. You can technically have multiple profiles in the iPad - that is, if you're a school, and that's really more of a OS-wide user account thing. (G did a hack over this by rewriting that profile when switching profiles - but it's not truly a multitask thing, and violates Apple Developer Guidelines).
> better spell checking (everything over Firefox)
No, and for more sensible reasons. Users do expect consistent spell checking because they use the keyboard to do that. Regardless, if you want to implement spell checking in-browser, that's impossible. If you want to do it outside of Safari, go ahead - it's just not integrated to those Apple things (more of a dedicated Grammarly interface rather than desktop spell checking).
Was switched off.
All the others (according to the linked information) are irrelevant for intrusive pop-up ads. By all means, please explain to me which of those settings do something different from what they are supposed to do, or tell me about an about:config settings that tells Firefox to never show me pop-up ads.
What made me angry: https://i.imgur.com/s9hC23U.png which blocks the interaction with any part of Firefox until I click "Not Now"