1291444 - Broken scrolling at http://news.google.com/

Status: RESOLVED INCOMPLETE

(Firefox for Android Graveyard :: Toolbar, defect, P5)

Description

[Mike Taylor [:miketaylr]]

STR)

1) go to http://news.google.com/
2) scroll down a few swipes
3) scroll up a few swipes

At some point, scrolling will get stuck. I can't go up or down, but a side-swipe will navigate to a different section.

Comment 1

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

What version of Fennec are you using? I'm not able to repro on Nightly.

Comment 2

[Mike Taylor [:miketaylr]]

Hey Kats, I was testing on 48 on a Galaxy S6. And yeah, it doesn't repro in Nightly (should have checked there too...), but the scroll lags pretty badly.

Comment 3

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

Ok, I can repro on 48, but not on 49 (Aurora Aug 1 build) or 51 (Aug 03 build). So it seems to only affect 48? And as that's on release already it's unlikely we'll fix it unless we do a dot release.

Also problematic is that the site is managing all the scrolling itself - it's not APZ scrolling but JS scrolling. So even if there's something we're doing that's wrong it's not going to be easy to track down.

I don't think there's anything actionable here so closing WFM but feel free to reopen if you disagree.

Comment 4

[Mike Taylor [:miketaylr]]

NO, I think that's the right resolution. I just tested with layout.css.prefixes.webkit=false and the problem as reported reproduces in Nightly... but that layout.css.prefixes.webkit=true will ride the trains in 49. If I had to guess, it would be a missing `webkitTransitionEnd` event.

Comment 5

[Mike Taylor [:miketaylr]]

> will ride the trains in 49

s/ride the trains/hit release/

Comment 6

[Mike Taylor [:miketaylr]]

(ugh, wrong field)

Comment 7

[bull500]

Attachment: googlenewscomp.png

Im getting two different versions of the site on Beta vs Nightly 51  
On Nightly i get the carousel version & AMP enabled news results with the problematic scrolling   
The site which i get on Beta doesn't seems to have the content when a side swipe is done but side swipe reveals more contentt on the Nightly version of the site
also layout.css.prefixes.webkit=true - on nightly 51 as default   

Another issue is click change edition on nightly via google news hamburger button. There is no popup to select different countries, im stuck. Only "close" button works.    

Just curious even if its JS scrolling why does it have to be soo bad?

Comment 8

[Randall Barker [:rbarker]]

I'm not sure there is much that can be done here. It looks like Google may be A/B test this. :snorp and I got different pages. On my device scrolling was clearing being done with JS while on his device it was using APZ. I was able to change editions. It appears that the js maybe running very slowly as it took several taps to get the edition selection pop-up to show.

Comment 9

[bull500]

(In reply to Randall Barker [:rbarker] from comment #8)
> I'm not sure there is much that can be done here. It looks like Google may
> be A/B test this. :snorp and I got different pages. On my device scrolling
> was clearing being done with JS while on his device it was using APZ. I was
> able to change editions. It appears that the js maybe running very slowly as
> it took several taps to get the edition selection pop-up to show.

yup! the change edition started working after yesterday's build on the AMP enabled version; maybe due to this Bug 1290823  
For fun i spoofed the Firefox android UA on the desktop Nightly and the site is un-scrollable  

Cant a testcase site with a JS scroll implementation be used and probably we can compare performance over other browsers and develop over it?   

Dont know if it will help but searching the internet i stumbled on this - https://developers.google.com/web/updates/2016/06/passive-event-listeners?hl=en

Comment 10

[Karl Dubost💡 :karlcow]

The version sent to Chrome UA on Gecko is working (and has a different layout, which is less fancy)

In https://cdn.ampproject.org/viewer/google/v5.js
There is a lot of code related to scrolling and touch.

Comment 11

[Thomas Wisniewski]

If changing the UA works, this may be a good candidate for an override.

Comment 12

[Karl Dubost💡 :karlcow]

This issue was about the scrolling. The scrolling in my latest tests seems fine. 
I seem also to receive the same version on all browsers. 

The design on the left posted by bull500
https://bug1291444.bmoattachments.org/attachment.cgi?id=8777866

seems to be a kind of A/B testing with AMP news, but I can't reproduce.

Comment 13

[bull500]

Attachment: scrollprob.mp4

(In reply to Karl Dubost :karlcow from comment #12)
> This issue was about the scrolling. The scrolling in my latest tests seems
> fine. 
> I seem also to receive the same version on all browsers. 
> 
> The design on the left posted by bull500
> https://bug1291444.bmoattachments.org/attachment.cgi?id=8777866
> 
> seems to be a kind of A/B testing with AMP news, but I can't reproduce.

The video shows the problem  
First is chrome, next is Nightly and final is Nightly with a spoofed UA.  

Its a different site for Firefox UA even though its the same URL

Comment 14

[Karl Dubost💡 :karlcow]

Thanks bull500.
So definitely we do not receive the same version (even when I explicitly put the Indian version). I'm receiving the same version than Chrome. And the scroll is blazing fast. There is also no other pages when sliding on the right side.  :/

Comment 15

[bull500]

My guess is they are sniffing the location of the user and the forwarding the content specific to google India's or other region specific google sites; with no escape other than spoofing UA.  

Even if i change to the US edition it still serves me the problematic site(scrolling to the right side one).

Comment 16

[Emma Humphries ☕️🎸🧞‍♀️✨ (she/they) [:emceeaich] (Pacific Time) use needinfo]

This is an assigned P1 bug without activity in two weeks. 

If you intend to continue working on this bug for the current release/iteration/sprint, remove the 'stale-bug' keyword.

Otherwise we'll reset the priority of the bug back to '--' on Monday, August 28th.

Comment 17

[Firefox Bug Husbandry Bot]

Re-triaging per https://bugzilla.mozilla.org/show_bug.cgi?id=1473195

Needinfo :susheel if you think this bug should be re-triaged.

Comment 18

[miralobontiu]

Attachment: 2019_02_27_10_48_17_Trim.mp4

Hi,

I encountered this issue on the latest Nightly 67.0a1 (2019-02-26) with Nexus 6P (Android 8.1.0), and Samsung Galaxy Tab S3 (Android 8.0).
Reproducible on Release 65.0.1, Beta 66.0b11, and Reference Browser.
Not reproducible on Focus.
Please see the attached video and logcat.

Thank you!

Comment 19

[miralobontiu]

Attachment: logcat27.02.2019.txt

Comment 20

[Randall Barker [:rbarker]]

From the video it looks like the page never finishes loading. I don't think this is the same issue.

Comment 21

[BMO Automation]

We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.