This stores the clipboard even if it was set in a GTK dialog.
Depends on D50764
Differential Revision: https://phabricator.services.mozilla.com/D50765
--HG--
extra : moz-landing-system : lando
Currently, when a Mochitest has a fail-if annotation, any passing assertions
are reported as EXPECTED-FAIL, which is extremely confusing, and makes it
difficult to understand which parts of the test are still failing without
removing the annotation. What we really want is for passing assertions to
still be reported as passing, and for only actually failing assertions to
reported as EXPECTED-FAIL, which this patch does.
Differential Revision: https://phabricator.services.mozilla.com/D52407
--HG--
extra : moz-landing-system : lando
The positioning of the arrow was correct, but due to the way the arrow was rotated, the visual center of the arrow did not match the center of the arrow box
Backing out the JS change here, CSS patch later in the queue
Differential Revision: https://phabricator.services.mozilla.com/D52668
--HG--
extra : moz-landing-system : lando
The pre-trailhead triplets, added in bug 1594125 through the remote whats-new-panel provider, serve as another onboarding like messages for AS Router.
Differential Revision: https://phabricator.services.mozilla.com/D52755
--HG--
extra : moz-landing-system : lando
Returning BrowsingContext* from these sorts of getters tends to lead to
misuse. WindowProxyHolder is the semantically correct type to return here, in
any case.
Differential Revision: https://phabricator.services.mozilla.com/D52096
--HG--
extra : moz-landing-system : lando
This code was added in bug 465158 to deal with on-demand dial-up
connections. That scenario is hopefully not common anymore.
One benefit of the code was that it excludes network adapters
that share the computers network from being part of network
change notifications, network ID, etc. However, the code assumed
that only adapters with the address 192.168.0.1 would be a ICS
adapter, but trying to set up ICS on Windows 10 actually set the
LAN interface with 192.168.137.1 - so that assumption isn't
valid anymore. So the code is likely not even running for
adapters that are ICS. It may run for adapters which have the
IP 192.168.0.1, but probably that's quite rare as that's more
often a gateway IP than a client IP.
In any case, it's better to just get rid of it and if needed,
however unlikely, we'll replace it with a more modern API.
Depends on D52573
Differential Revision: https://phabricator.services.mozilla.com/D52574
--HG--
extra : moz-landing-system : lando
Old code needed to dynamically load a DLL - which was not available
for windows versions prior to Vista, and if that failed it would
fall back to using an older API.
This patch now calls the methods directly, since we don't have to
worry about the library not being there; we also remove the
fallback, meaning we always call NotifyIpInterfaceChange instead
of falling back to NotifyAddrChange.
Differential Revision: https://phabricator.services.mozilla.com/D52573
--HG--
extra : moz-landing-system : lando
Instead of creating a picture caching slice for any content that
is fixed position, also check if the clip(s) for the cluster are
fixed position or anchored to the scroll root.
This prevents WR creating slices for parallax style effects. There's
not much point in doing this anyway, since those slices will invalidate
due to the spatial node of the clip changing during scrolling. This
also allows subpixel AA to be enabled in more situations.
Differential Revision: https://phabricator.services.mozilla.com/D52621
--HG--
extra : moz-landing-system : lando
The 'deletion-request' ping, which supercedes the 'optout' ping, notifies the
pipeline when a profile opts out of FHR upload. (IOW, when a user on a specific
profile unchecks the box in about:preferences#privacy about sharing
technical and interaction data with Mozilla).
This ping tries its best to reach the pipeline to let them know that we need
to delete data associated with the provided clientId. This means it will remain
pending on the client even after opt out and it will try to resend if upload is
ever re-enabled.
Differential Revision: https://phabricator.services.mozilla.com/D51710
--HG--
rename : toolkit/components/telemetry/docs/data/optout-ping.rst => toolkit/components/telemetry/docs/obsolete/optout-ping.rst
rename : toolkit/components/telemetry/tests/marionette/tests/client/test_optout_ping.py => toolkit/components/telemetry/tests/marionette/tests/client/test_deletion_request_ping.py
extra : moz-landing-system : lando
If we opt out of Telemetry and then back into it, we might end up with
out-of-order writes and deletes to the clientid state file. This would result
in us sending pings with c0ffee canary client ids.
So let's wait for pending save tasks before we process our removal task.
Also, while I'm here, let's add some trace logging to client id operations.
Differential Revision: https://phabricator.services.mozilla.com/D51709
--HG--
extra : moz-landing-system : lando
This allows us to move the call to InvalidateRegionThroughoutSwapchain to just before the call to
NextSurface, which makes it easier to merge the two calls.
Differential Revision: https://phabricator.services.mozilla.com/D50877
--HG--
extra : moz-landing-system : lando
These settings are now supplied during layer creation and never change.
Consumers must now create new NativeLayer objects if they want to change size or toggle opaqueness.
This aligns the NativeLayer API with DirectComposition's capabilities. It also simplifies swap chain
management.
Differential Revision: https://phabricator.services.mozilla.com/D51757
--HG--
extra : moz-landing-system : lando
This patch uses a cache dir at ~/.condprof-cache so
we avoid re-downloading the same file several times.
Differential Revision: https://phabricator.services.mozilla.com/D52180
--HG--
extra : moz-landing-system : lando
It's being used in the client and server, and so is a shared file.
Differential Revision: https://phabricator.services.mozilla.com/D52247
--HG--
rename : devtools/server/performance-new/gecko-profiler-interface.js => devtools/shared/performance-new/gecko-profiler-interface.js
rename : devtools/server/performance-new/moz.build => devtools/shared/performance-new/moz.build
extra : moz-landing-system : lando
To test this feature, check the "JSTracer" feature, and the user should be
prompted with a message bar to restart the browser. This will then set the
proper environment variable. Unfortunately, currently the user can still do
this even if a feature is not available in the build. See Bug 1585659.
Differential Revision: https://phabricator.services.mozilla.com/D50085
--HG--
extra : moz-landing-system : lando
Karl Tomlinson
Kris Maglione
Andreas Farre
Henrik Skupin
Bert Peers
Andrei Oprea
Julian Descottes
Nan Jiang
Sylvestre Ledru
Steve Fink
Mark Hammond
xueli
Noemi Erli
Michael Kaply
Valentin Gosu
Glenn Watson
Daniel Holbert
Chris H-C
Micah Tigley
Emilio Cobos Álvarez
Andrea Marchesini
Neil Deakin
Mats Palmgren
Markus Stange
Cosmin Sabou
Tarek Ziadé
Greg Tatum