Closed Bug 1555814 Opened 5 years ago Closed 5 years ago

[wpt-sync] Sync PR 17107 - Contents layer offset should be zero with ReplacedContentTransform

Categories

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

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

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla69
Tracking Flags:
Tracking Status
firefox69 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync upstream])

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

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

Xianzhu Wang <wangxianzhu@chromium.org> wrote:

Contents layer offset should be zero with ReplacedContentTransform

ReplacedContentTransform bakes the offset into it, so the contents
layer should have zero offset from transform node.

Bug: 967652
Change-Id: Iadfe3354286b9847acf41dd88822e40f73ccab64
Reviewed-on: https://chromium-review.googlesource.com/1636601
WPT-Export-Revision: 3077f81072f4dab53876c0ae4baefef97815ba26

Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core
Failed to get results from try push
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/568966d6dcc5
[wpt PR 17107] - Contents layer offset should be zero with ReplacedContentTransform, a=testonly

https://hg.mozilla.org/mozilla-central/rev/568966d6dcc5

Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox69: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla69
Whiteboard: [wptsync downstream] → [wptsync upstream]
You need to log in before you can comment on or make changes to this bug.