984965 - Laggy scrolling for overflow: auto content

Status: RESOLVED FIXED

(Firefox for Android Graveyard :: Toolbar, defect)

Description

[mozilla]

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1895.0 Safari/537.36

Steps to reproduce:

Scrolling lags on overflow: auto content 

Go to http://hn.premii.com/ on android firefox.



Actual results:

Scrolling is not smooth


Expected results:

Smooth Scrolling. 
 Same works on android browser on Android, Chrome on Android, Safari on iOS, IE on WP10.

Comment 1

[Aaron Train [:aaronmt]]

Which device, Firefox version, Android version are you using?

Comment 2

[mozilla]

Galaxy S3 - SGH-I747 - Android 4.3.1
Nexus 4 - Android 4.4.2

UserAgent on both
mozilla/5.0 (android; mobile; rv:28.0) gecko/28.0 firefox/28.0

Comment 3

[Aaron Train [:aaronmt]]

Hm, the site doesn't want to complete loading for me. I just see a spinner and loading text.

If you can still load the site it would be good to check Nightly (http://nightly.mozilla.org) to see if the issue is still present on Firefox 31.

Comment 4

[mozilla]

Site is working for me. 

I downloaded latest nightly and it is worse compare to beta and v28. On nightly, not only scrolling is bad but it tears the rendering after scroll. I can see rendering tiles .

Comment 5

[Aaron Train [:aaronmt]]

(In reply to mozilla from comment #4)
> Site is working for me. 
> 
> I downloaded latest nightly and it is worse compare to beta and v28. On
> nightly, not only scrolling is bad but it tears the rendering after scroll.
> I can see rendering tiles .

Sorry about that, that would be bug 983208 which we hope to fix very soon.

Comment 6

[Kartikaya Gupta (email:[e-mail])]

It seems to scroll smoothly enough for me on a Nexus 4 device. Is the scrolling significantly worse compared to regular pages for you? Or is it just slightly worse? We do use synchronous scrolling for scrollable subdocuments (such as overflow:auto) so slightly worse scrolling is expected in this case. This will be fixed once we switch Fennec over to using the C++ APZC code (bug 776030). You can also mitigate this problem by making the scrollable content the body of your document, and making the topbar position:fixed. I didn't look at the layout of the page in detail to see if this would break other things, but from a quick glance it looked like it should work.

Comment 7

[jwms]

May I suggest a demo page?  Comparing Fennec to Chrome on Android I can get to the bottom in one fling on Chrome and the least flings for Fennec is 5 for me.

http://www.html5rocks.com/static/demos/scrolling/demo.html

Comment 8

[Kartikaya Gupta (email:[e-mail])]

Fixed with APZ scrolling - both the URLs in comment 0 and comment 7 seem to scroll well for me in 48.