Skip to main content

Browse the archive

https://github.com/web-platform-tests/wpt
26 December 2018, 22:31:15 UTC
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 
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
1 parent f3cbe03
History
Tip revision: 1b5ce4ad3817e7b7247d7ff0f76b81877fce0d89 authored by Andrew Comminos on 21 December 2018, 21:45:26 UTC
Perform flexbox child hit testing by testing all children atomically
Tip revision: 1b5ce4a
File Mode Size
resources
META.yml -rw-r--r-- 111 bytes
idlharness.window.js -rw-r--r-- 285 bytes
iframe-unload.html -rw-r--r-- 1.1 KB
onvisibilitychange.html -rw-r--r-- 629 bytes
prerender_call.html -rw-r--r-- 836 bytes
test_attributes_exist.html -rw-r--r-- 729 bytes
test_child_document.html -rw-r--r-- 2.9 KB
test_default_view.html -rw-r--r-- 1.9 KB
test_minimize-manual.html -rw-r--r-- 7.9 KB
test_read_only.html -rw-r--r-- 1.2 KB
test_tab_state_change-manual.html -rw-r--r-- 7.8 KB
unload-1.html -rw-r--r-- 344 bytes
unload.html -rw-r--r-- 462 bytes
back to top