Closed Bug 400398 Opened 17 years ago Closed 16 years ago

Remove the throbber from the menu bar / nav toolbar default set

Categories

(Firefox :: Tabbed Browser, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED FIXED
Firefox 3.1b2

People

(Reporter: dao, Assigned: dao)

References

(Depends on 1 open bug)

Details

Attachments

(1 file, 5 obsolete files)

Attached patch patch (obsolete) — Splinter Review
This idea came up in bug 397723, in particular bug 397723 comment 94.
Attachment #285471 - Flags: review?(mconnor)
I don't like the idea of having to look in a different place depending on whether I have more than one tab open.
Hmm, this would also mean that if a tab is hidden (ie, in overflow) and still loading, there's no visual indication that the browser is chugging away. I might be able to live with that, but if we still auto-collapse the tab strip when there's only 1 tab I'd agree with Jesse here.
Attachment #285471 - Flags: review?(mconnor) → ui-review?(beltzner)
I think it's worth noting that the discussion which prompted this was the suggestion that the throbber should be invisible when not actually active. I think I'd prefer a disappearing throbber (empty space) next to the search field than a throbber that appears when the tabbar isn't visible.
(In reply to comment #3)
> I think it's worth noting that the discussion which prompted this was the
> suggestion that the throbber should be invisible when not actually active.

This is the way spinning progress indicators work on OS X. I don't really have a problem with the throbber being visible or not visible, but if it's going to look like a spinning progress indicator, it should behave consistently.

If we don't want to change the behavior I'd suggest we change the graphic to be something different.
So, I'm told current thinking for the throbber is now more along the lines of bug Bug 402968. I think it accomplishes the same goal as this bug originally sought to (get rid of inactive throbber state), so depending on how you look at it this bug can be with a DUPE or WONTFIX...
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → WONTFIX
(In reply to comment #5)
> So, I'm told current thinking for the throbber is now more along the lines of
> bug Bug 402968. I think it accomplishes the same goal as this bug originally
> sought to (get rid of inactive throbber state), so depending on how you look at
> it this bug can be with a DUPE or WONTFIX...

Can we still expect something from bug 402968?
So, looks like the conclusion is that bug 402968 is a WONTFIX, and we should do it this way instead. >_< Reopening! :)
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Attached patch better patch (obsolete) — Splinter Review
Attachment #285471 - Attachment is obsolete: true
Attachment #300692 - Flags: review?(gavin.sharp)
Attachment #285471 - Flags: ui-review?(beltzner)
Target Milestone: --- → Firefox 3 beta4
Comment on attachment 300692 [details] [diff] [review]
better patch

Beltzner and Connor said they want this
Attachment #300692 - Flags: ui-review+
Attachment #300692 - Flags: ui-review+
Flags: blocking-firefox3?
Summary: Show the throbber in the menu bar / main toolbar only if the tab bar is collapsed → Show the throbber next to the menu bar only if the tab bar is collapsed
Not a blocker, but wanted.

Dao: will this cause bouncy-ui? I'm just wondering how (if at all) the width of the search field is affected by this patch.
Flags: wanted-firefox3+
Flags: blocking-firefox3?
Flags: blocking-firefox3-
Comment on attachment 300692 [details] [diff] [review]
better patch

This will shift the search bar on Mac. Should the space be preserved?
Beltzner and I agree that this should be WONTFIX.  What we should do instead is:

* Make the throbber invisible (transparent but taking up the same amount of space) when nothing is loading.  This would bring Windows in line with Mac, and it's just a matter of changing an image.

* Make the throbber visible in Customize Toolbars mode, so you can grab onto it easily if it is in a toolbar or recognize it easily if it is in the palette.

* MAYBE: if the user selects "always show the tab bar", automatically remove the throbber from whatever toolbar it is on.
(In reply to comment #12)
> Beltzner and I agree that this should be WONTFIX.  What we should do instead
> is:
> 
> * Make the throbber invisible (transparent but taking up the same amount of
> space) when nothing is loading.  This would bring Windows in line with Mac, and
> it's just a matter of changing an image.

This is rather unrelated and doesn't explain why this should be WONTFIXed. The Mac theme is already doing it, and it doesn't interfere with the goal of this bug.

> * MAYBE: if the user selects "always show the tab bar", automatically remove
> the throbber from whatever toolbar it is on.

I don't see why it should be limited to this case. A few moments ago I couldn't even tell if I set that pref, since I have multiple tabs pretty much always.
Summary: Show the throbber next to the menu bar only if the tab bar is collapsed → Show the throbber next to the menu bar only if it's busy and the tab bar is collapsed
Attachment #300692 - Attachment is obsolete: true
Attachment #304348 - Flags: ui-review?(beltzner)
Attachment #300692 - Flags: review?(gavin.sharp)
> This is rather unrelated and doesn't explain why this should be WONTFIXed

It's related in that it reduces the visual-complexity hit of having the throbber next to the menu bar (Windows) or on the navigation toolbar (Mac).

I already explained why this should be WONTFIXed, in comment 1: it would be really weird and inconsistent to have the activity indicator go away (from its normal location) depending on whether you have multiple tabs open.  Maybe *you* have a zillion tabs open all the time, so the inconsistency wouldn't bother you, but many people (including me) often have one or two.
(In reply to comment #15)
> > This is rather unrelated and doesn't explain why this should be WONTFIXed
> 
> It's related in that it reduces the visual-complexity hit of having the
> throbber next to the menu bar (Windows) or on the navigation toolbar (Mac).

The still throbber is a minor complexity hit compared to two spinning throbbers. But again, we can do both.

> I already explained why this should be WONTFIXed, in comment 1: it would be
> really weird and inconsistent to have the activity indicator go away (from its
> normal location) depending on whether you have multiple tabs open.  Maybe *you*
> have a zillion tabs open all the time, so the inconsistency wouldn't bother
> you, but many people (including me) often have one or two.

If we don't show the still throbber, it wouldn't "go away", it would just not appear anymore. For the user there's not really anything new to learn, since the throbber on the tabs has been there for ages and is just as attention-grabbing.
By the way, the assumption that I have a zillion tabs open all the time is wrong. I was talking about my main profile, which isn't the only one that I have and use.
Morphing, given bug 392870 and bug 455864.
Status: REOPENED → ASSIGNED
Depends on: 392870, 455864
Summary: Show the throbber next to the menu bar only if it's busy and the tab bar is collapsed → Remove the toolbar throbber
Target Milestone: Firefox 3 beta4 → ---
Attached patch remove it (obsolete) — Splinter Review
Attachment #304348 - Attachment is obsolete: true
Attachment #339241 - Flags: review?(mano)
Attachment #304348 - Flags: ui-review?(beltzner)
What does this have to do with easily discoverability of tab browsing for new users?

So now the throbber will only spin on the tab.  What about when tabs that are loading out of view on the tabstrip?
(In reply to comment #19)
> What does this have to do with easily discoverability of tab browsing for new
> users?

It depends on the browser.tabs.autoHide change.

> What about when tabs that are loading out of view on the tabstrip?

The toolbar throbber isn't global, so that's unrelated.
(In reply to comment #14)
> Created an attachment (id=304348) [details]
> show the throbber if it's busy and the tab bar is collapsed

(In reply to comment #15)
> I already explained why this should be WONTFIXed, in comment 1: it would be
> really weird and inconsistent to have the activity indicator go away (from its
> normal location) depending on whether you have multiple tabs open.  Maybe *you*
> have a zillion tabs open all the time, so the inconsistency wouldn't bother
> you, but many people (including me) often have one or two.

I usually have a lot of tabs (150 in Firefox, 40 in SeaMonkey), but I also prefer to "always show the tab bar" because if for some reason I start the browser with only one tab, then if the tab bar isn't there I'm lost. Yet I think that the single throbber on the menubar or toolbar has a different functionality than the individual throbbers on all tabs, and I'd like it to stay, regardless of whether the tab bar is collapsed: I'm not always sure where to look for the current tab, but a revolving (or otherwise moving) throbber at a fixed location near top right is something I couldn't miss. So I agree with comment #15 even though I have many tabs open most of the time.
IMO the throbber on toolbar must stay. It is important as it shows that there's still some activity in tabs (loading, script running, etc). Instead of looking through the line of tabs you can simply look on right upper corner. And, if needed, it can be removed manually by user, so I don't think it's worth a bug.

(In reply to comment #20)
> (In reply to comment #19)
> > What about when tabs that are loading out of view on the tabstrip?
> 
> The toolbar throbber isn't global, so that's unrelated.

Isn't global? I thought it was.
Then, if it's not global, what exactly does it indicate?
> (In reply to comment #20)
> > (In reply to comment #19)
> > > What about when tabs that are loading out of view on the tabstrip?
> > 
> > The toolbar throbber isn't global, so that's unrelated.
> 
> Isn't global? I thought it was.
> Then, if it's not global, what exactly does it indicate?

Yeah, it is not global.  So it's only purpose is to indicate the active tab activity.  It does seem pretty pointless when you think about it though.  I think the best thing to do would be to make it global since if there are tabs loading out of view on the tabstrip, users will at least know there is network activity/some tab sucking up cpu power.
Comment on attachment 339241 [details] [diff] [review]
remove it

get a ui-r before landing. I don't like this myself.
Attachment #339241 - Flags: review?(mano) → review+
Attachment #339241 - Flags: ui-review?(faaborg)
We could also leave the throbber in the customization palette, if we wanted.
As I wontfixed bug 455864, it makes more sense to leave the throbber in the customization sheet.
Attachment #339241 - Attachment is obsolete: true
Attachment #340549 - Flags: review?(mano)
Attachment #339241 - Flags: ui-review?(faaborg)
Ask ux.
The removal of the toolbar throbber has been discussed with Alex and Beltzner. I asked Beltzner if we should leave it in the customization sheet but he wasn't sure. We can still do that later if wanted.
(In reply to comment #28)
> We can still do that later if wanted.

I.e. remove it entirely.
Summary: Remove the toolbar throbber → Remove the throbber from the menu bar / nav toolbar default set
Comment on attachment 340549 [details] [diff] [review]
leave it in the customization sheet

Giving user's the ability to customize their browser is overall a good thing, so ui-r+  (although I don't really agree with the user's decision to have a throbber visually disconnected and distant from the thing that it is representing feedback for).
Attached patch updated to trunkSplinter Review
Attachment #340549 - Attachment is obsolete: true
Attachment #344740 - Flags: review?(mano)
Attachment #340549 - Flags: review?(mano)
Attachment #344740 - Flags: review?(mano) → review+
Comment on attachment 344740 [details] [diff] [review]
updated to trunk

r=mano
http://hg.mozilla.org/mozilla-central/rev/ab03149a5b63
Status: ASSIGNED → RESOLVED
Closed: 17 years ago16 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 3.1b2
Depends on: 470395
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: