New issue
Advanced search Search tips

Issue 854108 link

Starred by 1 user

Issue metadata

Status: Unconfirmed
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Bottom scroll indicator blocks taps on anything underneath

Reported by rile...@gmail.com, Jun 19 2018

Issue description

Steps to reproduce the problem:
1. Search anything on google from mobile 
2. Scroll to bottom
3. When bottom is reached scroll a bit up (until address bar is shown) and a bit down in same movement until that grey indicator at the bottom is shown
4. unable to tap on privacy

What is the expected behavior?

What went wrong?
When that bottom scroll indicator is shown anything underneath is untapable.

Did this work before? Yes 

Chrome version: 67.0.3396.87  Channel: stable
OS Version: Android 7.0
Flash Version: 

This happens on all sites that have something to click on the bottom of the page i.e. https://eurovilla.hr/en/search/buy-apartment/
Sometimes it works
 
Labels: Needs-triage-Mobile

Comment 2 by rile...@gmail.com, Jun 20 2018

The problem is also that address bar doesn't hide on consecutive scroll without stopping. Address bar only hides when first scroll down is stopped
Cc: mthiesse@chromium.org sahel@chromium.org pnangunoori@chromium.org beccahughes@chromium.org
Components: UI>Input>Touch
Labels: M-68 RegressedIn-67 FoundIn-67 M-67 M-69 Triaged-Mobile Target-68 Target-69 FoundIn-69 FoundIn-68 hasbisect
Status: Untriaged (was: Unconfirmed)
Tested the issue in Android and able to reproduce the issue. 

Steps Followed:
1. Launch Chrome.
2. Navigate to any URL - www.google.com
3. Search for any query.
4. Scroll down to the bottom of the page.
5. Scroll a little bit, so that the omni box is displayed.
6. Try scrolling down again so the grey patch is displayed indicating end of page.
7. Tap on "Privacy" or "Terms" link.
8. Observed that links are not tappable.

Chrome versions tested:
67.0.3396.87(Stable), 69.0.3465.0(Canary)

OS:
Android 8.1.0

Android Devices:
Pixel 2

Using the per-revision bisect providing the bisect results,
Good Build - 67.0.3382.0 (546346)
Bad Build - 67.0.3383.0 (546671)

You are looking for a change made after 493382(GOOD), but before 493383(BAD).

When tried to take per-revision bisect, every time it gave different results all the time. Suspecting CL's from the list are as below:

> https://chromium.googlesource.com/chromium/src/+/1ab1d0aded63efb945743a21531a2401fb090638
> https://chromium.googlesource.com/chromium/src/+/46259cc58e11f12ca3308b694c59a14b195fc703
> https://chromium.googlesource.com/chromium/src/+/0cc53890a252923a6ae35f968b998f8d1cf13d0a

mthiesse@/ sahel@/ beccahughes@ -- Could you please take a look into this issue. Please assign to the related dev if they are not related to your changes.

Please navigate to below link for log's and video--
go/chrome-androidlogs/854108

Thanks!

Comment 4 by sahel@chromium.org, Jun 20 2018

https://chromium.googlesource.com/chromium/src/+/46259cc58e11f12ca3308b694c59a14b195fc703 is about autoscroll browser side fling which affects Windows and Mac. It is very unlikely that the cl causes a regression on Android
https://chromium.googlesource.com/chromium/src/+/1ab1d0aded63efb945743a21531a2401fb090638 is definitely not the cause.

I think none of the CLs you linked to are likely to be the cause. Is this a flaky failure? The bisect doesn't appear to be working.
Cc: ligim...@chromium.org
Labels: -hasbisect Needs-Bisect
Status: Unconfirmed (was: Untriaged)
Praphulla, can you please try a bisect again.

Sign in to add a comment