Browser Extension and Minimize?

cuppscakes
cuppscakes
Community Member
edited April 2023 in 1Password 7 for Windows

Finally getting around to trying out the Windows Beta (running 6.0.158d, installed standalone), and got two questions:

1.) Apologies, as I've seen it referenced, but can I get an official, current, response: do browser extensions (namely Chrome) work with the Windows Beta? The "Register Browser Extension Helper" button does nothing (disabled, per an older thread?), and any combination of installing/uninstalling/opening/enabling the Chrome extension and Windows Beta result in either a)clicking the extension button spawning new windows (locked) over and over or b)a simple "No matching items found" message. Nothing I've tried works. Tried with both regular and beta extensions, FWIW.

1b.) Minor quibble, but one thread said the work-around was to click "Browse" in the 1Password client. I manually entered my logins using "google.com" in lieu of "http://google.com" or "https://www.google.com" or any variant. Seems that, sans http://, the Browse button doesn't work. Any chance of fixing that (I don't fancy editing hundreds of logins, nor figuring out if I need http:// or https:// for each)?

2.) Can I minimize the Windows Beta to my system tray? Or otherwise move it to the background. I'm fine if I have to wait on browser integration, but if I have to keep the application actively on my desktop, it's a bit of a pain. Any word of minimize or close-to-tray options, like every other version/release?

Thank you!


1Password Version: 6.0.158d
Extension Version: Stable/Beta
OS Version: Windows 10
Sync Type: Families

Comments

  • AGAlumB
    AGAlumB
    1Password Alumni

    1.) Apologies, as I've seen it referenced, but can I get an official, current, response: do browser extensions (namely Chrome) work with the Windows Beta? The "Register Browser Extension Helper" button does nothing (disabled, per an older thread?), and any combination of installing/uninstalling/opening/enabling the Chrome extension and Windows Beta result in either a)clicking the extension button spawning new windows (locked) over and over or b)a simple "No matching items found" message. Nothing I've tried works. Tried with both regular and beta extensions, FWIW.

    @cuppscakes: Sorry for the confusion! Extension support is still very basic. When you launched the 1Password 6 beta app, it should have given you the option to register it to use with the browser extensions. If you said yes, that will make things slightly easier (especially if you have 1Password 4 installed). Otherwise you'd need to kill the old app in Task Manager for the extension to connect to the beta. You'll need to have 1Password 6 running, and then click the 1Password extension button in the browser to have it fill.

    1b.) Minor quibble, but one thread said the work-around was to click "Browse" in the 1Password client. I manually entered my logins using "google.com" in lieu of "http://google.com" or "https://www.google.com" or any variant. Seems that, sans http://, the Browse button doesn't work. Any chance of fixing that (I don't fancy editing hundreds of logins, nor figuring out if I need http:// or https:// for each)?

    You can use the Browse button in the beta to open the webpage, but you'll need to use the extension button as I described above to fill the login. I wasn't able to reproduce this "http://" issue you're describing. Can you give me the exact steps, including the URL and browser version you're using. It's definitely not advised to fill login credentials on an insecure (http://) webpage, but it's something I'd like to look into in case there's a bug there that needs to be addressed.

    2.) Can I minimize the Windows Beta to my system tray? Or otherwise move it to the background. I'm fine if I have to wait on browser integration, but if I have to keep the application actively on my desktop, it's a bit of a pain. Any word of minimize or close-to-tray options, like every other version/release?

    The 1Password 6 beta is currently a single app, so there's no separate component that can be run in the background when you close it. Having a notification icon for it is something we'll explore in the future though, but as you can see we have a lot of work to do on browser integration still and that's our top priority. :)

This discussion has been closed.