Issue metadata
Sign in to add a comment
|
Fling scrolling is not working |
||||||||||||||||||||||||||||
Issue descriptionChrome Version: 66.0.3336.0 OS: Android N, O Device: Galaxy S8+, Pixel 2 XL What steps will reproduce the problem? (1) Go to any page with vertical content that would require scrolling to view. (2) Enter Chrome VR (3) Use controller to scroll up and down the page using a fling motion. What is the expected result? The page uses fling scrolling. It keeps scrolling after your finger has left the touch pad or stops moving. What happens instead? As soon as your finger leaves the touch pad, the scrolling stops.
,
Feb 2 2018
Known issue with fallback UI path, Amir is working on it.
,
Feb 2 2018
Cool, another note for my own reference is that clicking is not working either in the right-hand section of the page.
,
Feb 2 2018
Clicking on the right-had section doesn't work?! Can you file a separate bug for that please? That's totally unexpected.
,
Feb 9 2018
Disregard comment 3, that was meant for another bug with a specific url.
,
Feb 14 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/8490926a774125c8edfed2b1992b22b00dec4212 commit 8490926a774125c8edfed2b1992b22b00dec4212 Author: Amirhossein Simjour <asimjour@chromium.org> Date: Wed Feb 14 20:58:07 2018 VR: send scroll to the correct target Scroll should be sent to the target that was under the pointer. Also fixed the target point for scroll end. BUG= 808512 , 808492 Change-Id: Ia24322bc56782f23c90ab19899b636ca21a520ff Reviewed-on: https://chromium-review.googlesource.com/919548 Reviewed-by: Michael Thiessen <mthiesse@chromium.org> Commit-Queue: Amirhossein Simjour <asimjour@chromium.org> Cr-Commit-Position: refs/heads/master@{#536812} [modify] https://crrev.com/8490926a774125c8edfed2b1992b22b00dec4212/chrome/browser/android/vr_shell/android_ui_gesture_target.cc
,
Feb 28 2018
,
Mar 1 2018
Verified with build 66.0.3356.0 canary. |
|||||||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||||||
Comment 1 by dbbrooks@chromium.org
, Feb 2 2018