New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 782405 link

Starred by 3 users

Issue metadata

Status: Archived
Owner: ----
Closed: Jan 18
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Task
Proj-VR
Proj-XR
Proj-XR-VR



Sign in to add a comment

Investigate how should event bubble/capture

Project Member Reported by bshe@chromium.org, Nov 7 2017

Issue description

Once we have composited elements (for example, Button element composited by a Rect, VectorIcon and InvisibleHitTarget elements), it is necessary to have a notion of event bubble/capture.

For instance, in the Button case, in order to position reticle correctly, we need to have an InvisibleHitTarget that is a child of VectorIcon(Button foreground) so that the reticle drew after VectorIcon. This also means all the events are sent to the InvisibleHitTarget instead of Button element (which might be a no hit testable element). But the logic which manages the button state (hover, press) must exist in Button element. So these events need to bubble up to Button element.

 
Project Member

Comment 1 by sheriffbot@chromium.org, Nov 8

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Pri-2 Pri-3
Status: Available (was: Untriaged)

Comment 4 by ddorwin@chromium.org, Jan 18 (4 days ago)

Labels: OS-Android

Comment 5 by samdrazin@chromium.org, Jan 18 (4 days ago)

Labels: -Type-Bug Type-Task
Status: Archived (was: Available)

Sign in to add a comment