Closed Bug 1823560 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 39099 - VT: Handle fragmented shared elements.

Categories

(Core :: CSS Parsing and Computation, task, P4)

Product:
Core
Component:
CSS Parsing and Computation
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
114 Branch
Tracking Flags:
Tracking Status
firefox114 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 39099 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/39099
Details from upstream follow.

Vladimir Levin <vmpstr@chromium.org> wrote:

VT: Handle fragmented shared elements.

This patch skips adding fragmented elements into the shared element
set. If an element becomes fragmented during the transition, then the
transition is skipped.

R=khushalsagar@chromium.org

Fixed: 1424806
Change-Id: I3e3a7305a75c16b06a53c891954a0961dcb2eedf
Reviewed-on: https://chromium-review.googlesource.com/4357275
WPT-Export-Revision: ba221d9a384cd75937e555adf61d7f1d45698a37

Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core

CI Results

Ran 9 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 2 tests

Status Summary

Firefox

TIMEOUT: 2

Chrome

FAIL : 1
TIMEOUT: 1

Safari

TIMEOUT: 2

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/867ba3718737 [wpt PR 39099] - VT: Handle fragmented shared elements., a=testonly https://hg.mozilla.org/integration/autoland/rev/24e4fec0e5ae [wpt PR 39099] - Update wpt metadata, a=testonly

https://hg.mozilla.org/mozilla-central/rev/867ba3718737
https://hg.mozilla.org/mozilla-central/rev/24e4fec0e5ae

Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox114: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 114 Branch
You need to log in before you can comment on or make changes to this bug.