Refactoring EventHandler: make it modular across different event types & across the scopes of its states |
|||||||||||
Issue descriptionThis is an issue to track all other issues regarding the refactoring of EventHandler and breaking it up into different classes.
,
Apr 14 2016
Thanks for filing the bug. We will want to separate out frame vs page states (crbug.com/449649) as well as by event type. Regarding the event-type based modularization, our immediate goal is to enable releasing implicitly captured touch pointer events w/o affecting existing TouchEvent capturing behavior. We will be driving TouchEvents through PointerEvents after making TE event handling a separate unit ( crbug.com/603567 ).
,
May 26 2016
,
May 26 2016
,
Jun 1 2016
,
Jun 2 2016
,
Jun 23 2016
,
Jun 23 2016
,
Jun 29 2016
,
Aug 29 2016
,
Oct 13 2016
|
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by nzolghadr@chromium.org
, Apr 14 2016