4 ms·
> The only think keeping me on Fx is a sense of ethics So do I. At least I still use Firefox as my secondary browser. My own main recriminations: - The downl
by idoubtit 7y ago
> The only think keeping me on Fx is a sense of ethics
So do I. At least I still use Firefox as my secondary browser.
My own main recriminations:
- The download manager is awful. I sometimes download several times a file because I didn't see it started. And I could describe half a dozen bugs with it. For example, under some conditions, the size of a download is replaced by the sum of the previously downloaded files (4GB/4.1GB instead of 0/100MB + 4GB old files).
- about:config is broken. When I open the settings for power users in Chromium, each option has a short description. With Firefox, the documentation is not linked to the setting, it's in a wiki or blog posts.
- I need an extension to confirm on quit. I sometimes press Ctrl-q when I intended Ctrl-w. The config browser.showQuitWarning and browser.warnOnQuit have no effect. I had to read FF's source code to understand it was intentional: the code had evolved (IMHO, in a bad way), the doc had not.
- Local extensions are removed when FF stops. I heard that this is not the case with "developer FF", but I don't want to drop the OS packaging of ESR FF. And that feature is already in Chromium based browsers. I don't even know what devFF is, though I've heard it's based on a FF beta branch.
These are mostly not problems for the main target of FF. My parents main problem were that an update once replaced their custom starting page (tailor made) with the default one (recently visited sites + ads). They also had a few UI hard times, but these were either fixed by FF (adding a link to the starting page was impossible without reading a doc) or my parents got used to them.
- Vinnl 7y ago> - I need an extension to confirm on quit. I sometimes press Ctrl-q when I intended Ctrl-w. The config browser.showQuitWarning and browser.warnOnQuit have no effect. I had to read FF's source code to understand it was intentional: the code had evolved (IMHO, in a bad way), the doc had not. That's odd; I'm running stable Firefox, and the second option in my Preferences is "Warn you when quitting the browser" - and it does what it says, for me, without an extension.