Closed
Bug 1470299
Opened 6 years ago
Closed 6 years ago
In Nexus 4 API 23, m.yelp.de progress stuck at 25%
Categories
(GeckoView :: General, defect, P1)
GeckoView
General
Tracking
(Performance Impact:high, firefox-esr52 wontfix, firefox-esr60 wontfix, firefox61 wontfix, firefox62+ fixed, firefox63 fixed)
People
(Reporter: njpark, Assigned: esawin)
References
Details
(Whiteboard: [geckoview:klar:p1])
On latest klar geckoview, going to m.yelp.com on Nexus 4 5.1 device causes the site to continuously reload. This is different from previous behavior, where the progressbar was not completing/disappearing.
Comment 1•6 years ago
|
||
No-Jun says the site loads correctly on his Pixel 2. The site loads correctly for me on my Moto G5 Plus.
It sounds like this is a recent regression.
status-firefox62:
--- → affected
Priority: -- → P1
Updated•6 years ago
|
Keywords: regression
Reporter | ||
Updated•6 years ago
|
Whiteboard: [geckoview] [qf:p1]
Reporter | ||
Comment 2•6 years ago
|
||
On today's Klar Geckoview, instead of reloading, it exhibits https://bugzilla.mozilla.org/show_bug.cgi?id=1454477#c3 (progressbar stuck at 25%)
Comment 3•6 years ago
|
||
Chris, are we shipping Klar/Geckoview in 62 or 63?
Flags: needinfo?(cpeterson)
Looks like the plan as of June 20 is to ship in 62.
status-firefox63:
--- → ?
tracking-firefox62:
--- → +
Comment 5•6 years ago
|
||
(In reply to Liz Henry (:lizzard) (needinfo? me) from comment #4)
> Looks like the plan as of June 20 is to ship in 62.
Yes. We're aiming to ship GeckoView 62 in Focus (7.0 in September). We'll find an owner for this P1 bug in GeckoView triage tomorrow.
Flags: needinfo?(cpeterson)
Updated•6 years ago
|
Assignee: nobody → esawin
Summary: In Nexus 4 API 23, m.yelp.de site is loaded repeatedly on Klar Geckoview → In Nexus 4 API 23, m.yelp.de progress stuck at 25%
Updated•6 years ago
|
Assignee: esawin → snorp
status-firefox61:
--- → wontfix
status-firefox-esr52:
--- → wontfix
status-firefox-esr60:
--- → wontfix
I was able to reproduce this on a Nexus 4 on cnn.com. I tried m.yelp.de and it seemed fine. Looks like Gecko is just not sending us a message via the progress listener. Don't know why yet. Investigating further...
Updated•6 years ago
|
Assignee: snorp → esawin
Comment 7•6 years ago
|
||
[geckoview:klar:p1] because this is a Focus+GV blocker.
Assignee: esawin → nobody
Whiteboard: [geckoview] [qf:p1] → [geckoview:klar:p1] [qf:p1]
Updated•6 years ago
|
Assignee: nobody → esawin
Assignee | ||
Comment 8•6 years ago
|
||
With bug 1437988 landed, can we move away from using onPageStop as a signal for the progress bar on Focus, Emily?
The progress bar is a visual indicator for the visual page load progression, it should probably be based entirely on the value emitted by onProgressChanged.
On the GV side, we will continue investigating why on some page-device combinations onPageStop is not fired, but generally this issue not directly affecting the visual page load progress.
Flags: needinfo?(ekager)
Assignee | ||
Comment 9•6 years ago
|
||
I think Emily might be on PTO, Sebastian, can you look at comment 8?
Flags: needinfo?(s.kaspari)
Comment 10•6 years ago
|
||
Merged a fix into Focus master that uses 100% progress to stop the progress bar.
Flags: needinfo?(ekager)
Assignee | ||
Updated•6 years ago
|
Flags: needinfo?(s.kaspari)
Assignee | ||
Comment 11•6 years ago
|
||
No-Jun, can you please verify that this issue is fixed on Focus' nightly channel?
Flags: needinfo?(npark)
Reporter | ||
Comment 12•6 years ago
|
||
Just verified on nexus 4 that with Geckoview the progressbar progresses normally, and disappears. Can't reproduce the original issue anymore after multiple tries.
Flags: needinfo?(npark)
Reporter | ||
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Target Milestone: --- → Firefox 63
Updated•6 years ago
|
Product: Firefox for Android → GeckoView
Updated•6 years ago
|
Keywords: regression
Target Milestone: Firefox 63 → mozilla63
Updated•3 years ago
|
Performance Impact: --- → P1
Whiteboard: [geckoview:klar:p1] [qf:p1] → [geckoview:klar:p1]
You need to log in
before you can comment on or make changes to this bug.
Description
•