Guidance for Web Site designers to ensure interoperability w/1Password?
Do you have any guidance for web site developers like myself on how to ensure that the web sites we develop are fully compatible with the 1Password browser extensions? I'm especially interested in how I can ensure that our users can easily and accurately fill in their credit card information.
On a related note I've noticed that 1Password doesn't correctly fill in the expiry date in the credit card form used by the popular checkout service offered by stripe.com. E.g. check out this stripe checkout demo here: https://stripe.com/blog/stripe-checkout. Notice how 1Password only fills in the expiry month although the form expects month / year together in one form field.
Comments
-
Do you have any guidance for web site developers like myself on how to ensure that the web sites we develop are fully compatible with the 1Password browser extensions? I'm especially interested in how I can ensure that our users can easily and accurately fill in their credit card information.
Here is a sample form to give you some idea: http://cdn.agilebits.com/sh/cardtest.html
But you should also be fine if you are following the ECML spec: http://tools.ietf.org/html/rfc4112
On a related note I've noticed that 1Password doesn't correctly fill in the expiry date in the credit card form used by the popular checkout service offered by stripe.com. E.g. check out this stripe checkout demo here: https://stripe.com/blog/stripe-checkout. Notice how 1Password only fills in the expiry month although the form expects month / year together in one form field.
We've made changes to the filling in the past to accommodate Stripe. They must keep changing their form(s). :) I'll pass this along to the developers for resolution in a future update. Thanks!
0 -
Do you have any more guidance? Is there any place I can test my form online? I can't change the input element name attributes on my form. Is there a list of "names" you support? Do you support "January" instead of "01", etc. Thanks!
0 -
Hi,
I'd also like to see guidance for web developers to ensure interoperability with 1Password's autofill (and thinking bigger, with alternatives as well).
Of note, 1Password saves the url where an account is created. I've started to use 1Password's "open and fill" more, but I need to change many urls to the login url. It would be nice if developers could tell 1Password what url to use via a hidden field (or I suppose just use the same url for both).
Thanks,
Nathan.0
