Issue metadata
Sign in to add a comment
|
Horizontal scrollbar shows up in the wrong location on Android |
||||||||||||||||||||||
Issue descriptionChrome Version: 60.0.3089.0 OS: Android What steps will reproduce the problem? (1) Go to "about:flags" and enable "Chrome Home for Android" (2) Visit any long page, this works: https://news.ycombinator.com/item?id=14290358 (3) Pinch+zoom just a little so you get a horizontal scrollbar. (4) Scroll to the bottom of the screen so the url bar hides. (5) Scroll up just a little so the url bar re-appears. What is the expected result? The horizontal scrollbar should appear directly above the url bar. What happens instead? The horizontal scrollbar is floating too high (see screenshot). Is it possible to get a bisect of this without doing the bisect manually?
,
May 8 2017
,
May 8 2017
,
May 9 2017
This looks recent as I had to update my Canary to see it. It also seems like the horizontal scrollbar offsetting logic isn't working correctly while sliding the URL bar in - while its coming in, it overlays the scrollbar. Assigning to ktam@ for triage.
,
May 10 2017
,
May 11 2017
Note: 1) Good Build: 60.0.3080.0 Bad Build: 60.0.3081.0 2) Bisect Range: https://chromium.googlesource.com/chromium/src/+log/60.0.3080.0..60.0.3081.0?pretty=fuller&n=10000 3) Please find logs and video taken on Moto G4 Plus(athene_f)/7.0.0 @ http://go/chrome-androidlogs1/6/719714 4) Culprit: https://chromium.googlesource.com/chromium/src/+/23d381fd827c8880b85fe5794627e98af07454cc
,
May 11 2017
Thanks! Ouch, egg on my face. https://chromium.googlesource.com/chromium/src/+/23d381fd827c8880b85fe5794627e98af07454cc
,
May 15 2017
,
May 16 2017
Wooohooooooo! This was fixed by https://chromium.googlesource.com/chromium/src/+/80ecb98035a6654fff02e86877be39f51fcc3d54 I synced to before this patch, verified the bug, then synced past this patch and verified the bug hath been squashed.
,
May 16 2017
Although we don't have a test for specifically for this, the assert added in https://chromium.googlesource.com/chromium/src/+/b4d70c2b28f321a94a52615c95692b6da8738783 will catch anyone making this mistake again.
,
May 22 2017
The NextAction date has arrived: 2017-05-22
,
May 22 2017
This issue is now not reproducible on latest M60-60.0.3107.0, hence verifying. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by schenney@chromium.org
, May 8 2017NextAction: 2017-05-22
Status: Unconfirmed (was: Untriaged)