All the commits have been reviewed by Mozilla peers on the Cranelift repository.
Differential Revision: https://phabricator.services.mozilla.com/D42479
--HG--
extra : moz-landing-system : lando
This condition was needed when FindInsertionPrevSibling and co didn't understand
display: contents.
Editor is pretty broken (and calls into PresShell::ContentRemoved directly, and
incorrectly, using anonymous nodes).
In this case we were taking the XBL path because of display: contents, which
means that we tried to seek to the editor anonymous node, and crash (since it's
not an explicit kid).
Editor needs to get fixed, but this is technically more correct and fixes the
crash, so we may as well take it in the interim.
Differential Revision: https://phabricator.services.mozilla.com/D42472
--HG--
extra : moz-landing-system : lando
1. As per the spec, if maxTargets is 0, return all targets.
2. Where maxTargets > 0, fix the loop condition so it doesn't incorrectly fetch one more target than requested.
Differential Revision: https://phabricator.services.mozilla.com/D42446
--HG--
extra : moz-landing-system : lando
This uses the layers.d3d11.enable-blacklist pref to allow running WebRender on WARP.
Differential Revision: https://phabricator.services.mozilla.com/D42255
--HG--
extra : moz-landing-system : lando
When we're slotted, we inherit our directionality from the slot element. But
when binding an ltr subtree into an rtl subtree, we used to bind the explicit
kids first, then the shadow root kids (which includes the slots to which
explicit kids may have been assigned).
So the explicit kids looked at the slot directionality before it was recomputed,
and thus ended up with ltr rather than rtl directionality.
Differential Revision: https://phabricator.services.mozilla.com/D42304
--HG--
extra : moz-landing-system : lando
updateLayer expects some objects to be non-null which are only initialized when the pref is set.
But in builds that were compiled with the 10.14 SDK, all NSViews are layer-backed by default, so
wantspdateLayer gets called, and returning YES from that unconditionally will cause updateLayer
to be called.
Differential Revision: https://phabricator.services.mozilla.com/D42333
--HG--
extra : amend_source : a7a1f7ecba9418e3bf5464bca90ba655002bc637
Entering the atoms zone with AutoAllocInAtomsZone is a bit of a special case and we don't support entering another realm in this state. Unfortunately this can happen during GC in a couple of place. The patch temporarily leaves the atoms zone during GC so that callbacks can enter whatever zones they like.
Differential Revision: https://phabricator.services.mozilla.com/D42312
--HG--
extra : moz-landing-system : lando
Automatic update from web-platform-tests
Handle null effect when interrupting a transition
If the effect of a CSS Transition is removed (via the getAnimations API)
and then the transition is interrupted by removing the 'to' style, we
previously assumed that the effect would always exist. This CL adds a
null-check for that case.
Bug: 992668
Change-Id: I399be7fd859bac0ca6e7ee1e29dbcbbae2e89403
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1753671
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686932}
--
wpt-commits: 8194a35b1626cb99346d3b2d008f83998194c2af
wpt-pr: 18428
Automatic update from web-platform-tests
Use observer for sync bases
Previously sync bases would not be updated if the base element was
swapped out. This has been changed to allow for this. Making events
and sync bases work more uniformly.
This is the first step in changing sync base repeats into actual
sync bases.
Bug: 993702
Change-Id: I1a1b381d094100296a420de8877bb1e57cd9709e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1753004
Commit-Queue: Edvard Thörnros <edvardt@opera.com>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Reviewed-by: Fredrik Söderquist <fs@opera.com>
Auto-Submit: Edvard Thörnros <edvardt@opera.com>
Cr-Commit-Position: refs/heads/master@{#686838}
--
wpt-commits: 5777568726d1e9d7e3e0cfa6b65497dcca2de229
wpt-pr: 18419
Automatic update from web-platform-tests
Revert "Changed test_designMode to check for empty string instead of br tag (#17809)" (#18421)
This reverts commit 0ca74f4e7b40069719c77d8ffab0e56e5ef2b095.
--
wpt-commits: 464774c28a35d48ff5f8cd8eb1c8e089277bb77f
wpt-pr: 18421
Automatic update from web-platform-tests
Make status neutral return code 0 so that jobs stop failing
GitHub seems to have broken the feature where an action returning
status 78 is deemed neutral, so to stop it looking like everything
failed, use a success status instead (i.e. return code 0); this
can be reverted when GitHub fix their bug.
--
wpt-commits: 70682eca754225b5513dab1ba6148368de59f82c
wpt-pr: 18417
Automatic update from web-platform-tests
[LargestContentfulPaint] Re-enable untrusted scroll test
The test was disabled because it landed too close to the change which changed
the startTime to not be 0. After addressing that change, the test now passes.
Bug: 987915
Change-Id: Id19623083aa141f7c3b541ad490db6395add6f8c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1753082
Auto-Submit: Nicolás Peña Moreno <npm@chromium.org>
Reviewed-by: Yoav Weiss <yoavweiss@chromium.org>
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686787}
--
wpt-commits: 6c01d2da08c37e2e7b75e8ab7b983a8b2afb6f3a
wpt-pr: 18411
Automatic update from web-platform-tests
Fix DCHECK when compositing additive CSS transform animations
Previously CSSTransformNonInterpolableValue assumed that anything that was
composited on-top of would be single. However that is not true; in the simple
case where there is a replace animation before it, the replace effect will be a
pair:
target.animate({ transform: [ 'scale(1)', 'scale(2)' ] }, 1000);
target.animate({ transform: [ 'rotate(0)', 'rotate(90deg)' ] },
{ duration: 1000, composite: 'add' });
In the example above, the scale animation would not yet have been reduced to a
single interpolated value, so the DCHECK for is_single_ would fail. This CL
fixes the logic to perform an interpolation in that case.
Bug: 979952
Change-Id: I36a3221c55aa3d98281a21a4ac93d95d61c5a1ff
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1750200
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686789}
--
wpt-commits: eba08b270c0e767b21cc725355c840a71c1d4e11
wpt-pr: 18403
Automatic update from web-platform-tests
CSS: Shortest serialization for gap shorthand
gap is <'row-gap'> <'column-gap'>?
https://drafts.csswg.org/css-align-3/#propdef-gap
If row-gap and column-gap are the same, we serialize
only a single value, consistent with Firefox and
the shortest representation principle.
https://drafts.csswg.org/cssom/#serializing-css-values
Change-Id: I8a2380d963cdbb7f33676b435d9cfb909abf9e77
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1750521
Auto-Submit: Eric Willigers <ericwilligers@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686773}
--
wpt-commits: a06709fbf13b28f4b1b3d24f5bbc2e5274fe87af
wpt-pr: 18407
Automatic update from web-platform-tests
[WebNFC] Distinguish between NFC not available and not enabled
Following spec change at https://github.com/w3c/web-nfc/issues/237, this
CL allows web developers to distinguish when NFC is not available and
when it's disabled by user preference.
Bug: 520391
Change-Id: I3927d855edef1b1cf9b2036a0b4991745b962e04
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1751948
Commit-Queue: François Beaufort <beaufort.francois@gmail.com>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Reviewed-by: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com>
Cr-Commit-Position: refs/heads/master@{#686762}
--
wpt-commits: 33a1ccaeb68cb1c02498a320b94cf7fd20708869
wpt-pr: 18416
