Asynchronous immediate mode hit-test inquiry |
|||||||||
Issue descriptionThere may always exist areas that we wish to target events to that cannot be represented by the current HitTest component implementation. In this case, the event-targeting logic needs to ask the client (e.g. blink, UI) what should be the disposition of the event. Implement this fall-back handling.
,
Jun 29 2017
,
Aug 15 2017
,
Aug 15 2017
,
Aug 15 2017
,
Jan 9 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/08e1c97b0f84b6aa6caef59776d203ef39c901fd commit 08e1c97b0f84b6aa6caef59776d203ef39c901fd Author: Ria Jiang <riajiang@chromium.org> Date: Tue Jan 09 23:41:13 2018 Tell clients to do hit-testing with kHitTestAsk flag in HitTestQuery. When the target hit-test region has kHitTestAsk flag set, we need to fall back to do hit-testing on the client side. HitTestQuery returns an empty target with kHitTestAsk flag and clients will then ask to do async targeting. Bug: 732402 Test: viz_unittests Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel Change-Id: I16e17f4d4b7d84ecdefc09d289248115070190ec Reviewed-on: https://chromium-review.googlesource.com/811836 Reviewed-by: Robert Kroeger <rjkroege@chromium.org> Commit-Queue: Ria Jiang <riajiang@chromium.org> Cr-Commit-Position: refs/heads/master@{#528168} [modify] https://crrev.com/08e1c97b0f84b6aa6caef59776d203ef39c901fd/components/viz/host/hit_test/hit_test_query.cc [modify] https://crrev.com/08e1c97b0f84b6aa6caef59776d203ef39c901fd/components/viz/host/hit_test/hit_test_query_unittest.cc
,
Feb 26 2018
,
Apr 24 2018
Deprecating label Proj-Mustash-Mus-WS in favor of Components.
,
Aug 14
Bug scrub: Is this needed to ship mustash/mash?
,
Aug 15
This is a duplicate of a fixed bug. However: there is probably something that needs to be done for event targeting in separate process ash/browser. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by rjkroege@chromium.org
, Jun 12 2017Labels: event-targeting