Hit tests of preserve-3d content hit obscured elements
Reported by
mara...@microsoft.com,
Apr 3 2018
|
|||||
Issue descriptionChrome Version: 65.0.3325.181 (Official Build) (64-bit) (cohort: Stable) OS: Win10 1803 (17118.1001) What steps will reproduce the problem? (1) https://jsfiddle.net/v3mnn4tt/ (2) Click on the top left corner of the element What is the expected result? Parent is hit, since it is on top of the child What happens instead? Child is hit, despite being obscured Works as expected in Edge and Firefox.
,
Apr 6 2018
hm, I don't think this type of hit-testing logic lives in the compositor. adding some people who can correct me and changing back to Blink>HitTesting for now.
,
Apr 13 2018
+ the compositor hit test folks
,
Apr 13 2018
reveman@ is right that we don't do this type of hit-testing in the compositor. Events would be targeted to the main frame and then blink should do its own hit-testing to decide which div to send the event to.
,
Apr 16 2018
Thanks for the info everyone. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by schenney@chromium.org
, Apr 3 2018