Closed Bug 22071 Opened 25 years ago Closed 25 years ago

[feature] [XBL] Toolbar grippies need to support different looks to be skinnable

Categories

(Core :: XUL, defect, P3)

x86
Other
defect

Tracking

()

RESOLVED FIXED

People

(Reporter: german, Assigned: hyatt)

References

Details

(Whiteboard: 1 day)

Right now toolbox grippies looks are hardcoded into their parent container, so all toolbars grippies look the same regardless of whether they are part of XPMenu bars, Toolbars task switcher etc. In order to make the UI skinnable and have a flexible solution across Mozilla, that would also work for Netscape we need to support individual styles for these grippies. Ideally they would be set up as anonymous nodes (like splitters are today), so that we can whatever abritrary XUL insode them. Future uses might include but are not limited to dragging/resizing side-by-side toolbars etc. We need to have this before any alphas/betas are rolled out in order to be able to remove the current limitations on skinn-ability.
Status: NEW → ASSIGNED
Target Milestone: M14
yup.
Target Milestone: M14 → M15
targetting m15
Target Milestone: M15 → M16
Target Milestone: M16 → M15
Need to put grippy construction into XBL.
Summary: Toolbar grippies need to support different looks to be skinnable → [XBL] Toolbar grippies need to support different looks to be skinnable
*IGNORE* - more massive spam, changing open XPToolkit bug's QA contact to jrgm@netscape.com
QA Contact: paulmac → jrgm
*** Bug 15158 has been marked as a duplicate of this bug. ***
Summary: [XBL] Toolbar grippies need to support different looks to be skinnable → [feature] [XBL] Toolbar grippies need to support different looks to be skinnable
Whiteboard: 1 day
Adding 'skins' keyword to appropriate bugs en masse, sorry about any mistakes...
Keywords: skins
This bug is taking more time than anticipated.
Blocks: 29160
Mass-moving most M15 bugs to M16
Target Milestone: M15 → M16
fixed
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Keywords: skins
You need to log in before you can comment on or make changes to this bug.