I'm sorry for explaining this poorly, but it's not easy to express. Those are two very, very different things you're talking about there. But then you should give the user the option to whitelist the executable. In other words, it is good that you flag a browser you think is not compatible. I don't think it is correct for the 1p7 program to refuse the connection without the user's ability to manually override that. Even if it means the user must manually add permission. If the browser is already Firefox-based or Chrome-based, I don't see why the 1p7 desktop app cannot communicate with it. I can then manually add the extension file and it works (both Waterfox 56.2.14 and 68.0b1). But I can manually navigate to the browser.exe and IDM will attempt to auto-install it. It didn't recognize WaterFox automatically. Like I have another extension Internet Download Manager.
I am having difficulty comprehending the relationship between Waterfox and Firefox versioning, but maybe you have a better understanding of that. It is unlikely that this will be expanded any time soon, but other browsers which maintain close compatibility with recent releases of Chrome and Firefox can run 1Password X. Those are the only ones that the 1Password desktop apps will communicate with. I'd recommend using one of the browsers we support: Sorry I don't have better news for you, and also for the circuitous route to get to this answer, given my relative unfamiliarity with Waterfox. So, long story short, Waterfox isn't a browser we officially support, and unless it is updated to be (and stay) reasonably close to current with its Firefox parent, similar to other derivative browsers, 1Password won't even work there unofficially. We make an effort to at least support the current Firefox ESR release (which is part of the reason that version 60 is supported: it was the ESR version until this summer, when it became 68). And I'm sure we'll need to raise the minimum requirement periodically going forward as well, in order to be able to adopt other new technologies. We're not able to remain backward-compatible indefinitely because then we can't take advantage of improvements and new features in the extension frameworks and browser itself to make 1Password better.
I think the key here is that they're telling you upfront that it's not going to work because the browser is out of date and therefore incompatible. So 1Password X doesn't work there on Windows or macOS. Okay, so, to get us on the same page here, when I manually copy the link to force it to install the extension, then try to sign into it, yes, I'm seeing the same thing you reported above: it isn't able to complete.
Anyway, you should be able to right-click where it says "add to firefox" and open the link in a new tab.Īha.
0 kommentar(er)
