Loading `about:cache` and selecting particular caches via the checkboxes
results in a cryptic error ("Unrecognized storage name 'null' in
about:cache URL") when updating the page. We avoid that by making sure
the storage parameter is in fact empty if it is supposed to be `null`.
Enable av1 decoding with the aom reference library on nightly
build except on Windows and Android where it's not working yet.
This codec is under development and subject to incompatible
changes. We're supporting a specific encoder revision for
testing with website authors to get early feedback.
See media/libaom/README_MOZILLA for the specific codec commit
hash our decoder expects.
MozReview-Commit-ID: JCPiVFg3geC
--HG--
extra : rebase_source : c7b9de67415d885ada64658f8f938b4091b468e3
The current way to configure compare-locales has a lot of
assumptions that make our l10n system really stubborn.
The generic configuration is independent of python, and uses
toml files for configuration. They're still modular, but
there's only one file format.
See http://moz-l10n-config.readthedocs.io/en/latest/fileformat.html
for the specification.
Also fixes a few nits in filter.py, where we compared the
entity key as bool, which is false if we pass in ''.
Explicitly compare as "entity is None" to be precise about
when we're checking files.
MozReview-Commit-ID: 5TmfobaImF4
--HG--
extra : rebase_source : 84e56eb2076e74f79677df9e0368811579c1f173
This involves a few changes:
- Remove the .exe from the makensis binaries. which.which will
auto-add it so Windows will keep working - and with it
present we were finding makensis.exe on Linux and trying to
run it, which isn't going to work
- Doesn't bother checking if nsis is 32bit if we're running on
Linux
- Add the -nocd option to nsis (on Linux) because it takes the
current working directory from the target of a symlink rather
than the symlink itself. See
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704828
MozReview-Commit-ID: CVT8LwS1t8w
--HG--
extra : rebase_source : 2a62327326ba80dfd728048d19f0ff1c90100838
The first time any other code in the parent process uses NSPR (usually via
nsIProcess) to spawn a new process, it spawns a thread to contuously wait for
any child process to exit. This thread winds up reaping our child processes
before we get the chance to wait for them, which leads us to continuously poll
for them to exit.
We don't have a good way to handle this, but checking the error status of
waitpid at least prevents us from failing catastrophically.
MozReview-Commit-ID: 75Z1yUHUmjy
--HG--
extra : rebase_source : db45f781190b6fc84873c32c611134326736a1ba
Updated time, access count and uri can be accessed using the node passed to the method.
There is no need to access the other arguments, which contain the old values of the
quantities changed.
MozReview-Commit-ID: 3WEwAs8gQ0w
--HG--
extra : rebase_source : 4f6f8bb9d9747cb9cfacf0a5ee5ed58dfca41c0d
Update interface and all instances where the method is called
to be called with the old values, since the new values are already
there as a part of the node, and thus redundant.
MozReview-Commit-ID: 5pcfJbg9tej
--HG--
extra : rebase_source : 4053523f466c3b1f77148376e1e93aa4bcb7e417
Redirect the link to about:preferences#privacy-reports
MozReview-Commit-ID: HIq9zpT6Jz9
--HG--
extra : rebase_source : 8393573834367174ef743c09470f74c22e1ccbdd
This adds the RemoteType annotation to a content crash report so that we can
distinguish between content processes that crashed while running remote, local
or extension code. The annotation is passed along the others to Socorro by the
crashreporter and is also whitelisted for inclusion in the crash ping.
MozReview-Commit-ID: 4avo0IWfMGf
--HG--
extra : rebase_source : 8d03f7e166b5762a5ce7cab13c2101302b4f1d2f
In case some legacy third-party things were relying on those files being
under a unix/ directory, revert the part of changeset c94e87a18096 that
renamed global-platform/unix to global-platform/gtk.
--HG--
extra : rebase_source : c0f9e96592822fe2c87e837a27becfde87a76a0c
Since it wasn't possible to have specific manifest entries for !Darwin
!WINNT !Android, a few places in the tree use the following pattern:
entry-for-unix
entry-for-osx os=Darwin
entry-for-windows os=WINNT
This works because subsequent manifest entries with more specific flags
override previous manifest entries.
Incidentally, this led to problems such as the one mentioned in
changeset c94e87a18096.
Now that there is a flag for !Darwin !WINNT !Android, we can use it
instead.
--HG--
extra : rebase_source : 6bde84ca3a322cb82847e49c789e444e21703fe3
Capture each media stream's length (as provided, otherwise as actually
downloaded), to gauge whether keeping media in memory would have a significant
impact.
MozReview-Commit-ID: 4yUQrbgLcGG
--HG--
extra : rebase_source : bed0ea1d58f864463926478b0f8ea59e7084c4af
In case some legacy third-party things were relying on those files being
under a unix/ directory, revert the part of changeset c94e87a18096 that
renamed global-platform/unix to global-platform/gtk.
--HG--
extra : rebase_source : bb78b309fe59ee5f76f276e54539e157eb019e69
Since it wasn't possible to have specific manifest entries for !Darwin
!WINNT !Android, a few places in the tree use the following pattern:
entry-for-unix
entry-for-osx os=Darwin
entry-for-windows os=WINNT
This works because subsequent manifest entries with more specific flags
override previous manifest entries.
Incidentally, this led to problems such as the one mentioned in
changeset c94e87a18096.
Now that there is a flag for !Darwin !WINNT !Android, we can use it
instead.
--HG--
extra : rebase_source : 6f20a9b31d48c8ee4126662730e95789de740971
This is a Linux-specific feature and other platforms don't have it (see also
the conditional in Troubleshoot.jsm and the ifdef in aboutSupport.xhtml).
MozReview-Commit-ID: IISzOvWXwCp
--HG--
extra : rebase_source : d57c2b42003619ed13a5bb6afe219d16c5d575ae
This allows native messaging binaries to identify the add-on that
invoked the native messaging app, in case more than one add-on is
allowed to launch the native messaging app.
MozReview-Commit-ID: GgjwfJDbBkW
--HG--
extra : rebase_source : b60d33e9f3936f26b8792ef5cd1f9fea304f29ae
GHOST_WINDOWS will be used to satisfy Quantum release criteria. As such, we
need release-channel collection.
Near as I can tell the memory manager works just as well in Release as in
pre-release, so this should be all that's necessary.
MozReview-Commit-ID: 1iLJhlgKoVQ
--HG--
extra : rebase_source : f5ae38b0693734c03278c1c0dde9e3b835d6a4b9
Without this change, browser_update.js "resets" a preference that it never
changed to a different value, which leaks through to future tests. This was
introduced in a8fcca075fde, and appears to be a simple mistake since that change
removes a setup/teardown pref change pair, but the prefs it changes are two
different ones!
This leaked pref change leads to test failures when special powers and mochitest
are installed as non-temporary addons.
MozReview-Commit-ID: 2jx3fB1iZMx
--HG--
extra : rebase_source : 35394dda16814d80116854bd40c00c95f30d34e2
In addition to updating webrender and webrender_traits, this patch:
- bumps the euclid dependency in webrender_bindings to match webrender
- updates the Cargo.lock files and re-vendors third-party rust packages
- updates the push_yuv_image callers due to an API change in WR cset a4b9e25.
Implement privacy.network.peerConnectionEnabled to allow WebExtensions to enable and disable RTCPeerConnections (aka WebRTC).
MozReview-Commit-ID: 5zGotQNwsko
--HG--
extra : rebase_source : 3543efa9fdbd7689581b3ffd3507cf2b4fee284d
Allow the use of the subsection render not just for the environment data.
It could help future developer to display subsection for another special
ping data. Also it will help with the redesign of the UI.
MozReview-Commit-ID: DHoS7Zw7IyC
--HG--
extra : rebase_source : a6ca4c0218c5b73c4c3e383886c9e94ec3f7f93d
GenericTable expect an array of array as data where KeyValueTable used to expect an object.
Use explodeObject() to process an object so it can be used by GenericTable.
MozReview-Commit-ID: 6hxxFwF2KXg
--HG--
extra : rebase_source : 29b2636eeea2f980182e5127f1e3f98630188e10
Both provide the same functionality so we only need to keep one of them.
MozReview-Commit-ID: AOiiRiFr1fD
--HG--
extra : rebase_source : 8e3b8d3f80c320f4a40fa4b5ba383fc323d15806
Most of the sections were already in their own object. This fixes the one that are not.
MozReview-Commit-ID: 92lAtwYwbDl
--HG--
extra : rebase_source : 8f1ad8d7e5fe18958858130bde8eb542782ad61a
Introduce the replacement of KeyValueTable by GenericTable.
Both provide the same feature so we only need one.
MozReview-Commit-ID: AyWKPkrlX64
--HG--
extra : rebase_source : 20547cab0a53f2e122f0cebdcac3eb3f24eedde1
Gathering this data point takes up to 100ms on reference hardware and might impact
startup performance.
MozReview-Commit-ID: 32sd5uUF08N
--HG--
extra : rebase_source : a80da25b384b47995cc25db9a711ef02ca5842cd
Collect telemetry for all requests to get an exact percentage of
requests that are subject to HSTS priming, and how many result in an
HSTS Priming request being sent. Clean up telemetry to remove instances
of double counting requests if a priming request was sent.
HSTSPrimingListener::ReportTiming was using mCallback to calculate
timing telemetry, but we were calling swap() on the nsCOMPtr. Give it an
explicit argument for the callback.
Add tests for telemetry values to all of the HSTS priming tests. This
tests for the minimum as telemetry may be gathered on background or
other requests.
MozReview-Commit-ID: 5V2Nf0Ugc3r
--HG--
extra : rebase_source : daa357219a77d912a78b95a703430f39d884c6ab
Several years ago there was a single zip file for all test files. Clients
would only extract the files they needed. Thus, zip was a reasonable
archive format because it allowed direct access to members without
having to decompress the entirety of the stream.
We have since split up that monolithic archive into separate,
domain-specific archives. e.g. 1 archive for mochitests and one
for xpcshell tests. This drastically cut down on network I/O
required on testers because they only fetched archives/data that
was relevant. It also enabled parallel generation of test archives,
we shaved dozens of seconds off builds due to compression being
a long pole.
Despite the architectural changes to test archive management, we
still used zip files. This is not ideal because we no longer access
specific files in test archives and thus don't care about single/partial
member access performance.
This commit implements support for generating tar.gz test archives.
And it switches the web-platform archive to a tar.gz file.
The performance implications for archive generation are significant:
before: 48,321,250 bytes; 6.05s
after: 31,844,267 bytes; 4.57s
The size is reduced because we have a single compression context
so data from 1 file can benefit compression in a subsequent file.
CPU usage is reduced because the compressor has to work less with
1 context than it does with N. While I didn't measure it, decompression
performance should also be improved for the same reasons. And of course
network I/O will be reduced.
mozharness consumers use a generic method for handling unarchiving.
This method automagically handles multiple file extensions. So as long
as downstream consumers aren't hard coding ".zip" this change should
"just work."
MozReview-Commit-ID: LQa5MIHLsms
--HG--
extra : rebase_source : 100092c2f2ff609362a724fff60f46dd6e49c94e
extra : intermediate-source : d10f5ccd882b965fcad39914f7c3c930d1301a41
extra : source : a0e257e346ccf3c1db332ec5903241f4eeb9a7ee
Most consumers of `GetBookmarkIdsForURI` already don't need tags, the only
consumer which does (`TaggingService`) has been changed to use a separate
database query.
MozReview-Commit-ID: LabjaA6Q0GF
--HG--
extra : rebase_source : e13dc730a53b5b46ca1766bf896112aa65aa00af
This was found by Coverity Scan (CID 1409773, 1409774).
MozReview-Commit-ID: LA7oPMobbie
--HG--
extra : rebase_source : 0ca4245e445f0b0da0073cee7b5ee95c621af75f
This changes the `Scheduler.post` method to check for options in the `args`,
and accordingly update it with the time it takes for running `Scheduler.worker.post`.
This also changes the `test_duration.js` to add another duration (serialization duration)
for the operations where `Scheduler.post` is called.
MozReview-Commit-ID: EGPeHfMYI1U
--HG--
extra : rebase_source : caa281e6ad9cee1a39a7196c7253cae782c771db
Also removes some dead code.
A lot of the code in ExtensionUtils.jsm is not needed in all processes, and a
lot of the rest isn't needed until extension code runs. Most of it winds up
being loaded into all processes way earlier than necessary.
MozReview-Commit-ID: CMRjCPOjRF2
--HG--
extra : rebase_source : 37718eaf05a22b8ccb95f633cf7454bd7975cdce
Capture each media stream's length (as provided, otherwise as actually
downloaded), to gauge whether keeping media in memory would have a significant
impact.
MozReview-Commit-ID: 4yUQrbgLcGG
--HG--
extra : rebase_source : bed0ea1d58f864463926478b0f8ea59e7084c4af
security/ is already skipped through top-level moz.build. For
convenience, we skip the DIRS that end up adding GYP_DIRS, avoiding
reindenting their entire moz.build.
--HG--
extra : rebase_source : 346aba5f4ec29112cb2ce035844e57f13a214482
Ryan VanderMeulen
Kris Maglione
Sebastian Hengst
UK992
Gerald Squelart
Marco Bonardo
Wes Kocher
Servo VCS Sync
Benjamin Smedberg
Ehsan Akhgari
Georg Koppen
Carsten "Tomcat" Book
Dão Gottwald
Georg Fritzsche
Kartikaya Gupta
Blake Kaplan
Chris H-C
Jonathan Guillotte-Blouin
David Keeler
Shane Caraveo
Ralph Giles
Axel Hecht
Andrew Swan
Tomislav Jovanovic
Mark Banner
Kit Cambridge
Tom Ritter
J. Ryan Stinnett
Kate Ustiuzhanina
Leni Kadali
Henry Chang
Stephen A Pohl
Michael Layzell
Andreas Farre
Christoph Kerschbaumer
Robert Strong
milindl
flyingrub
Tim Taubert
Bob Owen
Raajit Raj
Jared Hirsch
Joel Maher
Nathan Froyd
Florian Quèze
Gabriele Svelto
Mike Hommey
Jed Davis
Edouard Oger
Rob Wu
Dan Banner
Alex Gaynor
Bob Silverberg
Julian Descottes
Jessica Jong
Liang-Heng Chen
Alessio Placitelli
DimiL
Scott Wu
Kate McKinley
Rajesh Kathiriya
Gregory Szorc
Sean Lee
Timothy Guan-tin Chien
Masatoshi Kimura
Michael Kaply
steveck-chung
Kirk Steuber
Luca Greco