Closed
Bug 17621
Opened 25 years ago
Closed 25 years ago
Leave toolbar button separators in XUL
Categories
(SeaMonkey :: General, defect, P3)
SeaMonkey
General
Tracking
(Not tracked)
VERIFIED
WONTFIX
People
(Reporter: michael.j.lowe, Assigned: german)
Details
It seems that you are removing the toolbar button separators for the new skin. I think it is better they are left in the XUL code because in some skins people will want them displayed. A better approach if you don't want them displayed with this skin is to hide them with the appropriate CSS rules.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WONTFIX
XUL springs are the official (more appropriate and generalizeable) method of achieving separators in XUL. Properly named and ID'd springs can then display whatever style they want (such as borders, ridges etc).
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 2•25 years ago
|
||
marking VERIFIED
Reporter | ||
Comment 3•25 years ago
|
||
If I look at the file editorOverlay.xul, I don't see any XUL springs either. Are they located for the editor somewhere else?
No XUL springs can be anything you want to be they are a tag that's already an official part of XUL. The exact specification of the look, spacing etc. is part of a skin. The older spearator was specified as html:div which is not as flexible and has other problems when used inside boxes. In other words if you want spacers in your skin you simply specify the springs in your XUL file, then use a class (for multiple occurences) or id (for single ocurrences) and refer to that in your style sheet. As I said the particular design should really not be hard-coded into a global XUL.css but instead is part of a specific skin design.
Moving all UE/UI bugs to new component: User Interface: Design Feedback UE/UI component will be deleted.
Component: UE/UI → User Interface: Design Feedback
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•