found while using the following: linux, opt comm: 2000.03.27.11 macOS, opt comm: 2000.03.27.10 winNT, opt comm: 2000.03.27.09 to repro: 1. start browser. 2. go to Tasks > Personal Manangers > Password Manager > View Stored Passwords OR open Preferences > Forms and Passwords > View Stored Passwords. result: a blank dialog window appears. the only difference btwn access from menu and access from Prefs is that the dialog that appears via Prefs is maximized. expected: Password Viewer dialog should display its content. this is what i see in the console (taken while using linux build): XML Error in file 'chrome://wallet/content/SignonViewer.xul', Line Number: 75, Col Number: 31, Description: undefined entity Source Line: value="&removeall.label;"
Fix checked in.
was able to verify as fixed on winNT and linux [opt comm, 2000.03.29.09], using an existing profile. however, on macOS the View Signons dialog would *not* appear when i used an existing profile. (it did work when i used a fresh profile.) am i running into another [existing?] bug here?
after chatting w/steve, i copied the mac profile in question to my winNT to see what would happen: still unable to open the View Signons dialog, even using today's opt comm bits on winNT. will attach the zip'd up profile soon...
Using your zipped up profile, I had no trouble opening the signon viewer on my NT browser.
even though i've only seen this problem on the mac (so far), i wonder if this particular bug might be in any way related to bug 33613. i see similar problems trying save signons with an existing profile, ie, the same profile in which i see this bug.
Bug 33613 is now resolved; see it for my explanation of what I think happened. Gerv
Closing this out as fixed since the original problem had indeed been fixed (there was an entry missing for "removeall.label" in the commercial tree only). The bug was then morphed and reopened as a problem having to do with old profiles. This should have been a new bug report. If that is still a problem, then open a new bug on it. But as I was unable to reproduce that problem, and as it had to do with an old profile only, I don't think we have to worry about it reoccuring.
hokay. i'll file another bug about this not working for an existing profile on Mac, and verify this one with its original summary.