Nothing in js/ uses TARGET_XPCOM_ABI, so the code in js's configure is
dead. Since TARGET_XPCOM_ABI is a Gecko-only thing, the reasonable
place for it is toolkit/moz.configure.
TARGET_XPCOM depends on TARGET_COMPILER_ABI, and the value of
TARGET_COMPILER_ABI is easily derivable from the current target and
compiler. The only notable change we make in the conversion to
moz.configure is that the ARM old-ABI is no longer supported by any of
our current targets: Android and Linux for ARM targets are both
exclusively EABI nowadays, so we have one less case to worry about.
TARGET_COMPILER_ABI's sole purpose was to provide information for
TARGET_XPCOM_ABI, and since we are deriving TARGET_XPCOM_ABI exclusively
inside moz.configure, we can remove TARGET_COMPILER_ABI.
This adds an attribute 'noShell' to nsIProcess that is used to launch a process
using CreateProcess() if we are sure we are launching an executable and don't
require the extra work of the Windows shell service.
MozReview-Commit-ID: 7p0iHCZK1uX
This patch adds an overload to nsIContentIterator::Init which accepts
RangeBoundary objects, and modifies the codepath to avoid using the offset of
the start or end nodes to construct the nsIContentIterator.
MozReview-Commit-ID: 5ZqKeiUunoN
The easy part of this patch is the addition of the RustTest itself.
The more difficult to understand part of the patch is the changes to all
of our Rust build configuration. We do this due to a bug in cargo:
https://github.com/rust-lang/cargo/issues/3923
where features on dependent crates are not correctly taken into account
when determining whether cached artifacts on disk are valid and whether
they should be evicted from the disk cache. The practical upshot of
this behavior is that, say, running gtests during normal development
when files in libxul are modified will:
* rebuild some Rust dependencies for libxul;
* link libxul;
* rebuild those same Rust dependencies *again* for libxul-gtest, since
we have different features active and therefore the old artifacts look
to be out of date;
* link libxul-gtest.
Needless to say, this is highly annoying and counterproductive behavior.
The "fix" is to ensure that the gkrust-shared crate explicitly depends
on crates and assigns features to them such that the feature sets do not
change between normal builds and testing builds. This is admittedly
fragile, but it is not the first time this has come up, and is probably
not the last.
Implementation of the search terms in the url fragment was done as concisely as possible(considering the various conditions required, with the underscore when other hash terms are present). To implement search through hashes in URL, the function urlStateRestore() was changed. To make the changes more aesthetic, another function urlSectionRestore() performs the tasks earlier performed by urlStateRestore(), and urlStateRestore() now implements the search parsing and a call to urlSectionRestore().
MozReview-Commit-ID: 9vgjNUpJkQG
--HG--
extra : rebase_source : c2cdb79e74faffa50bfd6636f0877f541f4f6ddf
BrandFullName is now defined in the branding files
MozReview-Commit-ID: 5wmInT9xbrT
--HG--
extra : rebase_source : 97f85c75026a354cbd7f55a4ed9860abad56820b
macOS implementation doesn't use nsPrintProgress, so we should remove this.
MozReview-Commit-ID: FJSXtjlv3mL
--HG--
extra : rebase_source : 2826317c83b9d90066e878899485b7146fd54a85
This allows us to have the same form history GUIDs across devices, which is mandatory
if we want tombstones to actually do something.
MozReview-Commit-ID: Hw6ahbVA5lB
--HG--
extra : rebase_source : 5289322dea430f364790026470ff844f754dd570
The manifest of an extension has two fields, permissions and optional_permissions,
which both take an array of strings consisting of permissions or origins.
The permissions API accepts the same values but within distinct origins and
permissions fields of an object.
This patch modifies the schema to reflect this difference.
MozReview-Commit-ID: 3V3YeWEIVnf
--HG--
extra : rebase_source : 0d2f4b0e7736dbb41169c2690e716b5f48b43d92
* Add -moz-window-drag: drag property to toolbars in toolkit, on Windows as support was added in bug 1163113
* Use the toolbar-drag binding for #nav-bar on Linux.
MozReview-Commit-ID: 8ZABYMWswk1
--HG--
extra : rebase_source : 28c2fceef4991d4684c8249a787995994af1120d
Add telemetry to collect the following:
- Number of times a MediaRecorder is started during a session
- Duration of media recordings
- How often we're timing out init of audio and video track encoders
MozReview-Commit-ID: 9Pc2oKNCH1M
--HG--
extra : rebase_source : 16414a5ffa95413458d36295e5508df4c16e6fa9
Sebastian Hengst
Nathan Froyd
David Krauser
Catalin Badea
Cervantes Yu
Wes Kocher
Ryan VanderMeulen
Ian Moody
Xidorn Quan
Nika Layzell
Vedant Chakravadhanula
Mark Banner
Tim Nguyen
Simon Sapin
Sylvestre Ledru
Dão Gottwald
Alessio Placitelli
Kai Engert
Makoto Kato
Ricky Chien
Servo VCS Sync
Markus Stange
Gabor Krizsanits
Edouard Oger
Scott Wu
Sam Foster
Bryce Van Dyk
Erica Wright