Open Bug 60553 Opened 25 years ago Updated 3 years ago

All buttons in a toolbar should be as wide as the widest one

Categories

(Core :: XUL, defect)

defect

Tracking

()

Future

People

(Reporter: mpt, Unassigned)

References

(Depends on 1 open bug)

Details

To reproduce: * Switch to the Classic theme, if you are not using it already. * Mouse over the buttons in the toolbar of a Navigator, Messenger, or Composer window. What you should see: * All buttons are the same width. What you actually see: * Buttons are different widths, depending on how wide their icon and button text happens to be. This results in the buttons having variable target areas which are completely independent from common the button actions are, and that's just Wrong. Problem occurs with: * 2000111520 build, Mac OS 9.0 Does not occur with: * Internet Explorer 5.0, Windows 98 For dual menubuttons, the width of the button part of the menubutton (not the menubutton as a whole) should be the same as the width of other buttons in the toolbar. I'm sticking this in XP Apps: GUI, because I don't think this is a Themes issue. Firstly, the width for the toolbar buttons needs to be recalculated whenever a button is added to or removed from the toolbar, something which I don't think themes are capable of. And secondly, this problem applies across all themes given that a theme can't know how long toolbar button text is going to be in a given localization.
This needs to be implemented after bug 60552, otherwise it will be impossible to tell whether bug 60552 has been properly fixed without creating test chrome for it.
Depends on: 60552
QA Contact: sairuh → claudius
In the case of the browser window, making buttons wider would make the location bar shorter. Of course, this wouldn't be a problem, if the user could move the location bar below the navigation bar is (s)he so wished.
seems like themes still need to play a role here. A skin designer may decide to not have their buttons all the same size and would need to be able to override any default width behavior.
ccing pinkerton since he's taken the bug which this depends on - and this bug might even be the real one to fix instead.
Nominating 1.0. A solution talked about in bug 60552 would be simply to implement an "equal-size" or "equal-size-children" or some such attribute or property on box. I wonder if hyatt or evaughan have kicked that idea around. Reassigning, for the moment...
Assignee: ben → hyatt
Component: XP Apps: GUI Features → XP Toolkit/Widgets
Keywords: mozilla1.0
OS: Mac System 8.5 → All
Priority: P3 → --
Hardware: Macintosh → All
So this is essentially a request to support equal-size. Not gonna happen for 1.0 but happy to supply guidelines if someone wants to take this on. Futuring.
Status: NEW → ASSIGNED
Target Milestone: --- → Future
--> default owner
Assignee: hyatt → jaggernaut
Status: ASSIGNED → NEW
QA Contact: claudius → jrgm
Target Milestone: Future → ---
Target Milestone: --- → Future
Assignee: jag → nobody
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.