Revision 1b5ce4ad3817e7b7247d7ff0f76b81877fce0d89 authored by Andrew Comminos on 21 December 2018, 21:45:26 UTC, committed by Chromium WPT Sync on 21 December 2018, 21:45:26 UTC
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
1 parent f3cbe03
reflection-misc.html
<!doctype html>
<title>HTML5 reflection tests: miscellaneous elements</title>
<meta name=timeout content=long>
<p>Implementers looking to fix bugs might want to use the <a
href=reflection-original.html>original version</a> of this suite's test
framework, which conveniently aggregates similar errors and only reports
failures. This file is (part of) the authoritative conformance test suite, and
is suitable for incorporation into automated test suites.
<div id=log></div>
<script src="/resources/testharness.js"></script>
<script src=/resources/testharnessreport.js></script>
<script src=original-harness.js></script>
<script src=new-harness.js></script>
<script src=elements-misc.js></script>
<script src=reflection.js></script>
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...