1062245 - The Navigation bar isn't sliding in smoothly and overhangs the content on the top of the page

Status: RESOLVED WORKSFORME

(Firefox for Android Graveyard :: General, defect)

Description

[Jan Henning [:JanH]]

Attachment: Navigation bar FF31.png

Steps to reproduce:
1. Go to a web site which requires scrolling.
2. Scroll down a bit, then start scrolling slowly upwards.
3. Observe what happens when the navigation bar appears.
4. Continue scrolling until you hit the top of the page.

What happens:
When scrolling upwards, at first the web site you're looking at is moving. Once the navigation bar decides to appear, the web site stops moving, instead only the navigation bar is sliding in. Only once the navigation bar is fully extended does the web site start moving again in response to your scrolling.
Finally, when reaching the top of the page, the navigation bar overhangs the top of the page, blocking the content there (compare attached screenshots). This means you can't click any links there without some careful touch screen manipulation in order to hide the navigation bar without scrolling the whole page downwards.

What should have happened:
The behaviour of FF31 and previous versions:
- While the navigation bar is sliding in, the scrolling movement of the website itself continues smoothly.
- When you scroll all the way to the top, the navigation bar appears above the actual web site content.

Other infos:
Tested with both FF32 and the current nightly.
My device: Samsung Galaxy S3 Mini, Android 4.1.2

Comment 1

[Jan Henning [:JanH]]

Attachment: Navigation bar FF32.png

Comment 2

[Jan Henning [:JanH]]

Attachment: Navigation bar FF31.png

Oops, looks like I've accidentally switched the file names.

Comment 3

[Jan Henning [:JanH]]

Attachment: Navigation bar FF32.png

Comment 4

[Aaron Train [:aaronmt]]

Some of this I interpret as bug 1046017, but we should figure out what is a problem and or what is working as intended.

Comment 5

[Jan Henning [:JanH]]

In today's nightly, things are working again as they used to, so maybe it really is related to bug 1046017.

Comment 6

[Aaron Train [:aaronmt]]

Interesting. Thanks for checking.