With the fix of bug 247919 Camino supports the wallet.crypto.autocompleteoverride hidden preference, but Camino still fails to handle some authentication fields inside HTML frames. This is reported using 0.8.1. I'm not certain yet if it matters whether or not autocomplete="off" has anything to do with this. I'll try to construct some test cases.
Okay, has nothing to do with bug 247919. Camino simply fails to access stored Keychain data for form fields in HTML frames. See the testcase URL.
(Note that Camino *will* prompt to store changed values if the user enters new data.)
yeah, this is a known issue. this may already be a dupe, i'm not certain. we need to fix this regardless for 0.9.
Dup of bug 186384
*** This bug has been marked as a duplicate of 186384 ***