Closed
Bug 249578
Opened 21 years ago
Closed 20 years ago
Move XMLPrettyPrint chrome from "communicator" into "global"
Categories
(SeaMonkey :: Build Config, defect)
SeaMonkey
Build Config
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: benjamin, Assigned: benjamin)
Details
Attachments
(1 file)
|
5.57 KB,
patch
|
jst
:
review+
neil
:
superreview+
|
Details | Diff | Splinter Review |
I'm moving all chrome needed by tier 9/50 (gecko+toolkit) out of the
"communicator" chrome package into "global". This bug covers xmlprettyprint
chrome resources.
|
Assignee | |
Comment 1•21 years ago
|
||
|
|
Assignee | |
Updated•21 years ago
|
Attachment #152197 -
Flags: superreview?(neil.parkwaycc.co.uk)
Attachment #152197 -
Flags: review?(neil.parkwaycc.co.uk)
|
|
Assignee | |
Updated•21 years ago
|
Attachment #152197 -
Flags: review?(neil.parkwaycc.co.uk) → review?(jst)
|
||
Updated•21 years ago
|
Attachment #152197 -
Flags: superreview?(neil.parkwaycc.co.uk) → superreview+
|
||
Comment 2•21 years ago
|
||
Comment on attachment 152197 [details] [diff] [review]
move prettyprint chrome to "global" package
r=jst
Attachment #152197 -
Flags: review?(jst) → review+
|
||
Updated•20 years ago
|
Product: Browser → Seamonkey
|
|
Assignee | |
Comment 3•20 years ago
|
||
This actually got fixed with the grand "DOM" locale moves.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•