- From: Jonas Sicking <jonas@sicking.cc>
- Date: Thu, 12 Dec 2013 13:21:41 -0800
- To: Joel Weinberger <jww@chromium.org>
- Cc: Webapps WG <public-webapps@w3.org>
On Dec 12, 2013 11:21 AM, "Joel Weinberger" <jww@chromium.org> wrote: > What are this group's thoughts on this? Any particular concerns with this approach? I like the approach. The issue in the past has been that banks were extremely worried about the formfill feature in browsers. To the extent that they would blocklist browsers that didn't honor autocomplete="off". Of course, that was a long time ago. Things might have changed. If nothing else, marketshares have changed. They would have a much harder time to blocklist Chrome or Firefox today then they did back then :-) But it would suck if the result is that they create their own form fields using <div>s and/or contenteditable. Reaching out to banks might be good. Is that something you've looked at? And at minimum making a better implementation of form autocomplete sounds like a good thing. Sounds like you've done that. Though you might also want to make sure that the remembered username/password is stored in an encrypted form. / Jonas
Received on Thursday, 12 December 2013 21:22:39 UTC