This change gives a bit more flexibility for isolating issues and seeing which specific marker offset is giving trouble when a test fails.
Depends on D168445
Differential Revision: https://phabricator.services.mozilla.com/D168446
Otherwise, semantics are exposed (e.g. for a table), which completely defeats the author's intent that this be treated as presentational.
Differential Revision: https://phabricator.services.mozilla.com/D170165
Previously, the test was retrieving an Accessible with a non-existent id and calling testAccessibleTree on it.
That meant we were calling testAccessibleTree with null, which is a no-op.
Now, we get the intended Accessible so that the test actually tests what it was supposed to test.
This is important to test a potential bug in the next patch.
Differential Revision: https://phabricator.services.mozilla.com/D170306
Fixes the border radius and color/style of the outline applied to
feature callouts when they are focused. Also applies the focus ring to
the callout's arrow with some CSS changes.
Differential Revision: https://phabricator.services.mozilla.com/D170524
Simplifies some upcoming work to change how we store these when
updating primitive dependencies during picture cache updates.
Differential Revision: https://phabricator.services.mozilla.com/D170546
Fixes the border radius and color/style of the outline applied to
feature callouts when they are focused. Also applies the focus ring to
the callout's arrow with some CSS changes.
Differential Revision: https://phabricator.services.mozilla.com/D170524
This currently only includes block frames, grid containers, and flex
containers, and the document and pagination frames. It is possible more frames
will need to be added or more advanced checks in the future.
This adds some related tests to ignoring some subtrees, but are expected fails
until bug 1816570 is fixed.
Differential Revision: https://phabricator.services.mozilla.com/D169018
Otherwise, semantics are exposed (e.g. for a table), which completely defeats the author's intent that this be treated as presentational.
Differential Revision: https://phabricator.services.mozilla.com/D170165
Previously, the test was retrieving an Accessible with a non-existent id and calling testAccessibleTree on it.
That meant we were calling testAccessibleTree with null, which is a no-op.
Now, we get the intended Accessible so that the test actually tests what it was supposed to test.
This is important to test a potential bug in the next patch.
Differential Revision: https://phabricator.services.mozilla.com/D170306
Testcase 001 and 002 test row-oriented and column-oriented flex container,
respectively. The "a" and "b" variant test `box-sizing:border-box` and
`box-sizing:content-box`, respectively.
Differential Revision: https://phabricator.services.mozilla.com/D170035
Remove all the transition-in and transition-out animations from the
Spotlight dismiss button, leaving the dialog-initial and dialog-last
animations, anticipating that all our messages will either have a
dismiss button on every screen or on none of the screens.
Differential Revision: https://phabricator.services.mozilla.com/D170527
IME for ibus may send composition after filtering `GDK_KEY_PRESS` event
asynchronously. In that case, IME or ibus usually synthesize `GDK_KEY_PRESS`
again for letting the application know what's being handled. However, according
to the bug report, IME may send composition without synthesizing the
`GDK_KEY_PRESS` event.
Without this patch, `IMContextWrapper` dispatches only
`eContentCommandInsertText` event. Then, it'll cause only a set of
`beforeinput` and `input` events. Therefore, web apps may fail to do something
if they listen only composition and keyboard events only in Gecko. For avoiding
Gecko only failure in this case, we should make `IMContentWrapper` handle the
composition with `GDK_KEY_PRESS` event in the queue which it has not handled
yet. Then, web apps can work with `keydown` events whose `key` is `"Process"`.
Differential Revision: https://phabricator.services.mozilla.com/D170031
It is unclear that we want it enabled for all users and this way we don't have to audit the changes in renderdoc-sys.
We can and should revisit this in the future if we feel like it would be useful to ship with webgpu+renderdoc integration.
Differential Revision: https://phabricator.services.mozilla.com/D170492
For programmatic scrolls, we should respect a users general.smoothScroll
preference. If smooth scrolls are disabled, programmatic scrolls with
behavior: "smooth" should be treated as instant programmatic scrolls.
Differential Revision: https://phabricator.services.mozilla.com/D170110
The alias set that we use for MFuzzilliHash depends on suppressions in structured cloning that are only turned on when we do differential fuzzing. Changing the alias set based on differential fuzzing runs into problems with add vs addEffectful, so the simplest fix seems to be returning early if the suppressions aren't active.
Differential Revision: https://phabricator.services.mozilla.com/D170141
On Windows ARM, we currently use the x86 version of the clearkey plugin.
We do however ship Firefox with the ARM version although prior to this
patch it was unused. Now if media.gmp-clearkey.allow-x64-plugin-on-arm64
is set to false, then we will attempt to load the ARM version of the
plugin. The pref remains true by default.
Differential Revision: https://phabricator.services.mozilla.com/D168707
We need to ensure the hash value is the same and remove the old binaries
if not because if we switch architectures without a version bump, we
will continue to use the old binary. Additionally we should also store
both ABI preferences for Windows ARM (x86 and aarch64) to ensure that if
we profile migrate, or update to a new version, we flush the plugins.
Differential Revision: https://phabricator.services.mozilla.com/D168809
Removed the "before request sent map" spec assert which is now unneeded
as to document invariants in the implementation.
Also updated WPT test expectations.
Differential Revision: https://phabricator.services.mozilla.com/D170335
This patch adds two new prefs, gfx.webrender.scissored-cache-clears
.enabled and .force-enabled to control its status beyond the blocklist.
The former is true by default and allows one to turn the feature off by
flipping it to false. The latter allows one to force the feature on even
if the blocklist disables it. It also adds the status to the decision
log in about:support.
Differential Revision: https://phabricator.services.mozilla.com/D170507
Currenty, FP can be invalid (FailFP) at the entries. For future modifications,
the FP has to be kept intact during throw handling/unwinding.
The patch replaces FailFP-hack with FailInstanceReg one. The InstanceReg pinned
register is always points to valid instance, including at the end of the call.
Using that property to signal when trap has occurred.
Differential Revision: https://phabricator.services.mozilla.com/D170105
