Issues with Safari extension
Long time 1Password user here. Have tried 1PW8 Safari extension from time to time, don't like it, turn it off, and then try again 6 months to a year later, find that nothing has changed, and shut it off again.
Maybe by now old-timers who feel like me have abandoned 1Password.
It changed everything i liked about the "inline behavior" of the 1PW7 app extension.
- Is there really no way to accept auto-fill suggestions with the keyboard? The suggestion(s) are below the user name field, and I find the arrow keys won't let me reach there to select an option. If I press Return, the top suggestion (which is 99% of the time the only match to the site) isn't selected. ONCE IN A WHILE, I have found I can press Tab to reach the suggestion, but that is rare. I have to use the mouse - which is why I have always reverted back to using CMD\ with the non-browser-extension autofill (I don't know what you call that, since it also listed among my Safari extensions).
- A large percentage of the time, after logging in using 1PW8 browser extension, 1PW then offers to save the login. This is a disturbing pop-up - I made no change, why would I want to say "yes" to that prompt? I always dismiss this unnecessary and misleading pop-up. This is despite my selection in the extension settings, "Autofill & save tab", to NOT "Offer to save logins" - which is explained as offering to save pre-existing logins. Why would anyone want to do this, and it seems it is incapable of honoring my choice in any event.
- When I am presented with a field to enter a 1-time code that is texted to me, 1PW extension always provides suggestions in the field. But - the field has no relevance to 1Password, and again, this disturbs me - because 1Password is not recognizing what kind of field this is.
- If I disable or uninstall the browser extension, the regular CMD\ autofill works, but often very slowly. Is this an automation script? It seems to fill the fields one character at a time, as if Safari invokes it repeatedly for each character. And sometimes it takes 10 seconds to react - as if, after some time period, the script is removed from memory, and takes some time to be reloaded. Besides being slow and ugly, is this automation actually secure?
- Back in the 1PW7 days, 1Password stated there would never be a browser extension per se, just the app extension, because Apple said a browser extension couldn't do the job and wouldn't be secure. How has that changed? Unlike in 1PW7, Safari warns for both 1PW extensions that they can read and alter web pages.
- The browser extension still offers very little help for most of the settings. Why have you never given a "?" link, or pop-up help, or more text under every setting, or a direct link to a specific web page that explains each option of the settings on a particular tab? Nor have I ever found a set of well-organized page on your web site. It seems that though you made the Safari browser extension the main way to interact with 1PW, it's been left as a weird afterthought, with a bunch of ill-defined options that aren't explained anywhere. One example: What are the differences between "Offer to save and fill logins and other items", "Offer to save items in autofill suggestions", "Offer to save logins", "Offer to save contact information" etc.? There are so many overlaps that are completely unexplained and I just don't understand the effect of these different options.
- After generating an updated password, you offer to save the password before the site itself has actually accepted the password.
Are there solutions to any of the issues I've raised?
I'm also interested in knowing what the business purpose was of so radically changing the architecture from 1PW7 to 1PW8? It's like there was a total change in ownership, management or technical leadership that decided, for some reason, that all these changes would be for the better.
