When the logic was switched to be by release-type, rc's were accidentally
excluded.
Differential Revision: https://phabricator.services.mozilla.com/D31587
--HG--
extra : moz-landing-system : lando
Stub installers aren't generated on esr branches; the repackage task includes
metadata indicating this. Use this information to filter out upstream artifacts
when use declarative artifacts.
Differential Revision: https://phabricator.services.mozilla.com/D31586
--HG--
extra : moz-landing-system : lando
When snaps started being packaged on archive.mozilla.org, the `build_platform`
of the snap repackge task changed, causing the beetmover dependencies to be
dropped. Switch the platform back so that the dependencies are restored.
Differential Revision: https://phabricator.services.mozilla.com/D31585
--HG--
extra : moz-landing-system : lando
Filters blur(), invert(), etc. can omit argument.
Computed/specified style serialization is a little tricky w.r.t the shortest
serialization principle. Ideally we should serialize `invert(1)` to `invert()`,
but that will be a breaking change, so we always serialize them with an
argument.
Note, Blink/WetKit treat specified (but not computed) style serialization
differently when the specified one is originally without argument. Our
current behavior is the same as pre-Chromium Edge.
Differential Revision: https://phabricator.services.mozilla.com/D31720
--HG--
extra : moz-landing-system : lando
Bug 1548941 restricted under which circumstances we allow the
browser.tabs.remote.autostart pref to turn off e10s. The PGO profileserver.py
script relied on the unittest-required user.js prefs collection to turn off
e10s (see also bug 1196094) via this pref. For PGO builds, we do not set the
MOZ_DISABLE_NONLOCAL_CONNECTIONS env var, which meant that we stopped
honouring the pref to turn off e10s. Unfortunately, this meant that
e10s was inadvertently now switched on for the pgo profiling, which
negatively impacted speedometer on PGO builds (and possibly other tests).
All this change does is re-disable e10s for PGO profiling. We should
investigate how to turn e10s on "properly" for PGO, but we can do that in
bug 1196094, without taking this temporary regression, especially as 68
branches.
Differential Revision: https://phabricator.services.mozilla.com/D31736
--HG--
extra : moz-landing-system : lando
Most of it is not used at this point, this leaves the parts that are used by
MathML, which are minimal.
Differential Revision: https://phabricator.services.mozilla.com/D31706
--HG--
extra : moz-landing-system : lando
In RTL scroll containers, the right most x-axis scroll position is 0 and
leftward scroll positions are negative values. And also
nsLayoutUtils::TransformFrameRectToAncestor, which is used to tell whether the
snap target element is inside the destination snapport or not [1], returns
negative x-axis positions for elements in RTL scroll containers if the element
is positioned at places where the elements are outside of the initial scroll
position (0, 0). So we don't need to tweak snapport postion even in the case
of RTL scroll containers.
Instead, what we needed in the first place is that we choose a proper x-axis
scroll position that the targe element appears inside the snapport.
[1] https://searchfox.org/mozilla-central/rev/11cfa0462a6b5d8c5e2111b8cfddcf78098f0141/layout/generic/nsGfxScrollFrame.cpp#6604-6605,6616-6617
Depends on D31409
Differential Revision: https://phabricator.services.mozilla.com/D31410
--HG--
extra : moz-landing-system : lando
This is part of the effort to get all the other versions of rand out.
Unfortunately the diff is kinda bug because this is the first crate
requiring rand 0.6 which has been split into multiple crates.
Differential Revision: https://phabricator.services.mozilla.com/D30744
--HG--
extra : moz-landing-system : lando
Annotation on main process crashes are written to both the .extra file
(for crash submission) and to the event file so that the browser can
detect the crash when restarting even if the crash report files have
been deleted.
This patch factorizes all the code that writes to both files, cutting
down all the duplicate calls, and fixes an issue with the
BreakpadReserveAddress and BreakpadReserveSize annotations which were
not written to the event file.
Differential Revision: https://phabricator.services.mozilla.com/D31247
--HG--
extra : moz-landing-system : lando
Upon a content process crash or hang crash annotations were incrementally
written into the .extra file starting with the exception handler callback and
then in a number of different places before the file was ready for submission.
This had a number of downsides: since the annotations were directly added to
the file it was impossible to tell which ones were already written at a
certain point in time, additionally some were written twice or even thrice.
The code doing the writing would also behave differently depending on the
contents of the file, the parameters passed to it and the contents of global
variables.
This change overhauls the whole process by keeping the annotations into a
temporary per-crash annotation table which is filled with all the required
annotations before being written out in a single pass when they are ready.
The annotations are gathered from the main process annotation table, the
per-process one (held by the CrashReporterHost) and exception-time specific
ones.
The resulting annotations are slightly different than before the patch: first
of all there are no more duplicate entries in the .extra file and secondly all
content/plugin process hangs annotations are properly filtered, before
annotations that were main process-only would leak into them.
Differential Revision: https://phabricator.services.mozilla.com/D31069
--HG--
extra : moz-landing-system : lando
This removes the XRE_TakeMinidumpForChild() which does not need to be
exposed anymore in the XUL API as well as
IToplevelProtocol::TakeMinidump() which was simply unused.
Differential Revision: https://phabricator.services.mozilla.com/D31062
--HG--
extra : moz-landing-system : lando
This patch sets the screen brightness on the reference Moto G5 and Pixel 2 phones to 50% before starting power tests and resets it to its original value once the test is complete.
Differential Revision: https://phabricator.services.mozilla.com/D31662
--HG--
extra : moz-landing-system : lando
- Put every color in a variable name.
- Add `label:hover` so that the radio input provides visual feedback upon hover.
- Implement "pressed" (`[type="radio"]:active`) and `:focus{border:0}`
to match Photon's design guidelines at
https://design.firefox.com/photon/components/radio-buttons.html
- Implement dark theme for radio inputs (using creative freedom as there
is no Photon guideline for this).
Differential Revision: https://phabricator.services.mozilla.com/D31510
--HG--
extra : moz-landing-system : lando
- Update info.svg to adjust color based on the fill color.
- Use button colors as defined by Photon (without this, the background
of the non-generic buttons are almost indistinguishable when dark
themes are enabled).
- Small refactor of message-bar.css to put all type-specific
declarations in one location.
Differential Revision: https://phabricator.services.mozilla.com/D31509
--HG--
extra : moz-landing-system : lando
Most colors have been replaced with a variable that has the same color
value.
The exception is the border color at the add-on details.
`--grey-90-a20` was replaced with `--in-content-box-border-color`,
whose value is `--grey-90-a30`. This is close enough.
Differential Revision: https://phabricator.services.mozilla.com/D31508
--HG--
extra : moz-landing-system : lando
we're looking to reduce costs on infra. as parallel gcp builds have served their purpose of demonstrating they are possible and valid, we'd now like to disable them until a later date.
Differential Revision: https://phabricator.services.mozilla.com/D31655
--HG--
extra : moz-landing-system : lando
The variable --theme-toolbar-icon-color is not defined in devtools. Let's use --theme-toolbar-color
Differential Revision: https://phabricator.services.mozilla.com/D31493
--HG--
extra : moz-landing-system : lando
A Proguard update in Bug 1550596 optimized away the WebAuthn methods, but
there's a convenient ReflectionTarget defined to say 'hey, don't do that.'
Differential Revision: https://phabricator.services.mozilla.com/D31693
--HG--
extra : moz-landing-system : lando
In bug 1527182 we made it so that APZ can directly drag-scroll scrollframes
that are inside SVG effects, because that's possible with WR on the compositor.
However the code changed in that bug was meant to be kept in sync with
a second piece of code. The second piece of code controls the generation
of ScrollInfo items for scrollframes inside SVG effects - since we can
APZ-scroll them with WR, we don't need the scrollinfo item anymore.
Producing the scrollinfo item was changing the structure of the APZ tree
in terms of where the transform ended up, and was causing badness with
untransforming the drag mouse events.
This patch adds a test that covers the scenario and also corrects the defect
by bringing the two bits of code back in sync.
Differential Revision: https://phabricator.services.mozilla.com/D31647
--HG--
extra : moz-landing-system : lando
Per https://bugzilla.mozilla.org/show_bug.cgi?id=1550625#c5 there is no
mechanism available for FIDO U2F JS API operations on Android. The exposed API
is FIDO2/WebAuthn-only. As such, Firefox cannot support FIDO U2F JS API
operations on Android, and we should disable the u2f preference so that
window.u2f is not set inappropriately.
Differential Revision: https://phabricator.services.mozilla.com/D31695
--HG--
extra : moz-landing-system : lando
Johan Lorenzo
Tom Prince
violet
Henrik Skupin
Ed Lee
Gijs Kruitbosch
Geoff Brown
Emilio Cobos Álvarez
Hiroyuki Ikezoe
Bastien Orivel
Miko Mynttinen
Gabriele Svelto
Gregory Mierzwinski
Rob Wu
Rob Thijssen
Dorel Luca
Julian Descottes
Stephen Donner
Jeff Gilbert
Jared Wein
Bogdan Tara
J.C. Jones
Kartikaya Gupta
Timothy Nikkel
Chris Manchester
Alastor Wu