After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 163890 - Shouldn't spinner be in statusbar?
Shouldn't spinner be in statusbar?
Status: RESOLVED DUPLICATE of bug 454914
Product: epiphany
Classification: Core
Component: Interface
git master
Other Linux
: Normal enhancement
: ---
Assigned To: Epiphany Maintainers
Marco Pesenti Gritti
Depends on:
Blocks:
 
 
Reported: 2005-01-13 03:16 UTC by Jorn Baayen
Modified: 2007-07-24 20:30 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Description Jorn Baayen 2005-01-13 03:16:30 UTC 
As the spinner is a "status thing", wouldn't it be more suitable to have it in
the status bar? It would also look less ugly as a bonus, it being in a separate
toolbar just looks plain horrible with many themes.
Comment 1 Jorn Baayen 2005-01-14 03:43:17 UTC 
It should probably somehow also be possible to put the spinner in the main
toolbar, by putting an empty toolitem with expand set to true (this is how
nautilus does it) in between the last item and the spinner- if the location
entry isn't there.
Comment 2 Reinout van Schouwen 2005-07-20 18:59:45 UTC 
Confirmed, that would be a nice enhancement.
Comment 3 Christian Persch 2005-08-17 18:15:17 UTC 
I made http://www.gnome.org/~chpe/patches/statusbar-spinner.diff to try it a
while ago; and I have to say I didn't like it at all...
Comment 4 Reinout van Schouwen 2006-02-02 11:13:24 UTC 
I'm not convinced about having it in the status bar either, but it would be nice if the spinner were a first class toolbar widget so that it could be removed from the toolbar.
Comment 5 Diego Escalante Urrelo (not reading bugmail) 2007-06-18 13:25:05 UTC 
Is it worth it?
Comment 6 Reinout van Schouwen 2007-07-24 20:30:33 UTC 
The spinner isn't going into the status bar. The remaining part of this bug is better described in bug 454914.

*** This bug has been marked as a duplicate of 454914 ***