Closed
Bug 231176
Opened 21 years ago
Closed 18 years ago
Separate out toolkit default prefs from gecko
Categories
(Core :: Preferences: Backend, defect, P3)
Tracking
()
RESOLVED
WONTFIX
mozilla1.9alpha1
People
(Reporter: benjamin, Assigned: benjamin)
References
Details
The default prefs for the toolkit should be separated out, so that either
1) we can ship them with the toolkit whenever the standalone
apprunner-with-toolkit becomes reality
2) new-toolkit apps can just take toolkit-prefs.js and stick it in their default
prefs directory
Unforunately this seapartion process is rather painful because I can't always
tell where gecko stops and the toolkits starts, or where the toolkit stops and
the app starts. The lines are fuzzy, but I'll make a stab at it.
Updated•21 years ago
|
Assignee | ||
Updated•20 years ago
|
Priority: -- → P3
Target Milestone: --- → mozilla1.9alpha
Assignee | ||
Comment 1•18 years ago
|
||
We're no longer making a clean distinction between "gecko" and the toolkit.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•