Closed Bug 104021 Opened 23 years ago Closed 23 years ago

Profile mgr needs to put necko offline when switching profile

Categories

(Core Graveyard :: Profile: BackEnd, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED
mozilla0.9.6

People

(Reporter: ccarlen, Assigned: ccarlen)

References

Details

Attachments

(1 file)

This came from bug 101329 - summary says it all. We need to put necko offline and then wait until receiving notification that it really is offline before proceding with shutting down the profile. For that, see bug 104020.
Status: NEW → ASSIGNED
Depends on: 104020
Target Milestone: --- → mozilla0.9.6
Blocks: 101329
Attached patch patch 1Splinter Review
Comment on attachment 56684 [details] [diff] [review] patch 1 how about just renumbering the Phases? :-)
Attachment #56684 - Flags: review+
Attachment #56684 - Flags: superreview+
Comment on attachment 56684 [details] [diff] [review] patch 1 rs=darin
Kai - drivers have requested another review for this to go into 0.9.6. Can you do it? Between this and bug 104020, all net activity should now be stopped when the NSSComponent gets the profile-before-change notification.
You are only adding a new notification, that is currently not used anywhere. But the code is required for the fix that I will produce for bug 104020. You notification is currently not used and therefore can't cause any trouble for 096. r=kaie
Kai, I'm not sure what you mean. This notification will be used by the code which was checked in for bug 104020. That patch is in place and the bug is closed.
I should have updated my tree before using grep to search it for the new notification string you added... Ok, your patch will already trigger necko to go off or back online. That's what we want and your patch looks good. r=kaie
a=asa (on behalf of drivers) for checkin to 0.9.6
Keywords: mozilla0.9.6+
I'm marking this fixed, as the code seems to have landed on the trunk.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Removing blockage of 104864 because this is in 0.9.6. It was checked in before the branch was cut.
No longer blocks: 104864
Re-adding the 0.9.6 tracking bug since we need to keep track of all of the 0.9.6 bugs that were labeled as such. ( This is closed - it's OK. )
Blocks: 104864
Verified code fix
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: