*shrug* moving from profile-do-change to profile-after-change per conrad's suggestion - this seems to fix the blocker for me, what's the worst that could happen? :)

This commit is contained in:
alecf%netscape.com 2001-11-28 23:40:45 +00:00
parent 4e4eb22081
commit 523be41c46
2 changed files with 4 additions and 4 deletions

View File

@ -354,7 +354,7 @@ nsChromeRegistry::Init()
do_GetService("@mozilla.org/observer-service;1", &rv);
if (observerService) {
observerService->AddObserver(this, "profile-before-change", PR_TRUE);
observerService->AddObserver(this, "profile-do-change", PR_TRUE);
observerService->AddObserver(this, "profile-after-change", PR_TRUE);
}
CheckForNewChrome();
@ -3180,7 +3180,7 @@ NS_IMETHODIMP nsChromeRegistry::Observe(nsISupports *aSubject, const char *aTopi
rv = userChromeDir->Remove(PR_TRUE);
}
}
else if (!nsCRT::strcmp("profile-do-change", aTopic)) {
else if (!nsCRT::strcmp("profile-after-change", aTopic)) {
if (!mProfileInitialized)
rv = LoadProfileDataSource();
}

View File

@ -354,7 +354,7 @@ nsChromeRegistry::Init()
do_GetService("@mozilla.org/observer-service;1", &rv);
if (observerService) {
observerService->AddObserver(this, "profile-before-change", PR_TRUE);
observerService->AddObserver(this, "profile-do-change", PR_TRUE);
observerService->AddObserver(this, "profile-after-change", PR_TRUE);
}
CheckForNewChrome();
@ -3180,7 +3180,7 @@ NS_IMETHODIMP nsChromeRegistry::Observe(nsISupports *aSubject, const char *aTopi
rv = userChromeDir->Remove(PR_TRUE);
}
}
else if (!nsCRT::strcmp("profile-do-change", aTopic)) {
else if (!nsCRT::strcmp("profile-after-change", aTopic)) {
if (!mProfileInitialized)
rv = LoadProfileDataSource();
}