Closed Bug 7583 Opened 25 years ago Closed 24 years ago

[FEATURE]Need continued support for profile.cfg

Categories

(Core :: Preferences: Backend, defect, P3)

Product:
Core
Component:
Preferences: Backend
Platform:
All
Other
Type:
defect

Tracking

()

Status:
VERIFIED INVALID

People

(Reporter: selmer, Assigned: neeti)

References

Details

In 4.x, there was support for the profile.cfg file.  It was basically the same
as a netscape.cfg file, except it lived in a profile.  This helps solve problems
when distributing Communicator since the distributor can lock prefs in the
profile without worrying about changing the behaviors of other profiles.

The CCK product needs this.
Blocks: 7579
Target Milestone: M9
John, are you planning to do this in your pref initialization work?
We're not even sure whether netscape.cfg will be supported in mozilla. It may
belong only in the commercial build.

This is all a big unknown to me, so far.
If netscape.cfg became commercial-only, then this would too.
Status: NEW → ASSIGNED
Assignee: don → dp
Target Milestone: M9
dp, can your team handle this issue?
Assignee: dp → neeti
This is a feature neeti. Maybe you have 8 bugs on this already. I will let you
mark it dup if you find another
Status: NEW → ASSIGNED
Target Milestone: M10
Summary: Need continued support for profile.cfg → [FEATURE]Need continued support for profile.cfg
Blocks: 11408
Target Milestone: M10 → M11
Moving tagett milestone to M11
Target Milestone: M11 → M15
Moving to M15
Moving all libPref component bugs to new Preferences: Backend component.  
libPref component will be deleted.
Component: libPref → Preferences: Backend
Target Milestone: M15 → M16
spam: moving qa contact on some bugs from paulmac to sairuh@netscape.com
QA Contact: paulmac → sairuh
This bug is no longer valid as per discussion with selmer.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
verif.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.