manifest.json has character limits for name (45) and description (132).
Language packs now use:
name: Language: {native_name} ({english_name})
description: {app} Language Pack for {native_name} ({locale_code}) – {english_name}
The English name is omitted if identical to the native name, and it's omitted from the name if the resulting name exceeds the character limit.
Longer name or description are always truncated.
Differential Revision: https://phabricator.services.mozilla.com/D164535
If we want to use individual-files for a lot of files, all
of which are going the same place, it is very verbose and
repetitive. Create an alternate, mutually-exclusive way of
specifying individual-files in a moz.yaml
Differential Revision: https://phabricator.services.mozilla.com/D163969
- make sure the patch files are sorted before we apply them
- strip trailing slashes from the repo url before we add more
- Allow the individual-files action to be used by individual-files
Differential Revision: https://phabricator.services.mozilla.com/D163968
Switches from `buildconfig.substs` to `bootstrap_toolchain` for the repackage job
Refactors mozpack/dmg to not depend on the environment; Moves path resolution of tools up to `mozbuild.action.{make_dmg|unpack_dmg}`
Update syntax to python 3.7+
Differential Revision: https://phabricator.services.mozilla.com/D163129
The JSON data added here is derived from mozIntl.sys.mjs for the native names,
and Intl.DisplayNames for the English names. Once it becomes possible to
synchronously import JSON from JS code, this data should be merged with that
used by mozIntl.sys.mjs.
Differential Revision: https://phabricator.services.mozilla.com/D163049
Switches from `buildconfig.substs` to `bootstrap_toolchain` for the repackage job
Refactors mozpack/dmg to not depend on the environment; Moves path resolution of tools up to `mozbuild.action.{make_dmg|unpack_dmg}`
Update syntax to python 3.7+
Differential Revision: https://phabricator.services.mozilla.com/D163129
According to Transvision, this is barely localized (only two locales set
a non-default width, and they all do it to just slightly more than
usual).
So standardize the initial size on that (800x500), remove the
localization, and remove the minimum size constraint, which wasn't there
before the regressing bug.
Differential Revision: https://phabricator.services.mozilla.com/D163511
Now that we depend on modern versions of python 3, we shouldn't have SNI
problems anymore. OTOH, the S3 address somehow causes certificate
problems on some setups (similar to bug 1787993), while the original
address doesn't, so this is all for the better.
Differential Revision: https://phabricator.services.mozilla.com/D163170
We don't check for pkg-config on some platforms (Windows, OSX, Android).
On those platforms, calling 'pkg_check_modules' will not work. Adding
the same 'when' used for the 'pkg_config' check to all the options that
end up calling 'pkg_check_modules' effectively disables them, and prevents
'pkg_check_modules' from being called.
Differential Revision: https://phabricator.services.mozilla.com/D150649
Before bug 1798291, all rust libraries were built in the same target
directory, and rust programs were built in a separate target directory
each. Cargo would be allowed to run in parallel for each target
directory. After bug 1798291, everything rust hits the same target
directory, so the normal behavior for Cargo is to block itself if run
multiple times. What this means in terms of the build is that now those
Cargos that are waiting are taking a make token, preventing other work
from happening.
It also turns out that on Solaris, Cargo doesn't block, and those Cargos
running in parallel are stepping on each other's toes.
By serializing, we ensure this doesn't happen. This should have been
done at the same time as bug 1798291 but I overlooked this.
Differential Revision: https://phabricator.services.mozilla.com/D163019
Nowadays, we don't need to bootstrap as many packages as we used to,
thanks to the bootstrapped tools and sysroots. The first step here is to
install the common base of necessary packages. As a matter of fact, none
of the other packages are necessary anymore, but we'll clean that up in
a followup patch.
This change and the followups have been tested on base docker images of
Arch Linux, Debian 10, 11, 12, Fedora 36, 37, Gentoo, OpenSUSE Leap,
Tumbleweed, Rocky Linux 8, Ubuntu 22.04, 22.10, Void Linux, and a Live
ISO of Solus Linux, with the assumption that actual users would have at
least what those images contain (and some of them are pretty barebones,
to the point that some of the base packages listed seem would seem
ridiculous... in fact we hadn't needed to include them so far).
Differential Revision: https://phabricator.services.mozilla.com/D162955
Nowadays, none of these are necessary. Some were there for compatibility
reasons (old ncurses, 32-bits libraries) that are long gone, and in the
case of openSUSE, it was not updated when we made the generic android
code bootstrap a JDK itself in bug 1740358.
Differential Revision: https://phabricator.services.mozilla.com/D162939
--enable-bootstrap doesn't cover everything that `mach bootstrap` deals
with, but the opposite is true, and it's redundant to have to maintain
a list of things to bootstrap when configure already knows what it
wants.
As a side effect, this now makes `mach bootstrap` install wasi-sysroot,
which it wasn't doing before.
Differential Revision: https://phabricator.services.mozilla.com/D162683
For some reason, in most cases, there is no redirection, but once in a
while, there is, and that breaks the download.
At the same time, make the download messages tell the url that is being
downloaded rather than where it is downloaded to.
Differential Revision: https://phabricator.services.mozilla.com/D162952
In the optics of running an end-to-end bootstrap on automation, it can
be useful to allow the standalone bootstrap to start from a repository
that is not mozilla-unified, so that, e.g. changes can be tested on try.
Differential Revision: https://phabricator.services.mozilla.com/D162695
This removes the `intl:app-locales-changed` event listener that was added in bug 1760825, as it's not longer required.
Depends on D159017
Differential Revision: https://phabricator.services.mozilla.com/D159018
This adds a subcommand ./mach cargo udeps with the following
sub command arguments:
Sub Command Arguments:
--all-crates Check all of the crates in the tree.
crates The crate name(s) to check.
--jobs [jobs], -j [jobs]
Run the tests in parallel using multiple
processes.
-v, --verbose Verbose output.
--message-format-json
Emit error messages as JSON.
--expect-unused Do not return an error exit code if udeps
detects unused dependencies.
Differential Revision: https://phabricator.services.mozilla.com/D159838
It was not installed consistently across platforms, and I think the only
reason we installed it had been superseded by the `mach uuid` command
(which didn't rely on it), and the `mach uuid` command was removed in
bug 1639509.
Differential Revision: https://phabricator.services.mozilla.com/D162636
It used to be necessary to set the target for android builds, but that
hasn't been the case since bug 1523341. In fact, that bug removed the
--target for non-artifact android builds, but somehow left this one
alone.
Differential Revision: https://phabricator.services.mozilla.com/D162634
--enable-application is the historic flag, and --enable-project was
added to handle the non-application things we build, while encompassing
the meaning of --enable-application. --enable-project has been preferred
for a while and we should reflect that more consistently in mozconfigs,
documentation, etc.
Differential Revision: https://phabricator.services.mozilla.com/D162625
At the time the message is printed, installing git-cinnabar hasn't even
been tried (it happens in the in-tree bootstrap, not the sandalone
bootstrap, which this is) ; we have installed a temporary copy of
git-cinnabar, which may fail, but if it does, we'd throw an exception
before reaching this message anyways.
Differential Revision: https://phabricator.services.mozilla.com/D162611
For the specific case of `.xpt` artifacts, we could place them
directly into `$topobjdir/config/makefiles/xpidl`, but I'm wary of
modifying the object directory in this manner. I'd like the initial
round of tooling building on this capability to look in
`dist/xpt_artifacts` for artifact builds and be able to give detailed
feedback in error situations. We can revisit the placement of
artifacts in the future as more use cases and shortcomings are
identified.
In the future, this mechanism might be used to include Java code
generated at build-time that exposes IDL constants to GeckoView.
Differential Revision: https://phabricator.services.mozilla.com/D161641
- `mozlog` version bump to `7.1.1`
- Changed `mozlog` dependency on `blessings` to `blessed`
- Some sugar lookups in `blessed` (Like `normal`) don't behave the same as the rest, so our code needed to change to handle the case when the lookup didn't return a callable.
- The tests in `test_widgets.py` and `test_terminal.py` were never actually being run (it was skipping because when importing `Blessings` it failed to import `_curses`). Given that, a portion of `test_terminal() never actually worked, and it wasn't known because the test didn't run (I didn't just delete half the test case because it didn't work, I deleted it because it can never work =P).
- I added a `test_terminal_colors.py` just to ensure that there's some coverage there, since `dim` and `normal` were failing (but CI was happy).
Differential Revision: https://phabricator.services.mozilla.com/D161858
On POSIX platforms there can be `lib` and `lib64` for `site-packages`.
On Fedora35 once a virtualenv is created, `lib64` is a symlink of `lib`.
Since we can determine what these paths will be before the virtualenv is
created, `realpath` has different results before/after, which is
problematic for our `pthfile`.
Since we only care about resolving the symlink in the prefix (to keep it
in line with the `topobjdir`, we can simply only `realpath` that and
disregard that there's a symlink between `lib` and `lib64`, which makes
our `pthfile` that's created and expected always the same on all
platforms.
Differential Revision: https://phabricator.services.mozilla.com/D162136
That's what we were doing before bug 1796956. Not preferring .exes
makes us choose hg over hg.exe, and CreateProcess doesn't know how
to execute the former.
Differential Revision: https://phabricator.services.mozilla.com/D162064
`packaging.version` can handle additional text in the version number (eg: `4.0pre1` and `4.0.2rc1`) that `LooseVersion` cannot.
Differential Revision: https://phabricator.services.mozilla.com/D161756
MOZ_BACKGROUNDTASKS should be undefined when the feature is disabled.
Add some more tests for `when` parameter of set_config() and set_define().
Differential Revision: https://phabricator.services.mozilla.com/D161400
There is a bug in Poetry 1.2.0a2 caused by a breaking change
on PyPi's end: https://github.com/pypi/warehouse/pull/11775
This bug was fixed in Poetry 1.2.0b3, but 1.2.0b1 dropped
support for Python 3.6, which is a requirement for us.
As a temporary workaround, we can patch the fix into our
virtualenv's copy of Poetry. This patch should be removed
once we switch to using a newer version of Poetry.
Differential Revision: https://phabricator.services.mozilla.com/D161544
- The old implementation also disabled the terminal handler and formatter, which also removed certain colored output and we don't want that.
Differential Revision: https://phabricator.services.mozilla.com/D160440
- The bug that was constantly disabling `VIRTUAL_TERMINAL_PROCESSING` has been fixed upstream in CYGWIN (fdbd153932) and merged into MSYS2 (e4fdb0cb73)
- The upcoming MozillaBuild `4.0.2` release will have the updated MSYS2 that contains this fix, allowing us to enable colored output on Windows.
- We will enable `ENABLE_VIRTUAL_TERMINAL_PROCESSING` once (For each stdout and stderr) on initializing the formatter to ensure that `VIRTUAL_TERMINAL_PROCESSING` is enabled whenever Mach is called..
- These changes will only be active if the MozillaBuild version is greater than or equal to Release `4.0.2`
Differential Revision: https://phabricator.services.mozilla.com/D138256
- Also vendored various `blessed` dependencies
- Added an exclusion for "ansicon" and vendored a "dummy" of it so that we don't vendor the DLLs it includes. It should rarely be needed in practice, and with the dummy in place it should just fail gracefully in the event that it is needed.
Differential Revision: https://phabricator.services.mozilla.com/D160405
- The old implementation also disabled the terminal handler and formatter, which also removed certain colored output and we don't want that.
Differential Revision: https://phabricator.services.mozilla.com/D160440
- The bug that was constantly disabling `VIRTUAL_TERMINAL_PROCESSING` has been fixed upstream in CYGWIN (fdbd153932) and merged into MSYS2 (e4fdb0cb73)
- The upcoming MozillaBuild `4.0.2` release will have the updated MSYS2 that contains this fix, allowing us to enable colored output on Windows.
- We will enable `ENABLE_VIRTUAL_TERMINAL_PROCESSING` once (For each stdout and stderr) on initializing the formatter to ensure that `VIRTUAL_TERMINAL_PROCESSING` is enabled whenever Mach is called..
- These changes will only be active if the MozillaBuild version is greater than or equal to Release `4.0.2`
Differential Revision: https://phabricator.services.mozilla.com/D138256
- Also vendored various `blessed` dependencies
- Added an exclusion for "ansicon" and vendored a "dummy" of it so that we don't vendor the DLLs it includes. It should rarely be needed in practice, and with the dummy in place it should just fail gracefully in the event that it is needed.
Differential Revision: https://phabricator.services.mozilla.com/D160405
This commit updates the outdated documentation for producing multi-locale
packages, and also arranges for Android multi-locale packages to produce a
GeckoViewExample binary that has `libs` and `assets/omni.ja`. Together, these
greatly ease multi-locale testing.
Differential Revision: https://phabricator.services.mozilla.com/D160705
This patch adds a `capture_log` flag that will allow a user to capture the logs produced when running the `push_to_try` methods. Currently, we use `subprocess.check_call` which causes hg to hang when we attempt to redirect and gather stdout. Using `subprocess.run` is better as it lets us capture the logs, but the log output is very slow and can easily lead people to believe that hg is hanging when it's not. This results in corrupted repos. Using Popen, the logs are output slower than `check_call`, but faster than `run` so you know something is happening. The speed at which these logs are printed is also why I have this log capturing behind a flag.
This functionality will be used in the `./mach try perf` selector to capture the child revisions produced for the try task config file changes and allow us to produce a PerfCompare link to provide the user.
Differential Revision: https://phabricator.services.mozilla.com/D155980
The download.py script can now run without a clone, which solves e.g.
problems stemming from the temporary git repository on windows.
It also now pulls from github by default, which doesn't suffer from
certificate validation issues like the taskcluster artifacts urls do.
Also, the self-update git-cinnabar subcommand handles upddates itself,
which leaves python out of the loop.
Differential Revision: https://phabricator.services.mozilla.com/D160997
These are changes to decouple the MSIX repackaging from Firefox/browser and
allow repackaging Thunderbird. Branding and MSIX template paths are now found
by inspecting the input file rather than hard-coded values.
Differential Revision: https://phabricator.services.mozilla.com/D159657
By bug 1715232, we added ICU4X license SHA256 hash to whitelist. But when
releasing ICU4X 1.0, license becomes Unicode-DFS-2016 like ICU4C. So I would
like to allow this license to import ICU4X 1.0.
Also, due to dependencies, some crates still use old ICU4X license. Although it
will be fixed by 1.1 release, we keep this hash.
Differential Revision: https://phabricator.services.mozilla.com/D160588
Now that Python's stdlib `venv` is used, `virtualenv` is no longer
needed.
Since mozharness depends on the wheels for `setuptools` and `pip`, and
they were vendored within `virtualenv` we must move them somewhere else.
I've chosen to add `third_party/python/venv/wheels` to hold those wheels
now that `virtualenv` is no longer there.
Depends on D145786
Differential Revision: https://phabricator.services.mozilla.com/D145787
Brew's Python 3.10 causes `virtualenv==20.7.2` to produce a wonky folder
structure (`$venv/opt/homebrew/lib/python3.10/site-packages`?).
This is likely fixed with newer `virtualenv`, but the simpler workaround
here is to use `venv` instead now that Python 3 is always used.
Adds `python3-venv` to docker image so that tests and debian-based tasks
can leverage it.
Differential Revision: https://phabricator.services.mozilla.com/D144872
The version of git-cinnabar that the bootstrap script pulls now doesn't
require Mercurial. Even older versions have been working fine without
Mercurial for a while.
Differential Revision: https://phabricator.services.mozilla.com/D160601
The fix for bug 1759555 involves having rust-analyzer invoke `mach`.
However, `mach` can't be executed directly on Windows systems -- it's a
Python script, not an executable, and so `::CreateProcessW` has no idea
what to do with it.
Work around this by having `mach` explicitly direct `rust-analyzer` to
use `sys.executable` to execute `mach`.
Differential Revision: https://phabricator.services.mozilla.com/D160306
It can be a frustrating experience to push something to e.g. try, get
build errors, fix them, and realize on a subsequent push that there were
other build errors, but since the build failed as soon as it reached the
first error, the logs didn't show them.
While stopping at the first error locally is more helpful locally
(although it still stop immediately and errors are often buried in the
logs), it is actually desirable to avoid stopping on automation.
Differential Revision: https://phabricator.services.mozilla.com/D154327
While we're here, make the setup more consistent across host/target
c/c++, and remove the C compiler warning flags from the C linker flags,
where they are irrelevant.
Differential Revision: https://phabricator.services.mozilla.com/D159358
I noticed that 'branch' is only used in Updatebot in the
Commit Alert task (we made it for Angle.) It doesn't do
anything anywhere else. So assert this in the validation checks
Differential Revision: https://phabricator.services.mozilla.com/D158047
If there is a vendoring section missing in the moz.yaml,
we will error out. Detect this right away and give a better error.
Perform some cleanup since we know we have a vendoring section.
Differential Revision: https://phabricator.services.mozilla.com/D158046
Also change the default value for --jobs to 0 instead of 1, because
`make -j1` doesn't initialize a jobserver, so cargo uses all cores,
which is a fine default, but now that we may also invoke the rest of
the build system, and because `make -j1` for that is slow, we instead
use 0 as the default (which means auto-detect).
Differential Revision: https://phabricator.services.mozilla.com/D159336
This migration creates the first FTL file under mobile/android/.
As GeckoView isn't actually localised (see bug 1605358), this file
is not exposed to localisers.
A migration script is still included, as previous localisations of
the about:config view's strings are available from its Fennec days.
Running the script will fail in an m-c checkout bootstrapped for
desktop development; it's possible to hack around this by manually
setting the `l10n_toml` value in `python/l10n/test_fluent_migrations/fmt.py`.
Differential Revision: https://phabricator.services.mozilla.com/D155450
This migration creates the first FTL file under mobile/android/.
As GeckoView isn't actually localised (see bug 1605358), this file
is not exposed to localisers.
A migration script is still included, as previous localisations of
the about:config view's strings are available from its Fennec days.
Running the script will fail in an m-c checkout bootstrapped for
desktop development; it's possible to hack around this by manually
setting the `l10n_toml` value in `python/l10n/test_fluent_migrations/fmt.py`.
Differential Revision: https://phabricator.services.mozilla.com/D155450
Make them match a pattern that will be recognized by mozharness as an
error, which, in turn, will make treeherder log parser find them.
Differential Revision: https://phabricator.services.mozilla.com/D159344
The data included in the `Reader:AddButton` message used by SaveToPocket.jsm is slightly modified, as it now includes a localization identifier rather than a preformatted label.
Differential Revision: https://phabricator.services.mozilla.com/D158575
Now that Python's stdlib `venv` is used, `virtualenv` is no longer
needed.
Since mozharness depends on the wheels for `setuptools` and `pip`, and
they were vendored within `virtualenv` we must move them somewhere else.
I've chosen to add `third_party/python/venv/wheels` to hold those wheels
now that `virtualenv` is no longer there.
Depends on D145786
Differential Revision: https://phabricator.services.mozilla.com/D145787
Brew's Python 3.10 causes `virtualenv==20.7.2` to produce a wonky folder
structure (`$venv/opt/homebrew/lib/python3.10/site-packages`?).
This is likely fixed with newer `virtualenv`, but the simpler workaround
here is to use `venv` instead now that Python 3 is always used.
Adds `python3-venv` to docker image so that tests and debian-based tasks
can leverage it.
Differential Revision: https://phabricator.services.mozilla.com/D144872
The data included in the `Reader:AddButton` message used by SaveToPocket.jsm is slightly modified, as it now includes a localization identifier rather than a preformatted label.
Differential Revision: https://phabricator.services.mozilla.com/D158575
The code is slightly cleaned up to not construct identifiers by concatenating strings, and to avoid using the requestTypes array when determining the prompt contents.
A few messages are moved to and from browser.ftl to group them better, though all of the "WebRTC Pop-up notifications" messages could also be moved from there to webrtcIndicator.ftl, which is now also included by browser.xhtml.
The message `webrtc-allow-share-audio-capture-unsafe-delegation` is added, as it appears to have been missed previously -- it's referred to in code, but the message itself was not defined.
Differential Revision: https://phabricator.services.mozilla.com/D158762
Following a suggestion from :mkmelin, this seems like an optimal solution: the overriding/duplication in m-c is removed, and all users get a more powerful default choice that they're still able to override with their own, should they so wish.
For clarity and to match other `about:` pages, the shared code is placed under `toolkit/content/`, and all content under `docshell/resources/` is removed.
Differential Revision: https://phabricator.services.mozilla.com/D156478
To support and enable the migration, quite a bit of refactoring is needed.
Many of the localised error messages are in fact fragments of HTML, including messages with nesting not supported by Fluent. In the FTL, these have each been split up into multiple messages using a custom migration transform (included directly in the script). This allows for localisers to work with the messages without HTML syntax, but does require the messages' structures to be maintained elsewhere. To that effect, the JS file represents messages as arrays of `[tagName, l10nId, l10nArgs]` tuples from which it builds the messages' elements. This fixex bug 1621895.
Though extensive, the refactoring done here is for the most part limited to what's required by the Fluent migration. For instance, not all issues raised in bug 1722896 are resolved here. Places where the structure was sufficiently messy to have introduced bugs or dead code have been cleaned up a bit, though.
This variant of netError that's used by the browser is not itself overridden by anyone else, which allows for it to be tackled first and independently of the docshell and mobile variants. As a part of its content is still passed in as a query parameter, it's possible that later refactors of the rest of the netError system will allow for further clean-up here.
Differential Revision: https://phabricator.services.mozilla.com/D155951
Previously most 'reasons' could only be seen if using a debugger, which
was not helpful when there was a problem in CI.
Depends on D158703
Differential Revision: https://phabricator.services.mozilla.com/D158704
This will resolve issues of drive letter uppercase/lowercase mismatch
causing the venv/site to be considered 'out-of'date'.
Differential Revision: https://phabricator.services.mozilla.com/D158703
Relevant strings from both browser.ftl and browser.properties are collected into a new contentCrash.ftl, which is only loaded when needed.
Differential Revision: https://phabricator.services.mozilla.com/D158649
- Added the variable `OPTIONAL_BROWSER_PACKAGES`, which contains
a list of packages which should, if possible, be installed with
zypper. If that isn't possible because the package can't be
found, just display a warning and continue.
- Add `gconf2-devel` to `OPTIONAL_BROWSER_PACKAGES`, since
gconf2-devel is not available in Tumbleweed repos and also
not required to build Firefox.
Differential Revision: https://phabricator.services.mozilla.com/D152217
This is a condition that happens when going through the js/src code path
in build/moz.configure/init.configure:mozconfig.
Differential Revision: https://phabricator.services.mozilla.com/D157769
This migration creates the first FTL file under mobile/android/.
As GeckoView isn't actually localised (see bug 1605358), this file
is not exposed to localisers.
A migration script is still included, as previous localisations of
the about:config view's strings are available from its Fennec days.
Running the script will fail in an m-c checkout bootstrapped for
desktop development; it's possible to hack around this by manually
setting the `l10n_toml` value in `python/l10n/test_fluent_migrations/fmt.py`.
Differential Revision: https://phabricator.services.mozilla.com/D155450
The synchronous DocumentL10n instance that's created here is not exposed on the root document, as that is the user-defined XML document. The localization root that's connected to it is in a closed shadow root.
This localization won't update on locale changes, but that matches what this view was previously doing.
Differential Revision: https://phabricator.services.mozilla.com/D156544
Since PowerShell is also available on Linux, checking for that is not
sufficient. We must first check if we're on Windows, and if we're not,
return early.
Differential Revision: https://phabricator.services.mozilla.com/D156602
Because the relevant SDK is not installed on the mac workers, we pull it
via fetches and adjust the plain build mozconfig as well as mozconfigs
for rusttest, grouping most things in build/macosx/mozconfig.common.
And because the SDK itself now has all the relevant headers, we don't
need the old check for system C++ headers (which also happens to have
outdated instructions)
Differential Revision: https://phabricator.services.mozilla.com/D156280
The strings from the translation.dtd and translation.properties files are all
merged into a single translationNotification.ftl file.
The string concatenation used in the original is maintained here, as DOM
Localization does not allow for using a <menulist> as a localized element.
Differential Revision: https://phabricator.services.mozilla.com/D155110
Except for the close-notification-message, all of the notification.dtd
strings are only used by popupnotification.js. Accordingly, the strings
are migrated to two different FTL files.
Differential Revision: https://phabricator.services.mozilla.com/D154890
Migrating the strings used by the edit dialogs also allows/requires for their migration elsewhere.
Some streamlining is applied to how autofillEditForms.js gets access to e.g. FormFillUtils methods, so that they are no longer routed via the XHTML files' script tags. The prior independence of this file from internal dependencies appears to have been in place to support its use as a part of the Payments API's UI, but that was dropped in bug 1721229.
The Fluent migration script included in this patch also covers changes from the immediately preceding patch.
The intl documentation change is a typo correction that was noticed while working on this patch.
Differential Revision: https://phabricator.services.mozilla.com/D155705
Migrating the strings used by the edit dialogs also allows/requires for their migration elsewhere.
Some streamlining is applied to how autofillEditForms.js gets access to e.g. FormFillUtils methods, so that they are no longer routed via the XHTML files' script tags. The prior independence of this file from internal dependencies appears to have been in place to support its use as a part of the Payments API's UI, but that was dropped in bug 1721229.
The Fluent migration script included in this patch also covers changes from the immediately preceding patch.
The intl documentation change is a typo correction that was noticed while working on this patch.
Depends on D155478
Differential Revision: https://phabricator.services.mozilla.com/D155705
What are we doing:
- Resolving a few bugs/user requests
Issues being addressed:
- Resolved issue where if the WPT_key.txt file is not available locally it does not affect running ./mach perftest-test
- Added section to WPT where we display the amount of tests we have remaining
- Altered the request_with_timeout function, to better handle requests
Differential Revision: https://phabricator.services.mozilla.com/D155268
Sandor Molnar
Chris H-C
Stanca Serban
andrej
Alex Ionescu
Iulian Moraru
Francesco Lodolo (:flod)
Sylvestre Ledru
Mike Hommey
Mark Banner
Otto Länd
Tom Ritter
Arthur Carcano
Heitor Neiva
Đăng Tú
Gabriel Bustamante
Eemeli Aro
Cristian Tuns
Norisz Fay
Emilio Cobos Álvarez
Shane Hughes
janvi01
Marco Castelluccio
ahochheiden
M. Sirringhaus
Valentin Rigal
Noemi Erli
Marian-Vasile Laza
Itiel
Nick Alexander
Andreas Pehrson
Mathew Hodson
Butkovits Atila
Jan-Erik Rediger
Andrew Halberstadt
Greg Mierzwinski
Alex Finder
Rob Lemley
ohall-m
Makoto Kato
Ryan VanderMeulen
John Schanck
Ray Kraesig
Csoregi Natalia
Paul Adenot
Kagami Sascha Rosylight
Narcis Beleuzu
Cosmin Sabou
Sammy Khamis
pmcmanis
Malte Jürgens
Sebastian Hengst
Olivier Tilloy
Johan Lorenzo
criss
Basix