The code here was introduced to fix bug 1053048, but the test there and the
test-case there no longer need this, and it's generally unsound to do stuff that
changes the state of the input from UnbindFromFrame().
I'll file a new bug for the bogus disabled styling in the test-case in a second.
I don't know how to add a test for this (no less because the testcase crashes on
debug builds regardless of this patch, see bug 1551192).
Differential Revision: https://phabricator.services.mozilla.com/D30914
--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
To not collide with the built-in "filter" method, the local
filter module should be named as filters.
Differential Revision: https://phabricator.services.mozilla.com/D30532
--HG--
rename : testing/raptor/raptor/filter.py => testing/raptor/raptor/filters.py
extra : moz-landing-system : lando
`mach run` as it is doesn't really parallel `mach run` on Desktop;
this makes it a little closer more fully featured. The underlying
functionality is all there in layers of mozharness; let's make it
easier to get to.
Differential Revision: https://phabricator.services.mozilla.com/D18292
--HG--
extra : moz-landing-system : lando
