Closed
Bug 38175
Opened 26 years ago
Closed 26 years ago
Back and forward buttons are displayed poorly.
Categories
(SeaMonkey :: General, defect, P2)
Tracking
(Not tracked)
VERIFIED
FIXED
M16
People
(Reporter: jud, Assigned: bugs)
Details
(Whiteboard: [nsbeta2+])
at least on linux thus far, the back and forward buttons are now grey standard
looking buttons, instead of matching graphical buttons.
Yep, this is a known problem. Ben and the UI gang are working on it ...
Ben, feel free to send this one over to German. :-)
Comment 2•26 years ago
|
||
On win32 I can't tell what style they have, 'cos they are 1 pixel big.
(2000-05-04-08 "crasher" build on Win98SE)
I think this design of the forward and back buttons needs to be re-done.
At least the way it looks right now, the whole "double arrow" look is too
confusing. I just now realized that the second arrow is for the history and
multiple-jump back and forward movement.
I don't like it at all. (sorry)
-WD
Comment 5•26 years ago
|
||
I second that, currently it looks really bad ...
| Assignee | ||
Updated•26 years ago
|
Status: NEW → ASSIGNED
Comment 7•26 years ago
|
||
This buttons just don't fit into the current UI. Can't we go back to the old
round ones? Maybe the round button can be tiled, the upper half working as usual
the other half opening a context menu with the back or forward history.
| Reporter | ||
Comment 8•26 years ago
|
||
moving to major, and platform to all. This looks like total crap and makes
things really hard to use when the default window size is small (another bug)
beucase you have to resize to get to the url bar.
Severity: normal → major
Hardware: PC → All
Comment 9•26 years ago
|
||
I think this is fixed now, looks great for me.
| Assignee | ||
Comment 10•26 years ago
|
||
this is fixed.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Comment 11•26 years ago
|
||
Yes. This is fixed on all platforms now with May22 builds. Marking Verified.
Status: RESOLVED → VERIFIED
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•