DocumentUserGestureToken adds no value to UserGestureToken |
|||
Issue descriptionCurrent design is not clean: - The DocumentUserGestureToken/UserGestureToken split we currently have looks unnecessary because UGT cannot be instantiated directly. - DocumentUserGestureToken is a misnomer because it is only loosely tied with a Document object. - Current UserGestureIndicator & UserGestureToken are in platform/ but they are only used in core/ & web/. We need to clean these up before we add frame level user activation bits as an alternate implementation, see the blocked bug.
,
May 29 2017
,
Nov 1 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by bugdroid1@chromium.org
, May 29 2017