Support for Orion Browser

Hey @the_lucifer ,

The desktop app won't connect to any browser that is not pre-approved by us, so that's out of the picture for now.
One of our devs have taken a quick look at Orion and saw it is a Safari web view with the extensions API implemented in it, so it is basically a big mesh of different pieces of software bundled up into a web view window.

1Password in the browser doesn't function correctly in it as there are functionalities missing in that browser that our extension utilizes. That might also be the case with the Classic extension if it were to connect to the desktop app in that browser.

So as of now, 1Password can't autofill in Orion, nor can you perform other actions such as getting to the extension's settings and more.

@anquieta , Firstly, I think you'll find this quite insightful regarding the future of local vaults: https://1password.community/discussion/comment/602340/#Comment_602340

And secondly, I don't think that the system-wide autofill that Apple introduced would work in other browsers but rather in other 3rd party apps that are not browsers. However, I hope I'm wrong and that would be indeed possible :)

@ag_yaron I understand the push to use 1Password in the Browser. As a user of standalone, iCloud synced vaults, I would very much appreciate if the classic extension could be updated to whitelist Orion.

Either that or 1Password 7 follows through on using system-wide autofill that Apple introduced in Big Sur, per here: https://blog.1password.com/autofill-on-big-sur/

Thank you.

Hi, so I dived a bit into why it's not autofilling. There's two issues here:

1. The Desktop app seems to respond to the extension that the browser is not verified. (Same thing happens with the 1password classic extension). Screenshot from the extension logs is attached:

1. There's no way to reach 1Password's settings from the icon (This seems to be an Orion issue, right clicking and choosing Settings does nothing). Is there a direct url to visit 1Password extension settings?

Thanks for the info @hakusaro .

I'll ask our developers to take a look and see if they can figure this out on our side of things.
As for the stuck loading screen, try right-clicking the extension's icon in the browser's toolbar -> Settings -> Turn off the "Integrate with 1Password app" option there.

@ag_yaron same behavior on all websites, as far as I can tell. I just picked a random site to test with.

The other thing that happens intermittently is that it takes an inordinate amount of time to login. That is to say, 1Password displays the loading spinner in the extension sometimes forever, but works on a new tab after a short delay.

Other Orion users also experience this problem, too, fwiw, but I don't think that it's been brought up too heavily.

Thanks for the screen recording @hakusaro ,

Does this issue occur on every website, or only on streamable.com? If it occurs on every website, then there's definitely something in that browser that doesn't play well with the extension, and I'll ask our devs to take a look at it.

As for your feedback here, you can make this new extension work more similarly to the old classic extension by disabling its inline menu in the extension's settings, that way it will not show up on its own inside/under fields. You can also adjust its keyboard shortcut in the settings page, but before we get to that, let's see if we can make it work in this browser.

Let me know if the issue in your video is unique to this website or to any/all websites.

@ag_yaron this is the behavior I see trying to autofill: https://streamable.com/rjo383

Note: yes, I did cancel the privacy dot com card, but I'm too lazy to re-record the video and hide the credit card. So, don't worry about that.

I would also say that the privacy card generation flow doesn't work either (pressing autofill does nothing).

With respect to the old vs new extension: last I checked, the Command + \ hotkey doesn't work so well with the 1Password X extension, and philosophically, I think it's more pure to use the old extension, since the new one is just implementing the entire 1Password experience, just like other password managers, inside the website window, below the fold. It's less ideal to me, philosophically, and less of a fun experience. Just my two cents though.

Hey guys, thanks for the followup and additional details.

You wrote that the Chromium based extension doesn't support autofill - what does that mean exactly? All the extension can do is save logins and autofill on websites. The classic extension can also save login and autofill websites, but it has not been updated or maintained for over two years now.
We do strongly urge everyone to use the new 1Password in the browser regardless of which browser you are using, as it provides a better autofilling experience and is being actively developed and constantly enhanced.
Here's how to utilize it to autofill and save logins: https://support.1password.com/getting-started-browser/

As for adding support for niche browsers - there's a lot more to it than just adding a line of code to support the code signature of that browser. We constantly audit the security of our supported browsers and the teams behind them, that's no simple task. We do not want the desktop app to establish a secure connection with any browser - that'll put your data in jeopardy, and this is not the first time we deny features that users want, so that we can maintain the highest security standards.

I completely understand where you're coming from, and will forward this request to the team, but I don't want to get anyone's hopes up.
Thanks again for the feedback here, much appreciated :)

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

@ag_yaron I'd like to throw my support in, but also add: I'm one of the most vocal supporters of 1Password, and not only that, but I'm a champion of 1Password for Business at my company. The 1Password Chromium extension doesn't support autofill, in my experience, on Orion. However, the desktop "classic" extension could "just work" if only 1Password provided support for it, or allowed users who are competent to bypass the signing check.

It's frustrating to be an ardent supporter of 1Password, and also to be told that because it's a niche browser, it can't be done. All that does is continue the existing browser monopoly: either you're Firefox, Chrome, or Safari, or you're a Sufficiently Big Company that you can launch a Chromium derived browser and get support because you can cheat (Edge). Any actual upcoming competitor browsers get stymied by default. How is a browser supposed to be non-niche when a popular password manager is refusing to support it, out of philosophical grounds?

How do I vote with my wallet here? Is $99 a month enough to compensate the developer who has to update the signing checks for the 1Password desktop extension? Can browser manufacturers pay this fee? Surely there's a good solution here.

I would appreciate this as well. Orion seems to be a potentially great alternate to Safari (especially after MacOS 12 and iOS/iPadOS 15 UI changes). The developers of Orion note that they've done everything they can on their end to be compatible with the classic 1Password extension. Like cmer noted, it already works, 1Password just needs to trust the browser signature for autofill to work. So hopefully a quick thing on your end without any additional work for ongoing support. Would really appreciate this.