We normally ask for confirmation before asking the operating system to
find an application to handle a scheme that the browser does not support.
It did not ask before doing so for the Usenet-related schemes news: snews:
and nntp:. Since most operating systems in 2024 don't have a trusted
newsreader installed by default, an unscrupulous program that the user
downloaded could register itself as a handler.
The website that served the application download could then launch that
application at will. Of course, all bets are off if a user runs such a
program to begin with, but in some situations (looking at you, MacOS!)
just downloading/unpacking could already result in registration as a
protocol handler without the user actually executing anything.
This is a solution for some users having issues with multiple MP prompts due to
either a race or asynchronously-triggered features that each need password
database access (e.g. website login + sync)
Based on Interlink's similar solution by Matt A. Tobin
This adds 'browser.tabs.insertAllAfterCurrent' as a preference which
makes all new tabs opened to be next to the currently active tab, instead
of at the end - regardless if the tab is considered "related" to the active
tab. This (naturally and logically) overrides 'insertRelatedAfterCurrent'
Resolves#1782
It can be assumed that people who launch the browser will do so with
network access, restoring tabs to live locations rather than
previously-visited static pages.
Defaulting this to soft refresh will prevent unnecessarily stale pages
from being displayed when restoring tabs, with minimal bandwidth used.
Note, this does not affect browser restart sessionstore behavior, which
will always re-display previously cached pages "as if nothing happened",
which is what we want.
Favor fallback content in that case (if present). Fallback is always
considered "good" in this case so may end up doing nothing which is what
we'd want for corner cases that hammer this routine with no content.
Also removes the redundant branding version of app.update.url in Pale Moon that was missed when many prefs were merged back into application preferences
Since AMO has removed all "legacy" extensions, they do not offer anything compatible with us any longer.
We send the native UA to them from now on to always have it respond with "Only with Firefox".
