search

mozilla-mobile / firefox-ios

Firefox for iOS
Mozilla Public License 2.0
12.23k stars 2.94k forks source link

When the address bar is set to bottom, scrolling down the page doesn't react immediately #10268

Open ozeidan opened 2 years ago

ozeidan commented 2 years ago

Steps to reproduce

Configure the address bar to show on the bottom of the screen. Scroll down on a page (normally, by moving the page up with one finger).

Expected behavior

The page should start moving immediately. After some scrolled distance, the address bar should hide.

Actual behavior

The page only moves up after one has scrolled enough to fully hide the address bar. This delay is a bit annoying.

Device & build information

┆Issue is synchronized with this Jira Task

lmarceau commented 2 years ago

Thanks a lot for the feedback!

I tested and could reproduce, here's a video of the described issue. I scrolled at first slowly, then I scrolled fast to see the difference. So if you're a user wanting to scroll slow you would see this for sure.

https://user-images.githubusercontent.com/11338480/159276166-85196842-51bc-4131-aaee-0aedd0084ec9.MP4

pashynskykh commented 2 years ago

Any updates on this? It's already 5 months since this bug was reported.

github-actions[bot] commented 1 year ago

This issue has been automatically marked as stale. Has the issue been fixed, or does it still require the community's attention? Please leave any comment to keep this issue opened. It will be closed automatically if no further update occurs in the next 30 days. Thank you for your contributions!

struq commented 1 year ago

Not fixed yet in v115.0

pashynskykh commented 1 year ago

Yep, this bug is still not fixed. Can't imagine why it's still getting ignored, because it's very annoying. This bug is one of the reasons I've stopped using FF on mobile.

pashynskykh commented 1 year ago

Looks like this bug was fixed with v106.3 (33647)! Can anyone confirm this?

ozeidan commented 1 year ago

Yes it's fixed for me too in 116.2

github-actions[bot] commented 2 weeks ago

This issue has been automatically marked as stale. Has the issue been fixed, or does it still require the community's attention? Please leave any comment to keep this issue opened. It will be closed automatically if no further update occurs in the next 30 days. Thank you for your contributions!