Closed
Bug 1106936
Opened 10 years ago
Closed 10 years ago
[e10s] Loading Spinner Doesn't Activate
Categories
(Firefox :: Tabbed Browser, defect)
Firefox
Tabbed Browser
Tracking
()
People
(Reporter: tech4pwd, Assigned: ttaubert)
References
Details
(Keywords: regression)
Attachments
(1 file)
3.68 KB,
patch
|
billm
:
review+
|
Details | Diff | Splinter Review |
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:37.0) Gecko/20100101 Firefox/37.0 Build ID: 20141202213802 Steps to reproduce: The loading spinner doesn't activate (that's the one that spins to the right), only the connecting spinner activates. Actual results: The problem is that this gives the perception of much slower load time than what actually happens. The user is made to feel like the machine is struggling to connect. Expected results: The loading/rendering spinner should appear as per non-e10s.
Comment 1•10 years ago
|
||
I can seethe problem on latest Nightly e10s windows7.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Updated•10 years ago
|
tracking-e10s:
--- → ?
Comment 2•10 years ago
|
||
Regression window(fx) Good: https://hg.mozilla.org/integration/fx-team/rev/7553b7c1f35f Mozilla/5.0 (Windows NT 6.1; WOW64; rv:36.0) Gecko/20100101 Firefox/36.0 ID:20141117141551 Bad: https://hg.mozilla.org/integration/fx-team/rev/ad799d59abdc Mozilla/5.0 (Windows NT 6.1; WOW64; rv:36.0) Gecko/20100101 Firefox/36.0 ID:20141117143554 Pushlog: https://hg.mozilla.org/integration/fx-team/pushloghtml?fromchange=7553b7c1f35f&tochange=ad799d59abdc Regressed by; ad799d59abdc Tim Taubert — Bug 1099490 - [e10s] Use nsBrowserStatusFilter in the content to avoid a flood of progress messages being sent to the parent r=billm
Assignee | ||
Updated•10 years ago
|
Flags: qe-verify+
Flags: needinfo?(ttaubert)
Flags: firefox-backlog+
Hardware: x86 → All
Assignee | ||
Comment 3•10 years ago
|
||
I initially thought this was caused by the double-filtering in e10s but it actually is caused by the RemoteWebProgress not sending onProgressChange() notifications.
Assignee | ||
Comment 4•10 years ago
|
||
Assignee | ||
Updated•10 years ago
|
Iteration: --- → 37.1
Points: --- → 3
Attachment #8531719 -
Flags: review?(wmccloskey) → review+
Assignee | ||
Comment 5•10 years ago
|
||
https://hg.mozilla.org/integration/fx-team/rev/84c03250d7f6
Assignee | ||
Comment 6•10 years ago
|
||
Backed out for m1-e10s failures: https://hg.mozilla.org/integration/fx-team/rev/faee1a0dc304 TEST-UNEXPECTED-FAIL | /tests/docshell/test/test_bug475636.html | Test timed out. - expected PASS
Assignee | ||
Comment 7•10 years ago
|
||
onRefreshAttempted() should of course default to allowing the action as long as we haven't implemented it yet. https://tbpl.mozilla.org/?tree=Try&rev=5f974f323d14
Assignee | ||
Comment 8•10 years ago
|
||
https://hg.mozilla.org/integration/fx-team/rev/cc368429c22a
Comment 9•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/cc368429c22a
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 37
Comment 10•10 years ago
|
||
I was able to reproduce this issue on Firefox 37.0a1 (2014-12-02) using Windows 7 x64. Verified fixed on Latest Firefox 37.0a1 (2014-12-10) using Windows 7 x64, Ubuntu 12.04 x86 and Mac OSX 10.9.5.
Status: RESOLVED → VERIFIED
status-firefox37:
--- → verified
You need to log in
before you can comment on or make changes to this bug.
Description
•