Closed
Bug 39315
Opened 25 years ago
Closed 20 years ago
RFE:Skin Picker capability needed to choose default1 or default2 skin.
Categories
(CCK Graveyard :: CCK-Wizard, enhancement, P3)
Tracking
(Not tracked)
RESOLVED
WONTFIX
Future
People
(Reporter: bmartin, Assigned: shrutiv)
Details
Latest CCK Build dated: 05-11-00
CCK Beta2 requirement.
Skin picker capability needed within the CCK Tool UI. Allowing users to choose
between 2 default skins.
There's currently a proposed UI that simply asks the user to enter the path to
the skin directory or jar file.
Would the skin picker UI be in addition to asking for the path or would it
replace asking the user for the path?
Currently the UI exists for this. However, the drop down pick list doesn't
contain the the names of the default skins.
Marking as Future per 9-25-00 bug triage
Target Milestone: M17 → Future
changing assigned to shrutiv from varada
Assignee: varada → shrutiv
Status: ASSIGNED → NEW
Summary: Skin Picker capability needed to choose default1 or default2 skin. → RFE:Skin Picker capability needed to choose default1 or default2 skin.
| Assignee | ||
Updated•24 years ago
|
Status: NEW → ASSIGNED
Comment 9•24 years ago
|
||
Updating QA contact to me for half of the CCK bugs while bom-shik is gone.
QA Contact: blee → barrettl
| Assignee | ||
Comment 11•24 years ago
|
||
Decided to document this. Reassigning to Kristi.
Assignee: shrutiv → kristif
Status: ASSIGNED → NEW
Comment 12•24 years ago
|
||
Netscape documentation team (see bugscape 10892) has a bug to document how to
implement this manually.
This bug, which we are likely not going to get to, is about implementing a
feature in CCK to switch skins. Reassigning to shrutiv.
Assignee: kristif → shrutiv
| Assignee | ||
Updated•24 years ago
|
Target Milestone: Future → ---
| Assignee | ||
Updated•24 years ago
|
Target Milestone: --- → Future
| Assignee | ||
Updated•23 years ago
|
Severity: normal → enhancement
Comment 13•20 years ago
|
||
Old CCK.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•