Closed Bug 273239 Opened 20 years ago Closed 20 years ago

Camino fails to access stored Keychain data for form fields in HTML frames

Categories

(Camino Graveyard :: General, defect)

Product:
Camino Graveyard
Component:
General
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 186384
Milestone:
Camino0.9

People

(Reporter: bugmail, Assigned: mikepinkerton)

References

(
URL
)

Details

(Keywords: testcase)

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.
URL: http://www.ba-ca.com/en/ → http://greg.tcp.com/mozilla/Test%20Ca...
No longer depends on: 247919
Keywords: testcase
Summary: Form autocomplete sometimes fails in HTML frames → Camino fails to access stored Keychain data for form fields in HTML frames
(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.
Target Milestone: --- → Camino0.9
Dup of bug 186384
*** This bug has been marked as a duplicate of 186384 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.