Closed
Bug 719868
Opened 13 years ago
Closed 13 years ago
Progress throbber still shows when we load about:home on startup
Categories
(Firefox for Android Graveyard :: General, defect, P3)
Tracking
(firefox11 verified, firefox12 verified, firefox13 verified, fennec11+)
VERIFIED
FIXED
Firefox 12
People
(Reporter: Margaret, Assigned: Margaret)
References
Details
(Whiteboard: startup-ux)
Attachments
(1 file, 4 obsolete files)
2.72 KB,
patch
|
mfinkle
:
review+
akeybl
:
approval-mozilla-beta+
|
Details | Diff | Splinter Review |
Somehow my patch from bug 718846 didn't catch this code path :(
Updated•13 years ago
|
tracking-fennec: --- → 11+
Priority: -- → P3
![]() |
||
Updated•13 years ago
|
Whiteboard: startup-ux
Assignee | ||
Comment 1•13 years ago
|
||
Putting the about:home check in the Tab:Load/Tab:Add observer didn't catch the cases where we're loading a URI directly from JS, which we're doing at startup (going through addTab).
Attachment #591642 -
Flags: review?(mark.finkle)
Comment 2•13 years ago
|
||
Comment on attachment 591642 [details] [diff] [review]
patch
I would rather keep addTab and loadURI ignorant of "about:home". Instead, let's pass a param object in browser.js startup:
> Services.obs.removeObserver(restoreCleanup, "sessionstore-windows-restored");
> if (aData == "fail")
>- BrowserApp.addTab("about:home");
>+ BrowserApp.addTab("about:home", { showProgress: false });
> ss.restoreLastSession(restoreToFront);
> } else {
>- this.addTab(url);
>+ this.addTab(url, { showProgress: url != "about:home" });
Would this cover the situation you are trying to fix?
Attachment #591642 -
Flags: review?(mark.finkle) → review-
Assignee | ||
Comment 3•13 years ago
|
||
Addressed comments. We should also make sure Brian does this in his patch for bug 701092.
Attachment #591642 -
Attachment is obsolete: true
Attachment #591965 -
Flags: review?(mark.finkle)
Assignee | ||
Comment 4•13 years ago
|
||
(In reply to Margaret Leibovic [:margaret] from comment #3)
> We should also make sure Brian does this in his patch
> for bug 701092.
Oh, I just looked more closely and he's just moving one of these lines around, so he should catch it when he gets a conflict.
Comment 5•13 years ago
|
||
Comment on attachment 591965 [details] [diff] [review]
patch
I thought some more about your feedback about not wanting to depend on callers to set showProgress. I still think using the param is better for flexibility. I could be proved wrong in time though.
Attachment #591965 -
Flags: review?(mark.finkle) → review+
Assignee | ||
Comment 6•13 years ago
|
||
Assignee | ||
Comment 7•13 years ago
|
||
Backed out because of twinopen failures:
https://hg.mozilla.org/integration/mozilla-inbound/rev/687b80084d3d
Assignee | ||
Comment 8•13 years ago
|
||
This was green on try. The problem was that by passing a params object ourselves, we weren't picking up some default params from addTab: http://mxr.mozilla.org/mozilla-central/source/mobile/android/chrome/content/browser.js#470.
This makes me slightly concerned that it's too easy to make mistakes like this. I was considering changing the way we set default params in addTab to always set those options, but I didn't know if that would break other addTab consumers, so I left it alone. Perhaps something to look into in the future.
Attachment #591965 -
Attachment is obsolete: true
Attachment #592404 -
Flags: review?(mark.finkle)
Assignee | ||
Comment 9•13 years ago
|
||
Attachment #592404 -
Attachment is obsolete: true
Attachment #592404 -
Flags: review?(mark.finkle)
Attachment #592778 -
Flags: review?(mark.finkle)
Assignee | ||
Comment 10•13 years ago
|
||
This addresses what we talked about on IRC.
Attachment #592778 -
Attachment is obsolete: true
Attachment #592778 -
Flags: review?(mark.finkle)
Attachment #592913 -
Flags: review?(mark.finkle)
Updated•13 years ago
|
Attachment #592913 -
Flags: review?(mark.finkle) → review+
Assignee | ||
Comment 11•13 years ago
|
||
![]() |
||
Comment 12•13 years ago
|
||
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 12
Assignee | ||
Comment 13•13 years ago
|
||
Comment on attachment 592913 [details] [diff] [review]
patch w/ default params changes
[Approval Request Comment]
Mobile-only polish fix to make startup appear less janky. Low risk.
Attachment #592913 -
Flags: approval-mozilla-aurora?
Assignee | ||
Comment 14•13 years ago
|
||
Comment on attachment 592913 [details] [diff] [review]
patch w/ default params changes
[Approval Request Comment]
This made its way into aurora through the merge, but it still needs to be uplifted to beta.
Attachment #592913 -
Flags: approval-mozilla-aurora? → approval-mozilla-beta?
![]() |
||
Comment 15•13 years ago
|
||
Comment on attachment 592913 [details] [diff] [review]
patch w/ default params changes
[Triage Comment]
Mobile only - approved for Beta 11.
Attachment #592913 -
Flags: approval-mozilla-beta? → approval-mozilla-beta+
Comment 16•13 years ago
|
||
status-firefox11:
--- → fixed
Comment 17•13 years ago
|
||
Verified fixed on:
Firefox 13.0a1 (2012-02-06)
20120206031148
http://hg.mozilla.org/mozilla-central/rev/814d0b2dbaba
Device: HTC Desire Z
OS: Android 2.3.3
Firefox 12.0a2 (2012-02-06)
20120206042011
http://hg.mozilla.org/releases/mozilla-aurora/rev/9fb0c06ceb49
Device: HTC Desire Z
OS: Android 2.3.3
Firefox 11.0
20120206202409
http://hg.mozilla.org/releases/mozilla-beta/rev/1c0aba74d116
Device: HTC Desire Z
OS: Android 2.3.3
Updated•13 years ago
|
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•