1P Mini won't recognise some sites in Chrome, but will in Safari

puffmoike

I have used 1P for many (largely trouble-free) years. I hit Cmd-\ dozens of times a day.

At the moment I am seeing some confusing behaviour for a series of sites I help administer. I often want to be logged in as different users, and use different browsers to achieve this.

If I use Safari to visit subdomain.example.com/login and hit Cmd-\ then 1P successfully logs in.

If I visit the same site in Chrome and hit Cmd-\ then rather than automatically logging in automatically a window opens below the 1P Mini icon in the menu bar, but none of the logins for the various subdomains of example.com appear in a suggestions list like I would expect, so I am forced to start typing to find the appropriate login. If instead I click on the 1P browser extension icon in Chrome 1P works as expected, automatically filling in and submitting the username and password fields.

I have tried a handful of other sites in Chrome and I don't have any problems logging in by simply hitting Cmd-\.

What's going on?

---

OS 10.10.2
1Password 5.1
Safari 8.0.3
Chrome 40.0.2214.111

MikeT

Hi @puffmoike,

We haven't been able to reproduce this consistently. Can you tell me if you can reproduce this on any specific site?

The issue is that the 1Password mini (the listener for the keyboard shortcuts) calls on the extension to pass the URL of the frontmost tab but it doesn't work consistently in Chrome for some reason, it works more reliable in Safari and Firefox.

When you press the icon, you're passing the URL to 1Password mini already as the call starts from the extension to mini. Pressing CMD+\ again almost always work, we haven't figured out why yet.

Generally, if the site is slow at loading and hasn't completed yet, the extension script itself can't run until the site is loaded first. That's why CMD+\ works the second time, the site by that time finished. However, this doesn't sound likely in your case because you said the same site works fine in Safari and it should be more consistent across the browsers if the loading is the issue.

puffmoike

Hi @MikeT,

To be honest I spend most of my time in Safari, where this isn't an issue. I typically only use Chrome for it's developer tools (and I'm not really a developer), when I want to use Adobe's Edge Inspect plugin to view sites simultaneously on my iPhone, or when I want to be logged into the same site as two different users.

The particular site I am having trouble with is communifier.com, and it happens regardless of which of our (private) subdomains I am attempting to login to. I have the exact URL associated with the account details (eg subdomain1.communifier.com/login; subdomain2.communifier.com/login) but hitting Cmd+\ doesn't work with any of them.

EDIT: Of course now I've just tried again to confirm, and it's working fine with both subdomains. I'm none the wiser why it's working now, but hasn't repeatedly over the past few days, including multiple reboots of the computer.

dteare

Thank you for the update, @puffmoike. While I'm happy it is working for you now, I'm also sad that you can no longer recreate this issue as I was hoping we could dig in and find the source of the troubles. Maybe next time :)

I'd like to share a little bit with what's happening underneath the covers and what I suspect is happening. When you press ⌘\, 1Password mini relies on a websocket connection to the foremost browser to ask for it's URL. If the websocket is not connected, we cannot get the active URL and are therefore unable to filter the list.

As Mike said, when you press the 1P browser icon, things behave differently. If the websocket connection is not established, then we'll try connecting to the mini, and once connected, send the current URL into the mini so it can filter the list of logins for you. At this point, ⌘\ will work again because the websocket connection is in place.

So my theory is something is preventing Chrome's websocket from connecting to 1Password mini, or somehow we get into a bad state and lose the connection. If this is the case, you should be able to see an error in 1Password's background page console. You can find this by going to the chrome://extensions/ page and clicking the background page link as shown here:

Next time this happens please see if any errors are happening here.

puffmoike

Hi @dteare (always love to know that my money is going to a software company whose founder is happy to get their hands dirty in the glamorous world of squishing bugs and talking to customers)

I have to admit that you're right on the edges of my understanding.

Using Chrome to view the same websites again today. Almost certain that I logged into subdomain1.communifier.com/login today using just ⌘\ . But I just tried logging into subdomain2.communifier.com/login and 1P Mini didn't recognise the site. Then I clicked on the 1P Chrome extension icon, and whilst it proffered the five appropriate login options for that domain, clicking on the one I wanted didn't achieve anything – it didn't fill in the fields.

At this point I tried to follow your instructions. Here's a screengrab of what I saw

Cheers,
Michael

MikeT

Hi @puffmoike,

That is weird. If you open the subdomain2. site in Safari, 1Password fills it in properly?

If you can reproduce it, can you look in Console to see if there are any errors from 1Password mini. To do this:

1. Open Console.app from the Applications > Utilities folder
2. Click on the Clear Display button on the Console's toolbar and then reproduce the problem with filling onto the subdomain2. site in Chrome.
3. Wait a minute, switch to the Console app, press Command + A to select all logs and then Command + C to copy it.
4. Paste (Command + V) the logs in your reply here or if you want, you can either send it to me in the private message or to us via email at support+forum@agilebits.com. If you're emailing it to us, please include your forum username in the body of the email, so we can find it quickly here.