[Skins] Global skin must contain all font/color/border info

VERIFIED FIXED in Future

Status

P4
normal
VERIFIED FIXED
19 years ago
10 years ago

People

(Reporter: hyatt, Assigned: hewitt)

Tracking

Trunk
Future
x86
Other

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [nsbeta2-] [nsbeta3-])

(Reporter)

Description

19 years ago
Need to change things so that the global skin is sufficiently rich to be used
for all font, color, and border info.  No derived skin should ever contain this
info.

Comment 1

19 years ago
spam: changing qa contact from ckritzer -> paulmac for xul bugs

Comment 2

19 years ago
Adding [beta], since we will be localizig it, and making a dependency for 12394.

Updated

19 years ago
Target Milestone: M13 → M15

Comment 3

19 years ago
targetting M15

Comment 4

19 years ago
These are pre-requisites of localizable chrome. Marking them [BETA]. Please fix
them by M14 so that we can be ready for localization. To make the chrome
localizable, the font name, font size, and UI geometry setting needs to be
externalized and move to chrome/[package]/locale/*.css.

Adding lyecies, amasri, and tao into CC list.


Thanks

Updated

19 years ago
Summary: [Skins] Global skin must contain all font/color/border info → [BETA][Skins] Global skin must contain all font/color/border info
(Reporter)

Updated

19 years ago
Target Milestone: M15 → M16

Comment 5

19 years ago
BULK MOVE: Changing component from XUL to XP Toolkit/Widgets: XUL.  XUL 
component will be deleted.
Component: XUL → XP Toolkit/Widgets: XUL

Comment 6

19 years ago
Two bugs where things that shouldn't be able to are changing colours of UI
elements in the default skin for Mozilla:

Bug 25349, "sidebar, dialogs using Win32 text colour; bad UI if white"

Bug 24919, "browser text colour prefs affect chrome as well as content"

Comment 7

19 years ago
Due to Beta indication in Summary, putting beta1 into keyword field.
Keywords: beta1

Comment 8

19 years ago
Is this needed for Browser skin?
Summary: [BETA][Skins] Global skin must contain all font/color/border info → [Skins] Global skin must contain all font/color/border info
Whiteboard: [NEED INFO]
(Reporter)

Comment 9

19 years ago
Depends on whether or not you want the app to be skinnable in beta1.  We already 
know there won't be a UI way to skin the app in beta1.  If this bug isn't fixed, 
you won't be able to write skins off of beta1 at all.

Updated

19 years ago
Whiteboard: [NEED INFO] → [PDT+]
(Reporter)

Comment 10

19 years ago
You should realize that truly fixing this bug will involve an enormous amount of 
work, and it involves fixing the 20 dependent bugs for each individual 
component.  You are basically committing to having a skinnable product in beta.

This task will probably involve at least a week's worth of work on the part of 
german, ben, hangas, and myself, and would drag in other component UI owners as 
well.  

I do think it's worth shooting for.  Just making sure you realize what you're 
getting us into.  This bug is very large.
(Reporter)

Comment 11

19 years ago
Removing for reconsideration.
Whiteboard: [PDT+] → [PDT]
(Reporter)

Comment 12

19 years ago
Given the amount open bugs, we should probably just bite the bullet and admit 
that we won't be skinnable in the least in beta1.

Comment 13

19 years ago
Per last comment, putting on the PDT- radar for beta1.
Whiteboard: [PDT] → [PDT-]

Updated

19 years ago
QA Contact: paulmac → jrgm

Comment 14

19 years ago
*IGNORE* - more massive spam, changing open XPToolkit bug's QA contact to
jrgm@netscape.com

Comment 15

19 years ago
Adding 'skins' keyword to appropriate bugs en masse, sorry about any 
mistakes...
Keywords: skins
(Reporter)

Comment 16

19 years ago
...
Assignee: hyatt → ben
Status: ASSIGNED → NEW
Keywords: beta1 → beta2
Whiteboard: [PDT-]

Updated

19 years ago
Blocks: 29160

Comment 17

19 years ago
Mass-adding beta2 keyword to all skins bugs.

Updated

19 years ago
Keywords: nsbeta2

Comment 18

19 years ago
Putting on [nsbeta2+][5/16] radar.  This is a feature MUST complete work by 
05/16 or we may pull this feature for PR2.
Whiteboard: [nsbeta2+][5/16]

Comment 19

19 years ago
Move to M19.
Target Milestone: M16 → M19

Comment 20

19 years ago
Putting on [nsbeta2-] radar, removing 5/16.  Did not make the Netscape 6 train.
Whiteboard: [nsbeta2+][5/16] → [nsbeta2-]

Updated

18 years ago
Target Milestone: M19 → M20

Comment 21

18 years ago
M20

Comment 22

18 years ago
Nav triage team: setting to "future"
Whiteboard: [nsbeta2-] → [nsbeta2-] [nsbeta3-]
Target Milestone: M20 → Future

Comment 23

18 years ago
re-assigning to Paul Hangas
Assignee: ben → hangas

Comment 24

18 years ago
Note we are trying to reduce the scope of skins to meet schedules, happy to 
discuss.  Other skin bugs being Futured include bug 39336 and bug 19562.

Updated

18 years ago
Status: NEW → ASSIGNED
Adding nsbeta3 keyword to bugs which already have nsbeta3 status markings so 
the queries don't get all screwed up.
Keywords: nsbeta3

Updated

18 years ago
Keywords: skins

Updated

18 years ago
Assignee: hangas → hewitt
Status: ASSIGNED → NEW
Component: XP Toolkit/Widgets: XUL → Themes
QA Contact: jrgm → pmac

Comment 26

18 years ago
Sending to Joe
(Assignee)

Updated

18 years ago
Status: NEW → ASSIGNED
Priority: P3 → P4

Comment 27

18 years ago
Themes Triage Team marking fixed because changes in skins for Mojo will redefine 
the structure of a skin.
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED

Comment 28

18 years ago
After speaking with David Hyatt, this bug is marked as invalid.
Marking verified.
Status: RESOLVED → VERIFIED
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.