Closed Bug 77871 Opened 23 years ago Closed 14 years ago

new way of throbber design

Categories

(SeaMonkey :: Themes, enhancement)

Product:
SeaMonkey
Component:
Themes
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED EXPIRED

People

(Reporter: niko, Unassigned)

References

(
URL
)

Details

There was a proposal for a completely new way of design the throbber (see above
url) in Mozillazine (http://www.mozillazine.org/talkback.html?article=1908 -
message posted 04/25 6:44 PM).

I think the proposed way to present a throbber is really cool!

To the animations:
 - the (netscape!) navigator wheel should be replaced in the mozilla versions of
the skin - e.g. with a "roarring" (don't know a valid english word, perhaps
something like shouting, firing out of the mouth) mozilla.
 - for the mail throbber - like "ksheka" meant - :
"For the envelope, how about opening the envelope and a page coming out when
downloading messages, and putting a page in and closing it when sending email?"

All in all, these are two bugs: one for the chrome (XUL and JS) changes and one
for the skin changes.
A number of people in that discussion suggested that the animation should be 
subtle and polished, perhaps just minor changes to the logo/image that already 
appears.

Changing severity to enhancement.
Severity: normal → enhancement
This is up to mozilla.org
I have no idea what obligations we have wrt the current throbber.
Assignee: mpt → endico
Very interesting. I love the idea of using the transparent background
although i'm not fond of the ship's wheel. 

The image is so big that it would be impossible to use it in an icon-only
version. 

I like the throbbers, but not the forward/back buttons.

I guess this image only works with the modern skin. CCing some 'modern' people
to see if they want to use it in the mozilla tree.
endico: of course the wheel in the example
(http://mozillazine-fr.org/tests/modern3_wish_RvR.html) is not good enough for
mozilla and doesnt really fit in the existing design (too large, not cool
enough), but it shows how cool a transparent icon could look if done right :-)
I personally like the idea of such an icon, especially since the existing
Mozilla throbber is rather ugly IMHO. A little problem would be, that we need 2
different throbber, one for Mozilla, one for Netscape, but this shouldn't be a
real problem.
The new icons in the email/news client got a very positive response in that
talkback, so I think that the person(s) who did them is probably the right
person to do a cool throbber which fits well in the overall design of the new
modern theme :-))

ooh, an msn explorer like gui.. but better :) confirming because endico didn't 
veto it outright.
Status: UNCONFIRMED → NEW
Ever confirmed: true
I didn't notice before, but Asa points out that this version of the design moves
the masthead from the left over to the right and gives it a job, by turning it
into the throbber. I think this makes a lot of sense since the masthead normally
serves no purpose, does it? Its just a piece of decoration. 

Also, I really like the borderless reload and stop buttons.
In the past i've only wanted to use the red Mozilla head icon as the basis
for a throbber because I'm concerned that whatever image is used in the
throbber will become a de facto logo image for us in the same way that the
blue M in the current throbber has. 

But, if those images are being used in the UI anyway, as mastheads, then
we might as well use them as the throbber image and then it saves us from 
needing yet a new piece of throbber artwork. (for the modern theme at least.
classic still needs one)
It should be emphasized that the main motivation for this change was to move the 
masthead to the right instead of the left of the window. When the image is on 
the left it causes all the toolbar buttons to move to the right. This interrupts 
muscle memory trained from years of experience with previous versions of 
Netscape. Moving the image to the right eliminates this problem, looks cool, and 
if turned into a throbber replacement, makes it useful too.

I also suggested in the Mozillazine talkback that one problem with having this 
masthead replace the throbber is that the throbber normally hangs with the right 
edge of the window when the window is resized smaller. The masthead image is 
probably too big to fulfill that role; you'd lose too much of the toolbar. A 
solution might be to allow the masthead to act as the toolbar background (I 
don't know how strange that would look). I suppose you could also have a smaller 
masthead image that appears when the big one won't fit and that behaves similar 
to the throbber.
I personally have thought that the wheel would look a lot better if it were 
rotating 360 degrees rather than back and forth.  But I find the idea pretty 
cool, for whatever that's worth.  :)
Component: User Interface Design → Themes
Maybe the throbber from the old Firebird (0.5-0.1) should be used because it
looks more sensible
Product: Core → SeaMonkey
Assignee: endico → nobody
QA Contact: zach → themes
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.