Closed
Bug 88136
Opened 24 years ago
Closed 24 years ago
Alignment of throbber off between browser and mail client
Categories
(SeaMonkey :: Themes, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: wjbell, Assigned: hewitt)
Details
(Keywords: modern, polish)
When you have a browser and mail/news window maximized and switch between the
two you can see that the throbber alignment is way different. Then mail/news
throbber is closer to the right edge of the screen and a little lower. This is
only cosmetic but it makes things look cheap when closing or opening from one to
the other.
![]() |
||
Comment 2•24 years ago
|
||
Not only the throbber is not aligned, the bottom toolbar itself isn't either.
One window looks shifted a little bit upwards in comparison to the other
Maximizing the browser, mail/news, composer, & addressbook in modern (build
2001062904 on Win2k) I see the following:
mail/news, composer, addressbook have throbber in the same place. Browser has
throbber slightly to the left and up.
Bottom toolbar may be one pixel thicker on mail/news than on browser, but at
least the icons don't move.
![]() |
||
Comment 4•24 years ago
|
||
I see this too...marking NEW.
This happens on the classic skin also but not as bad. On the classic, you can
see the throbber move down a little when starting up mail/news compared to the
throbber in the browser.
![]() |
||
Comment 6•24 years ago
|
||
Modern theme bug. Not a problem in classic.
Assignee: ben → hewitt
Component: Skinability → Themes
![]() |
||
Updated•24 years ago
|
Blocks: patchmaker
![]() |
Assignee | |
Comment 7•24 years ago
|
||
The nav and mail toolbars are very different looking, and the throbbers were
placed in such a way as to align properly with that design. The mail throbber
is placed so that it is above the inset line that runs across the toolbar.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WONTFIX
![]() |
||
Updated•24 years ago
|
No longer blocks: patchmaker
Updated•17 years ago
|
Product: Core → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•