Bug 1550328 [wpt PR 16629] - Always use physical coordinates for visual rects, a...
commitd8db750e15fe957b7a2672b2974781cfb5347d95
authorXianzhu Wang <wangxianzhu@chromium.org>
Mon, 20 May 2019 12:59:36 +0000 (20 12:59 +0000)
committerJames Graham <james@hoppipolla.co.uk>
Wed, 5 Jun 2019 09:28:32 +0000 (5 10:28 +0100)
treea080c091f79b37dc03ca1ed934bf016bd5913f65
parent8f4b39504be0825deaae0c3204df26ca0f03fd70
Bug 1550328 [wpt PR 16629] - Always use physical coordinates for visual rects, a=testonly

Automatic update from web-platform-tests
Always use physical coordinates for visual rects

- Let MapToVisualRectInAncestorSpace() always treat the input rect as
  in pure physical coordinates. Previously the input was inconsistent:
  pure physical for boxes, and flipped for inlines.

- This makes it clear that all visual rects, regardless of their
  coordinates spaces, are in physical coordinates.

- This reduces unnecessary back and forth flipping in LayoutNG which
  is already using physical coordinates in inline layout.

Bug: 941228
Change-Id: I10e16c5e7833e94a615e4dd18aa3141512b8e9e3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1568619
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Reviewed-by: Stefan Zager <szager@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656051}

--

wpt-commits: 5e447de33a3c3c0de7cb96513e8318ca673f182e
wpt-pr: 16629
testing/web-platform/tests/intersection-observer/v2/drop-shadow-filter-vertical-rl.html [new file with mode: 0644]