Closed Bug 1516141 Opened 9 months ago Closed 8 months ago

[wpt-sync] Sync PR 14652 - Perform flexbox child hit testing by testing all children atomically

Categories

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

enhancement

Tracking

()

RESOLVED FIXED
mozilla67
Tracking Status
firefox67 --- fixed

People

(Reporter: wptsync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Andrew Comminos <acomminos@fb.com> wrote:
>  Perform flexbox child hit testing by testing all children atomically
>  
>  When two child elements of a flexbox overlap (for example, due to
>  negative margins), the element drawn in the foreground may not actually
>  capture the hit if the element underneath it is hit-tested in an earlier
>  phase (e.g. foreground before child block background), despite being
>  occluded. This is because painting of flexbox children is done
>  atomically (all phases at once). This change makes hit testing atomic as
>  well, in accordance with the spec [1].
>  
>  [1] https://www.w3.org/TR/css-flexbox-1/#painting
>  
>  Bug: 844505
>  Change-Id: Iceab80b42f19488dcb59565ea3c0ce40d48c483b
>  
>  Reviewed-on: https://chromium-review.googlesource.com/1388206
>  WPT-Export-Revision: 2eed18d128f0e1a535471df2a785fc13bdb7702e
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/c49c447610ee
[wpt PR 14652] - Perform flexbox child hit testing by testing all children atomically, a=testonly
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/37083c63895a
[wpt PR 14652] - Perform flexbox child hit testing by testing all children atomically, a=testonly
Status: NEW → RESOLVED
Closed: 8 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
You need to log in before you can comment on or make changes to this bug.