Closed
Bug 6427
Opened 25 years ago
Closed 25 years ago
threadPane.xul: non-localized XUL file
Categories
(Core :: XUL, defect, P3)
Core
XUL
Tracking
()
VERIFIED
WORKSFORME
M7
People
(Reporter: tao, Assigned: alecf)
References
()
Details
Please refer to the "XUL Coding Style Guidelines" in the URL above
for how to make XUL localizable. Thanks!
Q: just a minor point: shall we use
<?xml-stylesheet href="xul.css" type="text/css"?>
instead of
<?xml-stylesheet href="resource:/res/samples/xul.css" type="text/css"?>
|
Assignee | |
Updated•25 years ago
|
Summary: threadPane.xul: non-localizable XUL file → threadPane.xul: non-localized XUL file
Target Milestone: M7
|
|
Assignee | |
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
|
|
Assignee | |
Comment 2•25 years ago
|
||
Actually, this file is localized, and now we're using the right chrome URLs
instead of specifying xul.css.
BULK MOVE: Changing component from XUL to XP Toolkit/Widgets: XUL. XUL
component will be deleted.
Component: XUL → XP Toolkit/Widgets: XUL
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: tao → xptoolkit.widgets
You need to log in
before you can comment on or make changes to this bug.
Description
•