Closed
Bug 934714
Opened 11 years ago
Closed 11 years ago
Work - Don't show progress bar on Start page
Categories
(Firefox for Metro Graveyard :: Firefox Start, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
Firefox 28
People
(Reporter: sfoster, Assigned: sfoster)
References
Details
(Whiteboard: feature=work)
Attachments
(1 file, 1 obsolete file)
2.69 KB,
patch
|
rsilveira
:
review+
|
Details | Diff | Splinter Review |
Yuan suggest we not show the loading progress bar on the Start page - it only adds distraction.
Updated•11 years ago
|
Blocks: metrov1backlog
Summary: Don't show progress bar on Start page → Change - Don't show progress bar on Start page
Whiteboard: [triage] feature=change c=tbd u=tbd p=0
Updated•11 years ago
|
Summary: Change - Don't show progress bar on Start page → Work - Don't show progress bar on Start page
Whiteboard: [triage] feature=change c=tbd u=tbd p=0 → feature=work
Assignee | ||
Comment 1•11 years ago
|
||
There's lots of ways to achieve the goal of this bug. I made the progressbar container's visibility tied to the loading attribute. Then, for about:start we don't update the loading value. That seems to get closest to what we mean. Open to other ideas though
Assignee: nobody → sfoster
Attachment #828773 -
Flags: review?(rsilveira)
Comment 2•11 years ago
|
||
Comment on attachment 828773 [details] [diff] [review]
Dont track loadingState for about:start, collapse progressbar when not loading
Review of attachment 828773 [details] [diff] [review]:
-----------------------------------------------------------------
This patch is causing the progress bar to abruptly disappear after loading, instead of the nice fade we have. One option is to use the startpage attribute to set the visibility collapse on #progress-container.
Attachment #828773 -
Flags: review?(rsilveira) → review-
Assignee | ||
Comment 3•11 years ago
|
||
Take 2. Following IRC discussion, this patch has the progressbar container observing the windowState to turn off when startpage is truthy. We can't just default startpage to true because we have an artivation url or being restoring a session. But we do update the windowState when newTab is called, via the selectedTab setter. Except that currently skips this step for the first tab case. So I modified that logic so BrowserUI.update is always called there, which will set startpage=true, which will hide our progressbar.
Its not perfect, you see a glimpse of it as you startup. But I think it might be good enough?
Attachment #828773 -
Attachment is obsolete: true
Attachment #829019 -
Flags: review?(rsilveira)
Comment 4•11 years ago
|
||
Comment on attachment 829019 [details] [diff] [review]
observe windowState to toggle progressbar, call browserUI.update to reset windowState in time
Review of attachment 829019 [details] [diff] [review]:
-----------------------------------------------------------------
Looks good and works.
Attachment #829019 -
Flags: review?(rsilveira) → review+
Assignee | ||
Comment 5•11 years ago
|
||
Comment 6•11 years ago
|
||
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 28
Comment 7•11 years ago
|
||
Shouldn't this be done for all the other about:xxx pages too?
Assignee | ||
Comment 8•11 years ago
|
||
Yuan, what do you think? I dont think it hurts any on the other about: pages, but we could easily do it.
Flags: needinfo?(ywang)
Comment 9•11 years ago
|
||
I think it makes sense to apply this to other about: pages too. One overall design goal on those in-content pages(from desktop to mobile) is to make it feel less like a webpage, more like one part of chrome.
If the in-content pages can be displayed without any perceived waiting time, we should go ahead and disable showing progress bar.
Flags: needinfo?(ywang)
Assignee | ||
Comment 10•11 years ago
|
||
Follow-up bug as bug 937234. This bug was always about about:start specifically and blocks the Start Page transitions story, which is now complete.
You need to log in
before you can comment on or make changes to this bug.
Description
•