Closed Bug 19556 Opened 26 years ago Closed 25 years ago

[FEATURE] Skinnable Navigator

Categories

(Core :: XUL, defect, P1)

Product:
Core
Component:
XUL
Platform:
x86
Other
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: hyatt, Assigned: bugs)

References

Details

(Whiteboard: [nsbeta2-])

This window is unskinnable. Tracking bug for the various problems with this component's skin.
spam: changing qa contact from ckritzer -> paulmac for xul bugs
No owner has stepped up. Therefore I'm picking one. Assigning to matt. cc'ing don.
Assignee: hyatt → matt
Status: ASSIGNED → NEW
Blocks: 20870
Adding [beta], since we will be localizig it, and making a dependency for 12394.
Assignee: matt → rgoodger
Priority: P3 → P1
Summary: [Skins] Navigator is unskinnable → [FEATURE][SKINS] Skinnable Navigator
Target Milestone: M13 → M14
Ben ...
Status: NEW → ASSIGNED
might help if I actually accepted the bug... but then we all love our bugzilla spam, don't we! :D
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
Summary: [FEATURE][SKINS] Skinnable Navigator → [BETA][FEATURE][SKINS] Skinnable Navigator
BULK MOVE: Changing component from XUL to XP Toolkit/Widgets: XUL. XUL component will be deleted.
Component: XUL → XP Toolkit/Widgets: XUL
At the request of jevering, I'm nominating this as a "beta1" blocker.
Keywords: beta1
Since we are not doing skins for beta1, I recommend that we change the summary to "localizable navigator". Changing.
Summary: [BETA][FEATURE][SKINS] Skinnable Navigator → [BETA][FEATURE] Localizable Navigator
pdt - please nominate individual dependencies
Whiteboard: [pdt+]
Summary: [BETA][FEATURE] Localizable Navigator → [FEATURE] Localizable Navigator
my initial sweep shows that this component is localisable (in terms of having complete support for stringbundles and dtd localisation). There are a few areas that I have created fixes for and I will check these in soon. Following this, please either comment here or open new bugs on areas of the navigator package found to be non-localisable.
further note: once this component is fully localisable I shall morph this bug back into what it was originally - skinnable navigator, as that is an issue that cannot be forgotten (post beta1).
Aren't we only localizing beta into Japanese? Do we have all we need to do that? Do we need to do this extra work before beta or can it wait. My guess is the latter. Deleting PDT+ distinction for reconsideration.
Whiteboard: [pdt+]
the work is already done, its just waiting for the tree to go green so I can check it in ;)
Putting on the PDT- radar for beta, but do go ahead and check in if your ready.
Whiteboard: [PDT-]
done and done open new bugs on cases of localisability gone bad.
Keywords: beta1
Summary: [FEATURE] Localizable Navigator → [FEATURE] Skinnable Navigator
Whiteboard: [PDT-]
Target Milestone: M14 → M15
*IGNORE* - more massive spam, changing open XPToolkit bug's QA contact to jrgm@netscape.com
QA Contact: paulmac → jrgm
Adding 'skins' keyword to appropriate bugs en masse, sorry about any mistakes...
Keywords: skins
Blocks: 29160
Move to M16 for now ...
Target Milestone: M15 → M16
Mass-adding beta2 keyword to all skins bugs.
Keywords: beta2
Keywords: nsbeta2
have everything wrapped up now I think. Will check in skinnability fixes for this tomorrow.
Keywords: beta2
Putting on [nsbeta2-] radar. This is a "meta' tracking bug.
Whiteboard: [nsbeta2-]
Move to M20.
Target Milestone: M16 → M20
Marking fixed. If there are specific issues regarding skinability they should be filed separately.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Verified fixed, per PixelJockey meeting.
Status: RESOLVED → VERIFIED
Target Milestone: M20 → M16
No longer blocks: 20870
Keywords: skins
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: jrgmorrison → xptoolkit.widgets
You need to log in before you can comment on or make changes to this bug.