Issue metadata
Sign in to add a comment
|
misplaced hitbox/appearance of {fixed: bottom;} element
Reported by
sawahata...@artspark.co.jp,
Jun 19 2018
|
||||||||||||||||||||||||
Issue descriptionSteps to reproduce the problem: 1. open https://rawgit.com/knee-cola/f3912c3fd6c0d5b35708240c037dbfd4/raw/05d9d454c6e4405a0a6635e91ec6cdf994508894/chrome-mobile-footer-bug.html on android chrome. 2. scroll down (swipe up) 2 (or more) times. 3. tap the footer button. -> it doesn't react 4. tap 50～100px above of the footer button => it reacts. What is the expected behavior? What went wrong? `window.addEventListener("scroll", e => console.log(innerHeight, visualViewport.height));` show values that differed by the address bar (tab bar) height. Did this work before? Yes 66 Chrome version: 67.0.3396.87 Channel: stable OS Version: 5 - 8 Flash Version: for more detail. (the writer is not me) https://stackoverflow.com/questions/50723672/footer-buttons-links-become-unresponsive-on-mobile-chrome-v67-0-3396-68-on-andr
,
Jun 22 2018
same behavior as 854108, 855274
,
Jun 25 2018
Same issue! I spent one day to find out this is not caused by the UI library which imported to my Vue project. https://ansonhorse.github.io/vant-touch-skewing/src/plain.html I tested v67.0.3396.68 and v67.0.3396.68, these two meet this issue, and v58.0.3029.83 works fine. And, any goods news about this issue?
,
Jun 26 2018
Tested the issue in Android and able to reproduce the issue. Steps Followed: 1. Launch Chrome. 2. Navigate to https://rawgit.com/knee-cola/f3912c3fd6c0d5b35708240c037dbfd4/raw/05d9d454c6e4405a0a6635e91ec6cdf994508894/chrome-mobile-footer-bug.html 3. Scroll down to the bottom of the page t. 5. Scroll a little bit, so that the address box is displayed. 6. Try scrolling down again so the grey patch is displayed indicating end of page and address bar is hidden. 7. Tap on buttons 8. Observed that buttons are not clickable. Chrome versions tested: 67.0.3396.87(Stable), 69.0.3472.0(Canary) OS: Android 8.1.0 Android Devices: Pixel 2 Manual bisect results, Good Build - 67.0.3377.0 (544610) Bad Build - 67.0.3378.0 (544931) You are looking for a change made after 544810(GOOD), but before 544811(BAD). https://chromium.googlesource.com/chromium/src/+/6a6a41a3525c5844d8f26d0a65d099522a85516c Using per-revision bisect , the changelog which we got seems to be unrelated.so, will try to re-bisect and update accordingly. Thanks!
,
Jun 29 2018
Please re bisect, the suspect doesn't seem to be the actual culprit.
,
Jul 10
I checked just now reproduce on Stable(67) Beta(68) Dev(69.0.3475.0) fixed on Canary (69.0.3486.0)
,
Jul 12
As per comment 6, tried to re bisect this. Using per-revision bisect , the changelog which we got seems to be unrelated. https://chromium.googlesource.com/chromium/src/+/018b457108b049d89a9af894f597307211eee487 As per comment7, this issue seems to be fixed on canary and found similar issue Issue 848122 which has fix on canary but not yet merged to beta.So cc'ing @sahel to look into this issue. @sahel: Could you please look into this issue.If this is not with respective to your change please help in assigning to the owner. Thanks!
,
Jul 12
,
Jul 12
I confirm the fix on Canary, and it is merged to M68. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by pnangunoori@chromium.org
, Jun 20 2018