Closed Bug 1788844 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 35759 - Check property equality for object-view-box by value

Categories

(Core :: Layout: Images, Video, and HTML Frames, task, P4)

Product:
Core
Component:
Layout: Images, Video, and HTML Frames
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
106 Branch
Tracking Flags:
Tracking Status
firefox106 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(Depends on 1 open bug,
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Anders Hartvoll Ruud <andruud@chromium.org> wrote:

Check property equality for object-view-box by value

Otherwise the transitions code will try to "retarget" in incorrect
ways.

Fixed: 1358920
Change-Id: I1378621468ceff08c8864bd170ba625e4de66aaf
Reviewed-on: https://chromium-review.googlesource.com/3868738
WPT-Export-Revision: f7d5762e6bec1e2470bc087f7ae7aa461f2a49c5

Component: web-platform-tests → Layout: Images, Video, and HTML Frames
Product: Testing → Core

CI Results

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

Total 1 tests and 1 subtests

Status Summary

Firefox

OK : 1
FAIL: 1

Chrome

OK : 1
FAIL: 1

Safari

OK : 1
FAIL: 1

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/a6a7a4b8816f [wpt PR 35759] - Check property equality for object-view-box by value, a=testonly https://hg.mozilla.org/integration/autoland/rev/294354e67b99 [wpt PR 35759] - Update wpt metadata, a=testonly

https://hg.mozilla.org/mozilla-central/rev/a6a7a4b8816f
https://hg.mozilla.org/mozilla-central/rev/294354e67b99

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