1Password Browser URL handling bugs

linetrace

I've identified a few URL minor bugs in the 1Password iOS app's built-in browser that tend to compound into larger frustrations for me:

• The URI scheme is stripped off of URLs in the location bar/text field (presumably because 1Password--for good reason--defaults to HTTPS) and doesn't remember the URL's scheme, so when you re-select/edit an originally HTTP URL and hit return to load it'll fail to connect (unless the site support HTTPS).
• Hitting the reload button in the location bar causes the URL that was first entered to be reloaded, not the current URL shown in the location bar.

---

1Password Version: 6.4.4
Extension Version: Not Provided
OS Version: iOS 9.3.2
Sync Type: Not Provided

AGAlumB

The URI scheme is stripped off of URLs in the location bar/text field (presumably because 1Password--for good reason--defaults to HTTPS) and doesn't remember the URL's scheme, so when you re-select/edit an originally HTTP URL and hit return to load it'll fail to connect (unless the site support HTTPS).

@linetrace: Agreed. That's pretty frustrating. Mercifully it isn't something that comes up often these days since so many sites have moved to HTTPS, but when you do need HTTP it's not much fun to have to argue with 1Password about it.

ref: OPI-3678

Hitting the reload button in the location bar causes the URL that was first entered to be reloaded, not the current URL shown in the location bar.

You're absolutely right! Thank you for reporting this. That certainly isn't expected behaviour!

ref: OPI-3677

I also wanted to mention that we have a number of related issues with he built in browser. To some degree, we're limited in what we can do based on the capabilities of the Safari webview we're using, but this is an area where we'd like to improve things. Thanks so much for bringing these up! :)

linetrace

@brenty Thanks for looking into & confirming the issues. I understand some of the limitations of the Safari webview, so try not to expect too much. :)

AGAlumB

Indeed. However, it's definitely something we'll continue to work on, since we don't want anyone to have a frustrating experience, regardless of the cause. Thanks for your understanding. :blush: