New in-page menu feature doesn't work

toomanyairmiles

So you've started trying to edit the password page of sites to add in a 1password menu, leaving aside that this is an appallingly bad idea because it won't load right away the problem is the failure mode.

On sites where it doesn't work e.g. Google and reddit attempting to use autofill from the browser plugin opens a new tab where it fails for a second time.

Even worse, Opening a private window in firefox and attempting to use autofill results in it opening a new tab in the main window where it also fails to autofill.

How do I turn this ugh, 'feature', off?

Latest version of all.

Edit: To add to the above the menu doesn't work on your own community site, and now every time I edit my wordpresses their menu fields are chock full of 1password menus. This is stuff testing is supposed to fix!

---

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided

kaitlyn

Hey @toomanyairmiles 👋

Thanks for letting us know you ran into this! In an attempt to reproduce the issue, I tried out the password change flow on Reddit. That said, I had no luck in reproducing, so I've got a few questions for you.

• Just to double check, are you using the version 2.0.2 of 1Password in the browser?
• What's the website URL you have listed in your Reddit Login item in 1Password?
• Could you provide the steps you're taking to reproduce the issue along with what browser you're using?

I'm hoping those steps to reproduce will help me get to the bottom of it.

As for filling in a private window in Firefox, I did want to bring that up. While in private browsing mode, Firefox prevents extensions from accessing the local database, which 1Password relies on in order to function properly. There are other options available in Firefox's settings that you're welcome to experiment with.

toomanyairmiles

I'll repeat the actual question. How do I turn off these useless in page menus?

What have you done to the browser extension? Two clicks to access the generator?! What on earth is wrong with your UX team!

toomanyairmiles

Regarding the Firefox problems, in a further flash of brilliance from your devs, you've managed to install a completely new version of the browser extension in addition to the old one, resulting in v4x where I expected it and a new version hidden elsewhere.

How can I obtain an old version of the application while you guys fix this dogs breakfast?

I had to train a friend in using 1password this afternoon and the stupidity of this update ruined the session. Nothing is where it should be, the visuals are cramped, broken in places, high friction, and half assed! It's not even prompting for passwords properly because you're now trying to do it inline and in a manner which conflicts so badly with the chrome password manager that it doesn't make any sense at all.

Why do you people always do this - we finally got on a stable track for a while without every update breaking the browser plugin and now we have a UX change no one wanted.

kaitlyn

@toomanyairmiles – You're welcome to disable the inline menu by right clicking on the 1Password icon in your browser toolbar, then select Settings. After that, disable the "Offer to fill and save passwords" option under the Autofill section.

Thanks for sharing your feedback with me. The inline menu would definitely come in handy when filling new passwords. It should appear in any new password field and offer a suggested password with one click (with the above setting enabled). Without the inline menu, you can still fill a password by clicking the 1Password icon in your browser toolbar, then click the Autofill button in the second screenshot below.

Here's an example of filling a password via the inline menu:

And via the pop-up:

We do still offer the Classic extension, which you can install here. I would suggest giving the new browser experience a shot, though, if you're willing. While it's different than what you may be used to, it's more intuitive experience in a lot of ways.

If you have any other questions, don't hesitate to reach out.

toomanyairmiles

An inline menu might be a good idea, but only if you could programmatically determine which form fields are login fields and which are not with 99% accuracy. Unfortunately it's painfully clear that you cannot do that and anyone who has used your product should know that for themselves. The result of this fools errand of an update is 1password attempting to fill in form fields in the backend of wordpresses, search fields in gmail, and a host of other foolish places.

Equally if, like me, you are a web developer you don't want your password extension interfering with the body content of a web page because that's just another thing to debug.

You persistently fail to consider users like me who administrate multiple sites and as a consequence store thousands of passwords. When I log into google I have to deal with 30 different logins - not something achievable in a context menu.

Since you fail to address the point, how can I downgrade to a usable version of 1pass while I wait for you to fix this mess?

toomanyairmiles

To add to this, you need to make filling passwords and offering to save password separate options after this disaster, I want it to offer to save passwords - I do not need your lame attempts to incorrectly guess what is and isn't a login field.

kaitlyn

@toomanyairmiles – I appreciate you voicing your concerns. It means a lot that you'd take the time to do so. I see where splitting up the "Offer to fill and save passwords" would come in handy, and I've passed your thoughts along to the rest of my team.

In case you missed it in my last post, we do still offer the Classic extension, which you can install here. If you have any questions about reverting back to the Classic extension, I'll be here for you!

ref: dev/projects/customer-feature-requests#330

toomanyairmiles

I already had what you call the classic extension installed, which was working perfectly right up until you decided to automatically install this new mess whereupon it immediately broke the classic extension functionality (the issues I posted about originally). This means as far as I can tell even if I install the classic extension again you'll just auto update it away.

I fail to understand a great deal about the situation you've caused - why would you need a new extension when it delivers poorer UX and functionality than the original, why would you force the installation of this new extension, what on earth made you think of hiding the generator and making a bigger search box (a search box which is never used in the browser extension) count as improvements, why do you think making things bigger within the same space counts as an improvement.

The original 1password extension and engineering were brilliant, so far all you've managed to deliver through updates is broken software and poorer UX. You've consistently managed to make good software worse over a period of years.

kaitlyn

@toomanyairmiles – I'd be happy to help get you set up with the Classic extension again. Our new extension is a completely separate download, so there isn't a way to auto-update from the Classic extension as far as I know. If you haven't already, go ahead and remove the extension with a version number of 2.0.2.

Once you've done that, please give your computer a restart so we're working from a clean slate. Please test the connection between the Classic extension and the 1Password desktop app. Are you able to fill an item, or are you seeing the same behavior as previously? If you're still seeing the same behavior, I'd love to grab some steps to reproduce the issue from you so I can attempt to reproduce on my machine.

toomanyairmiles

I didn't install the new v2.02 extension - I saw an auto update message as I started the browser, the classic extension started exhibiting the weird behaviour I described at the start of this thread, and then I found that you had auto-installed the v2.02 extension but hidden it from the browser toolbar.

On my laptop the same auto update ran and (as per normal) simply broke the connection between the v4x extension and the 1password application meaning I had to reinstall the browser plugin from scratch.

So the problem now is that even if I install the more functional classic extension, your software will break it again.

ag_yaron

Thank you for the additional information and feedback here.

If the connection between the desktop app and the classic extension is broken, which can occur if the browser has a pending update or if the desktop app just updated, then you will get a message from the desktop app asking you to install the extension. When clicking that suggestion to install the extension, it will take you to our downloads page here: https://1password.com/downloads/mac/#browsers

Clicking on your browser's icon in that page will download and install the new 1Password in the browser. Instead of doing that, simply restart 1Password and your browser (or restart the computer if you find that easier) and the classic extension will regain functionality.

I hope you won't encounter the issue again, but if you do - a simple restart to 1Password and Firefox (or the computer) should do the trick for you.