Fix WebXR input with UAv2 |
||||
Issue descriptionIt looks like the user gesture token status is ignored, and it doesn't do much. Can it be removed? The only consumer is WebXR. (The comment is not helpful, since it just says "dummy leftover for compile test")
,
May 16 2018
,
May 16 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/47cf7037cbde6c278e987cde18da3ec8b7a86996 commit 47cf7037cbde6c278e987cde18da3ec8b7a86996 Author: Mustaq Ahmed <mustaq@google.com> Date: Wed May 16 18:24:03 2018 Fix user activation v2 trigger for a WebXR input. Bug: 843366 Change-Id: Ifa1d702a1357e4f508f708b5cf9783d0db90ad06 Reviewed-on: https://chromium-review.googlesource.com/1062009 Reviewed-by: Brandon Jones <bajones@chromium.org> Reviewed-by: David Bokan <bokan@chromium.org> Commit-Queue: Mustaq Ahmed <mustaq@chromium.org> Cr-Commit-Position: refs/heads/master@{#559190} [modify] https://crrev.com/47cf7037cbde6c278e987cde18da3ec8b7a86996/third_party/blink/renderer/core/frame/local_frame.h [modify] https://crrev.com/47cf7037cbde6c278e987cde18da3ec8b7a86996/third_party/blink/renderer/modules/xr/xr_session.cc
,
May 16 2018
,
Jul 4
|
||||
►
Sign in to add a comment |
||||
Comment 1 by mustaq@chromium.org
, May 16 2018Labels: UserActivation
Status: Started (was: Assigned)