Open and Fill appends /? characters

cheule

In 1Password for Mac, version 6.1 from Mac App Store, if I click on a website URL to "open and fill" in the 1Password main application, it appends erroneous /? characters that prevents the website from opening properly in some cases.

Example: I click on http://www.gmail.com but http://www.gmail.com/? is what is sent to safari.

---

1Password Version: 6.1
Extension Version: 4.5.3
OS Version: 10.11.3
Sync Type: iCloud

littlebobbytables

Hello @cheule,

This isn't actually 1Password for Mac's fault. It's actually sending two parameters after the ? that you aren't seeing and that are vital for the 1Password Browser Extension to know this is a URL sent by 1Password. What happens is there is an event that gets fired in the browser even before it attempts to load the URL. At this point the extension strips away the additional parameters and we have a fix in the beta version of the extension that properly removes the additional ? which isn't being correctly done in the current stable. It means the next stable release of the 1Password Browser Extension should resolve this issue.

As an aside, I would recommend updating the URLs if you currently have http://www.gmail.com stored in your Login item. That URL is redirected to https://accounts.google.com/ServiceLogin?service=mail&passive=true&rm=false&continue=https://mail.google.com/mail/&ss=1&scc=1&ltmpl=default&ltmplcache=2&emr=1&osid=1#identifier which is Google's current login page and you can see the parameter that will redirect you to mail.google.com.

So we've got a fix in the works that the next stable release will fix. Hopefully that won't be too far away :smile: Does any of this help at all in explaining the situation?

cheule

This totally makes sense, and the fact is that I even thought the issue might lie with the extension, which is why I was diligent in citing which extension version I was using.

Thanks for you superlative response.

littlebobbytables

Superlative - I love it :chuffed:

Glad I could help clear that up @cheule and I'm hopeful we're near a new stable version for the extension, we just need to make sure some changes we've been making on the Firefox side of things are good :smile: