Closed Bug 9030 Opened 25 years ago Closed 14 years ago

[FEATURE] Need to recognize profile's config.ini & setup DUN

Categories

(Core Graveyard :: Profile: BackEnd, defect, P3)

x86
Windows 98
defect

Tracking

(Not tracked)

RESOLVED WONTFIX
Future

People

(Reporter: selmer, Assigned: ccarlen)

Details

In all prior versions, the browser will change the default connectoid to match the one specified in the profile's config.ini file. The 5.0 release must also do so. There should be some code to steal from the 4.x release to implement this.
Status: NEW → ASSIGNED
Target Milestone: M9
Seting TFV to M9.
Target Milestone: M9 → M10
Dialer related stuff just getting in to the picture. Moving TFV to M10.
P3s aren't going to make it in M10. Bulk moving to M11.
Blocks: 12696
Summary: Need to recognize profile's config.ini & setup DUN → [FEATURE] Need to recognize profile's config.ini & setup DUN
Added [FEATURE] to summary.
Target Milestone: M11 → M15
Taking care of dialing related in the post-beta session. Moving the TFV to M15.
These bugs are not critical for beta 1, moving out.
No longer blocks: 12696
Component: Profile Manager → Profile Manager BackEnd
Moving all Profile Manager bugs to new Profile Manager Backend component. Profile Manager component to be deleted.
Target Milestone: M15 → M17
Moving this to M20.
Target Milestone: M17 → M20
Doing a mass reassign to Conrad Carlen. Conrad is going address all current and upcoming profile manager issues. Please do not hesitate to involve me in any of the issues.
Assignee: racham → ccarlen
Status: ASSIGNED → NEW
This is very old. Since we've lived with for so long, putting it off further. Let me know if it's a higher priority than I think.
Target Milestone: --- → Future
Can't this one be closed? I don't think config.ini is still used
QA Contact: agracebush → profile-manager-backend
Best to close it before the last person who remembers what DUN stands for dies.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.