Closed Bug 29160 Opened 23 years ago Closed 23 years ago

Skinnability issues


(Core Graveyard :: Skinability, defect, P3)



(Not tracked)



(Reporter: trudelle, Assigned: hangas)


(Depends on 1 open bug)


(Keywords: meta, Whiteboard: [nsbeta2-])

I gathered comments from several contributors, some of them key developers:

We need to have a very simple, generic XUL structure and aesthetic design, in 
order to be able to add multiple skins.  Currently, there are problems where 
design decisions that appear to have been made for the Netscape/Netcenter 
appearance severely constrain the ability to add other skins.

Menubar should be a toolbar.
All windows should start with a toolbox containing 3 toolbars: the menubar, the 
personal toolbar, and the command toolbar. Each of these should span the full 
width of the window. The throbber should be on top of the right edge of the 
command toolbar.  

Rounded corners should only be done in CSS, even then they make reordering ugly.

Note: This bug report may turn out to be merely a tracking bug for dependent 
bugs filed against specific issues.
Blocks: 28883
For `in order to be able to add multiple skins', read `in order to make 
constructing multiple skins easy, and also to focus attention on the content 
rather than the chrome'.

The rounded corners problem is dealt with in bug 23392.

For `Menubar should be a toolbar', read `Menu bar should be a toolbar (except on 
those platforms with a single menu bar, e.g. MacOS)'.

For `on top of the right edge of the command toolbar', read `on top of the right 
edge of the uppermost toolbar, not counting the menu bar (unless the menu bar is 
the only toolbar present)'. This is covered in bug 20058.
Depends on: 20058, 23392
OS: Windows 98 → All
Hardware: PC → All
Keywords: meta
Depends on: 32486
Adding 'skins' keyword to appropriate bugs en masse, sorry about any 
Keywords: skins
Added 'skins' bugs to dependency list, targetted m16
No longer blocks: 29160
No longer depends on: 29160
Target Milestone: --- → M16
Depends on: 3013
No longer depends on: 34554
Mass-adding beta2 keyword to all skins bugs.
Keywords: beta2
Depends on: 34554
No longer depends on: 14949
Blocks: 35035
Blocks: 35038
No longer blocks: 35035
No longer blocks: 35038
Added a few new skins bugs, fixed a couple that were in the wrong dependency 
field. Still looking for expected landing dates (mm/dd, not durations) in the 
whiteboard summaries of these bugs.
Depends on: 34389
No longer depends on: 34554
Depends on: 32155
No longer depends on: 34551
Depends on: 34551
No longer depends on: 18581
Depends on: 34554
No longer depends on: 8832
Depends on: 34556
No longer depends on: 14532
Depends on: 34563
No longer depends on: 22204
reassigning to hangas, who now owns skinnability
Assignee: trudelle → hangas
Keywords: nsbeta2
Keywords: beta2
QA Assigning non-confidential New/Assigned User Interface: Design Feedback bugs 
to Matthew Thomas (

Matthew Thomas is now the QA owner for the User Interface: Design Feedback 
component. (Bugs that involve UI issues in the Netscape-branded Mozilla browser 
should continue be QA assigned to
QA Contact: elig → mpt
A tracking bug, nsbeta-
Whiteboard: [nsbeta-]
Upating [nsbeta-] to read [nsbeta2-] in Status Whiteboard.
Whiteboard: [nsbeta-] → [nsbeta2-]
M16 has been out for a while now, these bugs target milestones need to be 
Component: User Interface: Design Feedback → Skinability
QA Contact: mpt → BlakeR1234
Target Milestone: M16 → M18
No longer depends on: 32486
Keywords: skins
Let's get rid of this meta bug. Only 4 of the dependancies are still open, and
this is why the skinability component is for. Peter, any idea if this can be
resolved without further work or if we actually need to open new bugs, reassign,
re-target, etc?
Also M18 milestone is over.
I have no need for this bug, Paul & Blake can do whatever they like with it.
In that case...
Closed: 23 years ago
Resolution: --- → FIXED
QA Contact: blakeross → pmac
Marking verified on all platforms (commercial build: 2001-06-01-08-trunk).
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.