1Password is not autosaving logins for Meteor.js apps
Many Meteor.js apps are using the Accounts package (http://docs.meteor.com/#accounts_api). You can see an example of its use here: https://atmosphere.meteor.com (look in the upper right corner). These login forms don't save to 1password. The form seems to fill fine once the info is in 1Password.
I just thought it might be worth discussing if this is something that Agilebits can do to help resolve or if it is something that the Meteor community can do to improve things on the Accounts package side. Thanks!
Comments
-
Hi @shrop,
Thanks for starting the discussion here! The type of sign-in page that you mention does present a challenge for 1Password, primarily because the sign-in occurs in a pop-up. In cases like this, there is essentially nothing for 1Password to fill until that 'sign-in' button is pushed and the username and password fields appear.
There's not much that we can do on our end, but there is a way that web developers can make sign-ins like this more 1Password-friendly. The html code for the site needs to include a
<form>
element. This element can be hidden or invisible to the viewer until the 'sign-in' button is pressed, but the code needs to be present on the page so that 1Password can find it. Now I'm not a developer myself, so please forgive me if this sounds a bit off, but this is how I understand it.I hope this helps, but if you have any further questions, don't hesitate to ask!
0