I have written before about how 1Passwd has a Better AutoFill Than Safari. While I am obviously biased, it seems I am not alone in finding the quirks in Safari hard to live with.
Sven discusses problems with Safari’s Autofill:
But there is a little problem with it. The automatic filling of the user name and password fields only takes place after a page has been completely loaded. And by "completely loaded" I mean that all of the page's elements such as images have been loaded — not just the HTML. And, you know, sometimes web sites are quirky. One of those little images gets stuck somewhere on the way; an ad-server is slow; you're on a slow internet connection; the site is on an encrypted connection — which often means it is generally slow, particularly when all of those little spacer-gifs are also served using the encrypted connection. Any of these reasons can cause the time until the page is completely loaded to be rather long, much longer than the time it takes to download the HTML and much longer than it takes Safari / WebKit to display a preliminary version of the page. So you end up seeing those empty login fields and expect them to be automatically filled with your user name and password but nothing happens ... nothing happens ... nothing happens ... ahhh, there it is
I had never noticed this problem because I am always on a DSL line. I will need to make sure 1Passwd doesn’t suffer the same problem.
Recent Comments