A quick and basic implementation of 'mach test-info report-diff' to provide a
high level comparison of two reports generated by 'mach test-info report'.
Mostly this is trying to give an impression of how many and which tests
have been added and deleted during the time period between the reports.
There is more information in the reports; a more thorough comparison is
possible, but seems lower-value: To be considered in a future bug.
Differential Revision: https://phabricator.services.mozilla.com/D65202
--HG--
extra : moz-landing-system : lando
This is supposed to be a minimal patchset to make Firefox work on
Mutter 3.36 in a similar fassion as on 3.34. The changes should
be compatible with any Wayland compositor, especially those that
do similar agressive culling and frame callback reduction.
While technically non-optimal, they should work as a short time
solution.
1.: Do not commit the toplevel surface in `moz_container_move`. Instead
use `gdk_window_invalidate_rect`, which (hopefully) triggers a surface
commit as well while not interfering in the order of commands. The is
necessary as the previous commit would commit invalid state in certain
scenarios (like fullscreening).
This fixes broken fullscreening.
2.: Do not set an opaque region on containers if that would cover the
whole toplevel surface. This works around problems concerning mouse
input responsiveness, as a completely covered toplevel surface might
not get frame callbacks any more, but we currently rely on it to process
input events like mouse movements.
3.: Only set an opaque region on the toplevel surface when maximized.
While the toplevel opaque region is actually redundant as long as the
content surface has an opaque region set, we need it for workaround 2.
But we want to unset it when not needed as occasianally it is not in
sync, creating glitches when e.g. unmaximizing.
Differential Revision: https://phabricator.services.mozilla.com/D64966
--HG--
extra : moz-landing-system : lando
CLOSED TREE
Backed out changeset d33b655d9fab (bug 963933)
Backed out changeset ed3f61f1c32c (bug 963933)
--HG--
extra : rebase_source : 4cf04bc52117beaf023151fb14601cd8cb3df35b
Since bug 440895, we've got support in sessionstore to support restoring a window
to their respective virtual desktops.
This patch using a deprecated GDK API. It builds and works fine, but not without
compilation warnings.
Differential Revision: https://phabricator.services.mozilla.com/D65105
--HG--
extra : moz-landing-system : lando
Steps to reproduce:
I've got a group of web servers using DNS failover for high availability.
We return a HTTP 421 from the offline server, indicating to the browser
that it should attempt to reconnect.
Actual results:
Firefox acknowledges the 421 and closes connections, but continues to cache
the old DNS.
Expected results:
Firefox should clear DNS on a HTTP 421 as well, to improve the usability of
this status code for DNS failover.
Differential Revision: https://phabricator.services.mozilla.com/D65078
--HG--
extra : moz-landing-system : lando
Make sure we don't try to import arsenic when the condprofile client is used.
Differential Revision: https://phabricator.services.mozilla.com/D65292
--HG--
extra : moz-landing-system : lando
This patch makes the CookieBehavior to be synced with the
CookieJarSettings field in the WindowContext when the document gets the
CookieJarSettings from the LoadInfo. We will only sync the
CookieBehavior but not the CookiePermission here. Because right now we
only need to access the cookieBehavior across process boundaries and
share the cookie permission among processes could leak origin
information.
Differential Revision: https://phabricator.services.mozilla.com/D63938
--HG--
extra : moz-landing-system : lando
We don't need to create the blocking-all cookieJarSettings every time we
request it since it is basically the same. Instead, we should make it as
a singleton.
The patch makes this change the rename the
CookieJarSettings::CreateBlockingAll() to GetBlockingAll() which
reflects the fact that it is a singleton.
Differential Revision: https://phabricator.services.mozilla.com/D64564
--HG--
extra : moz-landing-system : lando
This patch adds a new field CookieJarSettings in the window context.
This makes the CookieJarSettings can be accssible across the process
boundaries, which is needed for the work of making the ETP
Fission-compatible. We reuse the CookieJarSettingsArgs from the
NeckoChannelParams.ipdlh as the field here since it represents the
CookieJarSettings in IPDL and the syncedContext is based on the IPC
between processes. So, I think we can use it directly as a field.
Differential Revision: https://phabricator.services.mozilla.com/D63937
--HG--
extra : moz-landing-system : lando
Given that we are going to add ContentBlockingAllowList in
CookieSettings, so CookieSettings will be responsible for more stuff than the
cookie behavior and cookie permission. We should use a proper name to
reflect the purpose of it. The name 'CookieSettings' is misleading that
this is only for cookie related stuff. So, we decide to rename
'CookieSettins' to 'CookieJarSettings' which serves better meaning here.
Differential Revision: https://phabricator.services.mozilla.com/D63935
--HG--
rename : netwerk/cookie/CookieSettings.cpp => netwerk/cookie/CookieJarSettings.cpp
rename : netwerk/cookie/nsICookieSettings.idl => netwerk/cookie/nsICookieJarSettings.idl
extra : moz-landing-system : lando
I forgot to add this check only here. (I also checked again for all similar
methods' callers.) So, if the point is end of a text node (i.e., offset equals
its length), `IsCharNBSP()` refers wrong address.
I cannot find a way to reproduce this crash, therefore, this patch does not
have new crashtest.
(Additionally, this corrects the misspell in the method name.)
Differential Revision: https://phabricator.services.mozilla.com/D65279
--HG--
extra : moz-landing-system : lando