no autofill, even though data already in keychain

RESOLVED WONTFIX

Status

Camino Graveyard
OS Integration
--
major
RESOLVED WONTFIX
15 years ago
15 years ago

People

(Reporter: kingwhistle, Assigned: Simon Fraser)

Tracking

Details

(URL)

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.0.1) Gecko/20030306 Camino/0.7
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.0.1) Gecko/20030306 Camino/0.7

  On the pages listed at the bottom, Camino will not autofill. When I fill it
in, it will ask if I want to store...in keychain...
  Safari will autofill all of these pages.
  When I look into keychain, I find Camino listed several times on each of the
above mentioned pages (why should that be?) as an application allowed to access
(with confirmation).
  I have several other pages which Camino does autofill correctly for.

https://www2.harrisdirect.com/pre/login.htm
https://chaseonline.chase.com/chaseonline/logon/sso_logon.jsp
https://www.firstib.com/onlineserv/HB/Signon.cgi

Reproducible: Always

Steps to Reproduce:
1.Go to site and type in my user id and code
2.no autofill.
3.
4. 
Actual Results:  
no autofill

Expected Results:  
autofill

These are secure sites, so I don't know how to have you reproduce these results,
without you actually having an account in these places. When I try to make up a
fake account just to test out Camino, It says no such user id exists.
 I'm not a developer, just someone who loves your browser, and hates Safari's
lack of import/export/send link. and hates Microsoft, nuff said. I'm afraid ,
though, that without the autofill being usable on these sites, I may have to go
back to that damn Safari. I hope this is something simple. I have tried trashing
prefs several times. no change.
(Assignee)

Comment 1

15 years ago
These sites use autocomplete="off", which Camino respects.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.