[wpt-sync] Sync PR 12329 - [IntersectionObserver] Fix target rect calculation for LayoutInline.

RESOLVED FIXED in Firefox 63

Status

()

enhancement
P4
normal
RESOLVED FIXED
Last year
11 months ago

People

(Reporter: wptsync, Unassigned)

Tracking

unspecified
mozilla63
Points:
---

Firefox Tracking Flags

(firefox63 fixed)

Details

(Whiteboard: [wptsync downstream], )

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

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

Stefan Zager <szager@chromium.org> wrote:
>  [IntersectionObserver] Fix target rect calculation for LayoutInline.
>  
>  BUG=847623
>  R=chrishtr@chromium.org
>  
>  Change-Id: Ib8cefc856ecbeadfdeecabcf7f20b6d3b457db6a
>  Reviewed-on: https://chromium-review.googlesource.com/1164473
>  WPT-Export-Revision: 65db2ac534f22af2f9dc50279c728a8ebb2ed968
Component: web-platform-tests → Layout
Product: Testing → Core
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Ran 1 tests and 3 subtests
OK     : 1
PASS   : 3
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/083926fe16d3
[wpt PR 12329] - [IntersectionObserver] Fix target rect calculation for LayoutInline., a=testonly
Pushed by archaeopteryx@coole-files.de:
https://hg.mozilla.org/integration/mozilla-inbound/rev/076f7722d9b5
[wpt PR 12329] - [IntersectionObserver] Fix target rect calculation for LayoutInline: Set test as failing on OS X. r=bustage-fix
https://hg.mozilla.org/mozilla-central/rev/083926fe16d3
https://hg.mozilla.org/mozilla-central/rev/076f7722d9b5
Status: NEW → RESOLVED
Closed: 11 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
You need to log in before you can comment on or make changes to this bug.