Well... the good news is I went to 5 sites and they all
populated OK.
But it was really broken on every site I went to the other
day, and I
definitely restarted a couple of times. To answer your
questions the
new duplicated passwords were working correctly. Weird. I
will keep an
eye on the console if it starts up again.
BTW - I have the old wallet.crypto.autocompleteoverride
setting on,
because I want to save passwords for the sites I decide
thankyouverymuch.
On May 26, 2008, at 3:58 PM, Stuart Morgan wrote:
> On May 26, 2008, at 9:09 AM, Andrew Thompson wrote:
>> So of late I notice that autofill for passwords is
no longer working.
>> Extremely irritating.
>>
>> I've figured out if I re-enter the password, I get
a new, duplicate
>> entry in my Keychain, with the type "Web Form
Password" and
>> camino_default in the comments.
>>
>> Um, is this intentional or a bug? Did the way
passwords are stored
>> really change in a non-backwards compatible?
>
> There was certainly no intentional breaking of
backwards
> compatibility, and we did quite a bit of testing, but
there were a lot
> of changes to the Keychain code and some cases may have
slipped
> though. Once you have stored a duplicate password, does
that fill
> correctly, or does nothing fill either way? Does
Console show anything
> when you try to access a site where you have a stored
password that
> doesn't fill (using 1.6.1, where we added extra logging
of Keychain
> errors)?
>
> -Stuart
> _______________________________________________
> Camino mailing list
> Camino mozdev.org
> https:
//www.mozdev.org/mailman/listinfo/camino
AndyT (lordpixel - the cat who walks through walls)
A little bigger on the inside
(see you later space cowboy, you can't take the sky from
me)
_______________________________________________
Camino mailing list
Camino mozdev.org
https:
//www.mozdev.org/mailman/listinfo/camino
|