Support for Orion Browser

@ag_ana Any update on this? As others have noted, it seems Orion just needs to be on 1Password's whitelist… Thank you!

@reykjalin:

@ag_yaron and @ag_ana please ask your devs to take a closer look

Will do! :+1:

I just want to second this request and note that @hakusaro's experience here is the same one I've had, namely:

1. The 1Password X extension can't autofill on any websites; and
2. The 1Password X extension can sometimes take a really long time to load (1-3 mintues).

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.

@ag_yaron This is not correct. Orion runs a custom build of WebKit that includes support for the WebExtension API. To quote https://browser.kagi.com/faq.html:

And extensions! Unlike Safari, Orion has native support for both Chrome and Firefox extensions. This gives our users access to the largest extensions ecosystem in the world. With Orion, you can one-click install your favorite extensions directly from the web.
[...]
How does Orion support extensions?
Early in development, we decided to natively support the Web Extensions API, the same API that Chrome and Firefox use to make their extension ecosystems so powerful. We had to port in hundreds of APIs, one by one, that were never meant to work with WebKit. Took us a few years, but here we are!

Orion currently supports about 70% of Web Extensions APIs, and we add more every day. On top of that, we built advanced security features that give our users granular control beyond what Chrome and Firefox offer. For example, you can choose to allow an extension to run only on certain websites.

As such Orion should be able to support the 1Password X extension, but the extension doesn't work as it's supposed to. From what anyone has been able to gather the problem does not seem to be with Orion's implementation of the WebExtension API, but instead https://1password.community/discussion/comment/615192/#Comment_615192.

It'd be great if you could have your devs look into why the extension doesn't work as intended.

To recap

1. The 1Password browser extensions don't work in https://browser.kagi.com.
2. The WebExtension APIs are supported in Orion — the same APIs used by Firefox and Chrome to run browser extensions.
3. The problem seems to be with the 1Password extensions, not lack of support for the APIs used by the 1Password browser extensions.

@ag_yaron and @ag_ana please ask your devs to take a closer look. Based on what everyone has seen adding support for Orion in an updated version of the browser extensions should not be a complicated matter. If that's not the case, please let us (or better yet the Orion team) know what has to be improved so 1Password can support Orion.

Just wanted to add my +1 hoping Orion support is added. The browser looks quite promising, but lack of functional 1Password makes it very hard to consider switching.

Would love to see 1password working properly with Orion Browser!

Not yet @anquieta, sorry!

Really appreciate it @ag_yaron. Wondering if there's an update on this.

Hey guys,

Some of our devs (and security team) are looking into this. Thank you for the additional details and feedback.

Sometimes it's hard to believe there's a new browser to "rule em all". But this what is happening with Orion right now, the lightweight Safari became even lighter. Just try it for one day in your daily routine and check Activity Monitor to see its magic inside.
It's like it's never going to pass above 20% of cpu (depends on your hardware too though).. but while Safari has 100-150% with simple tasks, the same on Orion is only 10%.. and it's still on 0.99 alpha release.

1Password is one of the apps we "call" many times per day. With Orion I am back on using the mouse in my Mac :) Cause I need to have a shortcut like cmd \ that opens the 1password (mini) window and I search and drag n drop the credentials on my Orion browser for any site. I keep the ones that I want (and use) daily in Orion keychain BUT this is not why I am paying 1Password for.

I know it's not a browser that everyone knows. I know it's hard to develop that small detail into the old extension and make it compatible, but saving my passwords outside of 1Password, it's just doesn't feel right.

Maybe someone can push an alpha version for the "many" of us (https://daringfireball.net/2021/10/the_tragedy_of_safari_15_quote_unquote_tabs), that don't like the new Safari, and hate chrome and the Firefox memory hungry browsers?

I am using these ones for now:
https://addons.mozilla.org/en-US/firefox/addon/1password-x-password-manager/
https://chrome.google.com/webstore/detail/1password-%E2%80%93-password-mana/aeblfdkhhhdcdjpifhhbdiojplfjncoa

and I've tried beta as well, what is this for anyway?
https://chrome.google.com/webstore/detail/1password-beta-%E2%80%93-password/khgocmkkpikpnmmkgmdnfckapcdkgfaf?hl=en

Thanks in advance!

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.

It's a custom build of WebKit. It would be technically incorrect to call it a WebView. By that same logic, Edge and Opera are just Chromium WebViews. Given that it's just WebKit with a lot of APIs that don't exist in Safari by default, again, it seems trivial to support, and the decision is arbitrary.

While it's interesting to speculate on whether or not the classic extension would or wouldn't work, the simplest thing would be to build the extension, permit the browser, and test it to see if it worked. Same with the modern extension for that matter.

I hope that 1Password reconsiders. Again, philosophically, making arbitrary decisions on which browsers to support significantly harms the already-diminishing open web.