Move JSON dump loading and CanonicalJSON serialization to a worker to reduce impact on main thread
Differential Revision: https://phabricator.services.mozilla.com/D10064
--HG--
extra : moz-landing-system : lando
Bug 1483553 was fixed by the developers of medium.com so that we can remove
medium.com from the blacklist which prevents strict keypress dispatching on
specific websites.
Differential Revision: https://phabricator.services.mozilla.com/D12398
--HG--
extra : moz-landing-system : lando
When calling nsGlobalWindowOuter::SetOpenerWindow with null we should
make sure to also clear BrowsingContext::mOpener.
Differential Revision: https://phabricator.services.mozilla.com/D11769
--HG--
extra : moz-landing-system : lando
This adds a missing "return undefined", but nothing downstream pays attention
to the return value, so the bug was not observable from script.
Differential Revision: https://phabricator.services.mozilla.com/D12351
--HG--
extra : moz-landing-system : lando
This also renames a few local variables to follow the `unwrapped` convention
(arguments and locals that are not same-compartment with cx have names that
start with `unwrapped`, unless they're wrapped or AutoRealm'd on the next
line).
Differential Revision: https://phabricator.services.mozilla.com/D12350
--HG--
extra : moz-landing-system : lando
The manifest data is used to determine which tests exist, and what type they are
Differential Revision: https://phabricator.services.mozilla.com/D12408
--HG--
extra : moz-landing-system : lando
MOZ_VTUNE is defined on Nightly (because of --enable-profiling). With the HashMap
we only have some memory/perf overhead when we're actually using VTune's JIT code
profiler.
Differential Revision: https://phabricator.services.mozilla.com/D11292
--HG--
extra : moz-landing-system : lando
This test add a check for pointer id to make sure it always reply the
spoofed pointer id when resistfingerpritning is enabled. It also extend
the original test of pointer capture events into a test which tests
mouse and touch interfaces to make sure pointer capture events is
correctly filed even with the spoofed interface id. In addition, it also
adds test for that set/releasePointerCapture only accepts spoofed
pointer id when fingerprinting resistance is enabled.
Depends on D9532
Differential Revision: https://phabricator.services.mozilla.com/D9533
--HG--
extra : moz-landing-system : lando
When fingerprinting resistance is enabled, content should only view the
pointer capture events from the spoofed interface. In order to do so,
first, we need to restrict content to only set or release pointer capture
for only the spoofed pointer id. Second, we have to map other interfaces
into the spoofed one for pointer capture events.
Depends on D9531
Differential Revision: https://phabricator.services.mozilla.com/D9532
--HG--
extra : moz-landing-system : lando
This patch makes it to spoof the pointer id into mouse pointer id
when resistfingerprinting is enabled. And we will only spoof for
content but not for chrome. Since we don't know the pointer id
beforehand, we have to cache the pointer id of the mouse interface when
it is activated. And use that pointer for the purpose of fingerprinting
resistance.
Differential Revision: https://phabricator.services.mozilla.com/D9531
--HG--
extra : moz-landing-system : lando
- Add a new 12px round icon for Console errors.
- Update the warning (triangle) icon to use the same 12px size.
- Update the info icon to use the same 12px size,
and differentiate its design from the error icon.
- Tweak the Console's input and return icons to be a tiny bit
bigger (for better overall visual balance) and crisper @1x.
Differential Revision: https://phabricator.services.mozilla.com/D12250
--HG--
rename : devtools/client/themes/images/devtools-components/checkbox.svg => devtools/client/themes/images/checkbox.svg
extra : moz-landing-system : lando
The contain:paint clipping would be redundant and hence unnecessary in this
scenario, because:
- Scroll frames already clip their descendant frames.
- contain:paint has other (non-clipping-related) effects that prevent
descendant frames from escaping the scrollframe ancestor.
So, no further clipping is required.
This is a behavior change - it works around an issue that makes us fail to
repaint mousewheel-scrolled content inside of any scrollframe that returns true
from ShouldApplyOverflowClipping().
Differential Revision: https://phabricator.services.mozilla.com/D12056
--HG--
extra : moz-landing-system : lando
For touch events, we use 'touchend' to activate document, because 'touchstart' can be the start of either draging
or touch. As 'pointdown' is a precedent event of the 'touchstart', we should not activate document if the source of
event is from touch event.
Differential Revision: https://phabricator.services.mozilla.com/D12333
--HG--
extra : moz-landing-system : lando