viz hit test doesn't work when we have a window in between its sibling and that sibling's child |
||
Issue descriptione.g. +a----------------------+ | +b---------+ | | | | | | | | | | | | | | | +c-|------+ | | | |1 | | | | +----------+ | | | | 2 | | | | | | | +---------+ | +-----------------------+ a is the parent of b. c is a sibling of a; it's under b and above a. The hit-test data we have looks like: root a b c We can handle point 1 correctly because of z-order in hit-test data and we stop looking further after we found the target. However, for point 2, it's going to match window a instead of c - we go to a, then b (b doesn't contain it so we go back to a which contains it) and stops at a.
,
Nov 24 2017
Transient/modal windows are somewhat of an exception ... it'd be interesting to see a scenario where this happens.
,
Nov 24 2017
I'm not sure if it's possible in aura, but it's possible in blink (example [1] from flackr@) [1] http://jsbin.com/logoyit/edit?html,css,js,output
,
Nov 27 2017
Sadrul is right that we don't allow this in aura (or views).
,
Aug 15
I'm assuming this is only an issue if mash is using viz hit testing. Do I have that right?
,
Aug 16
yes. But mash must use viz hit testing if it's going to use OOP-D. |
||
►
Sign in to add a comment |
||
Comment 1 by sadrul@chromium.org
, Nov 24 2017