Hello, this is actually for android device and not ios, made a mistake wile filling out form for issue, however do not see a way to edit task description, could someone please edit or move issue to correct scope?

Tested the issue using #67.0.3396.87/70.0.3508.0 on Nexus 6P, 8.1.0; 70.0.3508.0 on Samsung Galaxy J7 as per the steps mentioned in original comment and could not reproduce the issue. No gap is an bottom of overlay on scrolling.

@Reporter: Is this issue consistently reproducible? Could you please let us know the details of your device for further triaging. This would help in better triaging.

Thanks!!

I'm also unable to repro the issue on M70. 

Hello, sorry for taking so long to get back to you, but I currently don't have access to said device to provide full details (will update on Monday). However it's pixel C tablet, and sadly but is not reproducible constantly. You need to got it in the right second for it to appear.

Ping, lina2991@. Are you able to provide more details? How often get you get this to trigger? I spent several minutes trying but couldn't.

Hi, I again have access to said device, so can try to provide as many details as I can. 

The device Im using to check is pixel C (8.1.0,), and today retested on canary to make sure it wasnt fixed with some other issue in the mean time, and still reproducible. Canary version - 70.0.3517.0.

We discovered this issue while developing a new feature for client - some new modals. Issue happens when a fixed position element is added to DOM (say overlay) and url bar is animating. So the same situation as in html I provided. In our actual project it appears more frequently, but I was unable to isolate why. My best guess - it just takes longer to get the result, so you can scroll longer. But you still need to get the correct timing. And as of few minutes ago all button bindings are also broken, they are where the element would be without the visual gap. 

My tips for reproducing - make sure bar is not visible before scroll. Click button, start scrolling up until overlay is added, then stop. And repeat until its broken. To get my first broken overlay it took me about half an hour, however when you figure out the timing - every other try breaks.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I managed to repro this once or twice, but in ~20 minutes of trying I still can't make it consistently repro. Given how hard it is to repro and the low severity I'm unlikely to get to it soon.