Scroll jumps after slide, or otherwise tap point offsets |
|||||||||
Issue descriptionChrome Version: 66.0.3359.158 OS: Android 8.1.0 Device: Google Nexus 5X * Did not repro on Chrome 67.0.3396.68 on Android 8.0.0 / Samsung Galaxy S8. What steps will reproduce the problem? (You need a valid account of Express Yoyaku by JR East to try this.) (1) Go to login page at https://shinkansen1.jr-central.co.jp/RSV_P/S_index.html Note: You can alternatively 1. go to https://expy.jp/ and then 2. find and tap the 2nd "ログイン (login)" button beneath "EX会員ログイン". (2) Log in to the service with a valid ID and password of that site. (3) Tap "予約" (4) Scroll down by sliding. Try to tap some buttons. What is the expected result? Scroll stops and the view stays there after slide. Buttons can be tapped normally. What happens instead? A. Scroll sometimes jumps back to the top after slide, or while sliding. B. When (A) didn't happen, any tap after that will be recognized to a wrong position. (up by ~3cm) See the attached movie.
,
Jun 12 2018
yamaguchi@ -- Thanks for reporting this issue. After step-1, i.e. after navigating to the URL - https://shinkansen1.jr-central.co.jp/RSV_P/S_index.html, we are unable to find the option "予約". Attached is the screenshot for reference. Could you please help us in finding the option mentioned by you in step-2 or please share the URL where the issue can be reproduced directly. You can also, verify its behavior in FireFox mobile browser as well to verify whether the issue is related to Chrome specific or site issue. Thanks in advance!
,
Jun 12 2018
,
Jun 12 2018
I think the description was misleading. Revised the description now to be clearer. https://shinkansen1.jr-central.co.jp/RSV_P/S_index.html is the login page where you should enter ID and password of this service. Also I noticed that accounts of this service cannot be issued online but need to be processed by the credit card vendor with which you use the service by subscription. So it might be difficult to try. I have tried with Firefox. I sometimes see scroll discontinuity like in the attached movie (as if DOM elements were modified in the middle) but tap points always matches with the visual (not covered by the movie clip).
,
Jun 12 2018
,
Jun 13 2018
yamaguchi@ -- Thanks for the reply. Yes, we can't register online to login to page and proceed further to the page where the issue is observed. Requesting dev team to kindly look into this issue. Thanks!
,
Jun 13 2018
I cannot access the page so I cannot repro either. If I understand it correctly, according to the report the issue is already fixed in M67 so I don't think we need to take any actions here. Closing as Wontfix. Feel free to re-open if there is a better repro available.
,
Jun 14 2018
I confirmed this still happening on Nexus 5X / Chrome 67.0.3396.87. So this would more likely be dependent on either - Android version (8.1.0) - or the device (Nexus 5X)
,
Jun 14 2018
The bug is not reproducible on Samsung Galaxy S8 but is reproducible on Nexus 5X. Doesn't sound like a compositing issue as the page is composted on both devices. Could you please try to provide a minimal repro case based on the website? It's hard to fix/triage without access to the bug page.
,
Jun 14 2018
It's difficult for me because this could not be reproduced on the developer tool (on Linux Chrome) just by changing layout. It'd be helpful if someone who has dev device can help to investigate further.
,
Jun 18 2018
yamaguchi@, you mention the tap points are off, this sounds a lot like issue 848122 - is that the same issue?
,
Jun 20 2018
Now I tried with Chrome 67.0.3396.87 on Nexus 5X / Android 8.1.0 It no longer reproduces on that version. Instead the site renders leaving some space on the right side. (See screenshot. I am not sure if this is intended or the site's issue.) Anyways I think this Issue was likely happening around 67.0.3396.68 or before, but not anymore. I haven't confirmed if there's any element which is position:fixed and touch-action:none. However the both issue seems resolved at almost the same time; I saw Issue 848122 resolved on 67.0.3396.87 (Nexus 5X and Samsung S8). Closing as WontFix because it's not reproducible anymore. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by yamaguchi@chromium.org
, Jun 11 2018