Closed Bug 157038 Opened 22 years ago Closed 22 years ago

Password Manager dialog not being updated

Categories

(SeaMonkey :: Passwords & Permissions, defect, P2)

x86
Windows NT
defect

Tracking

(Not tracked)

RESOLVED FIXED
mozilla1.1beta

People

(Reporter: morse, Assigned: morse)

Details

Attachments

(1 file, 1 obsolete file)

Now that password manager dialog has been changed from modal to non-modal, the 
display needs to be updated dynamically whenever the password list changes 
(e.g., when new logins are accepted).

See bug 156922 for similar problem with cookie manager.
Priority: -- → P2
Target Milestone: --- → mozilla1.1beta
Status: NEW → ASSIGNED
Comment on attachment 91559 [details] [diff] [review]
dynamically update password-manager display

sr=jag

Same thing applies here, use NS_LITERAL_STRING("...") instead of
NS_ConvertASCIItoUCS2("...").
Attachment #91559 - Flags: superreview+
Attachment #91559 - Attachment is obsolete: true
Comment on attachment 91588 [details] [diff] [review]
NS_ConvertASCIItoUCS2 changed to NS_LITERAL_STRING

r=jag (brought forward)
Attachment #91588 - Flags: review+
Comment on attachment 91588 [details] [diff] [review]
NS_ConvertASCIItoUCS2 changed to NS_LITERAL_STRING

oops, I meant sr=jag (brought forward)
Attachment #91588 - Flags: review+ → superreview+
Comment on attachment 91588 [details] [diff] [review]
NS_ConvertASCIItoUCS2 changed to NS_LITERAL_STRING

r=sgehani
Attachment #91588 - Flags: review+
One clarification.  Line 1907 in singsign.cpp which in the latest patch reads

   os->NotifyObservers
      (nsnull, "signonChanged", NS_LITERAL_STRING(state).get());

should instead read

   os->NotifyObservers
      (nsnull, "signonChanged", NS_ConvertASCIItoUCS2(state).get());

I got a little too overzelous in interpreting jag's comments when I converted 
the patch in comment 1 to the patch in comment 3.
One more minor correction.  In nsPasswordManager.cpp the patch shows:

   return ::SINGSIGN_RemoveUser(PromiseFlatCString(aHost).get(),
-                               PromiseFlatString(aUser).get());
+                               PromiseFlatString(aUser).get(), PR_FALSE);

The added parameter should be PR_TRUE instead of PR_FALSE.  This controls 
whether or not update notifications get sent when the password manager is 
directed to remove a user.  Without a PR_TRUE here, the dialog will not get 
updated.
Keywords: nsbeta1
Fix checked in on trunk
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: