While it doesn't seem like this SpiderMonkey feature will go away soon, replacing it makes tooling easier and is suitable here because the unconditional catch js already used.
MozReview-Commit-ID: 3G3LxrW24HF
alert_emails tell us who is interested in a particular histogram. If there's
no one interested, then the histogram shouldn't exist.
MozReview-Commit-ID: 90Yqof3dbsd
bug_numbers is now mandatory, because we really want to have some explanation
about where the probe came from.
We have a lot of non-bug-numbered probes (including non-Histograms.json-
resident probes like the use counters) that are being "grandfathered in" via
a whitelist in whitelists.json.
MozReview-Commit-ID: 62dN96sEOUf
These tests verify that the InstallTrigger API works as expected and that the
old style of signing add-ons is verified correctly. Other applications still
care about this so we don't want to regress it.
This switches most tests that previously expected an unsigned add-on to use an
AMO signed add-on. In apps that care that will allow it to install, in apps that
don't it will be effectively the same as unsigned (untrusted root).
Other tests that actually verify that the old style of signatures are either
seen or not seen are marked as skipped when AMO-signing is required. In some
cases that meant doubling up a few tests to make sure we have coverage.
MozReview-Commit-ID: 6V4U1U1HTqx
While investigating bug 1248489, we discovered that some code paths in
AsyncShutdown could possibly be sensitive to exceptions being thrown
in unexpected places. This patch attempts to make AsyncShutdown more
robust to such exceptions.
MozReview-Commit-ID: 5ImL9YNVgQr
Implement browser.i18n.getAcceptLanguages() including tests
Rebase against fx-team, resolving some conflicts
Fix eslint errors/warnings
MozReview-Commit-ID: 52sZWsIHbl4
This aims at speeding up DELETE FROM moz_places like queries.
The primary reason of slowness is the FOR EACH ROW trigger that takes care of updating the moz_hosts table when places are removed.
Unfortunately Sqlite doesn't support FOR EACH STATEMENT triggers, that means the trigger will hit multiple times for pages in the same host.
The patch introduces an additional temp table to accumulate hosts during a delete, then a trigger takes care of updating moz_hosts only once per touched host, rather than once per removed place.
MozReview-Commit-ID: BlJRLQZoC07
Add new alarm coverage:
* Alarms with a |when| property.
* Observer callbacks for canceled alarms being ignored.
* The one-argument forms of |alarms.create| and |alarms.clear|.
* |alarms.clear| ignoring alarms without matching names.
MozReview-Commit-ID: 9fmrX1kaSpd
