I've used 1Password on the Mac for years. I also use BrowserFairy in order to control which browser opens any particular URL.
When I originally installed BrowserFairy, any time I opened a URL from within 1Password then BrowserFairy would pop up. I'd choose the browser, and off I'd go. There would be no delay from BrowserFairy and only the appropriate browser selection popup would appear.
I'm not sure if this changed recently (a few months ago?), but I now notice that BrowserFairy is launched first, then approximately one second later, the URL is opened. This causes a difference in behavior of BrowserFairy in that the launch opens BrowserFairy to show its settings panel, then the subsequent URL open causes the browser selection popup to appear. This extra window and delay is aggravating.
After poking about in the console log, I believe I see what is happening.
Prior to this change, I suspect 1Password simply opened the URL (eg. NSWorkspace.shared.open). This is exactly the expected behavior from any application opening a URL.
After this change, it appears from the console log (eg. "Waiting for Browser Fairy to finishing launching") that 1Password now determines the default browser, launches it, waits 2-3 seconds, and then finally opens the URL. This is not SOP for opening URLs in MacOS. I can only imagine that this extra step and delay were added because some browser didn't properly respond to the open URL if the browser wasn't already running and this was 1Password's attempt at a solution.
First, I'd like to confirm this is what is actually happening.
Second, I'd like to request that 1Password revert to the standard open URL without the extra steps. This extra launch and delay is unnecessary and aggravating.
I verified that there has been no change in BrowserFairy over this time period nor have I made any significant OS updates (just minor patches). I also verified the opening a URL from any other source does not cause the extra launch and delay, so this issue is specific to 1Password. Other applications open URLs using the expected and standard mechanism. Why can't 1Password?
(BTW, I am an experienced software dev so I completely understand having to "hack" solutions to fix problems with 3rd party products, but I'd say this hack causes some additional problems.)
1Password Version: 7.1.2
Extension Version: 4.7.3
OS Version: 10.13.6
Sync Type: iCloud