Closed Bug 1550187 Opened 5 years ago Closed 5 years ago

[wpt-sync] Sync PR 16397 - Revert "Test offsetLeft/offsetTop of multi-line inline elements"

Categories

(Testing :: web-platform-tests, defect, P4)

defect

Tracking

(firefox69 fixed)

RESOLVED FIXED
mozilla69
Tracking Status
firefox69 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Xianzhu Wang <wangxianzhu@chromium.org> wrote:

Revert "Test offsetLeft/offsetTop of multi-line inline elements"

This reverts commit 07b1529d17138ce3b6441394d451e1d7d3cbe841.

We need to think more about the expected behavior.

Original change's description:

Test offsetLeft/offsetTop of multi-line inline elements

Bug: 953572
Change-Id: If3160a817ad784ea7c48f8f5ed7717f6de1bbff3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1570474
Auto-Submit: Xianzhu Wang \<wangxianzhu@chromium.org>
Commit-Queue: Koji Ishii \<kojii@chromium.org>
Reviewed-by: Koji Ishii \<kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#651616}

TBR=wangxianzhu@chromium.org,kojii@chromium.org

Change-Id: Id017a3a0d7c8a4197d30c85fa7220e6e8ea8f160
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 953572
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1572858
Reviewed-by: Xianzhu Wang \<wangxianzhu@chromium.org>
Commit-Queue: Xianzhu Wang \<wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#651876}

PR 16397 applied with additional changes from upstream: a1694d857ee5cab66a382ce97380cd0b122da624
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/f3e422b064fd
[wpt PR 16397] - Revert "Test offsetLeft/offsetTop of multi-line inline elements", a=testonly
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla69
You need to log in before you can comment on or make changes to this bug.