Extension will be outdated in Firefox 57 [version 4.6.9 extension is WebExtension compatible]

Thanks, @binaranomaly. Unfortunately, we are not ready for e10s and it will be some time before we are able to fully embrace it. Per the Mozilla wiki, force-enable is not recommended unless you're specifically testing compatibility with e10s in Firefox. This usually applies to add-on developers and such. In any case, I'm glad you got it sorted out and things are working for you now.

--
Jamie Phelps
Code Wrangler @ AgileBits

@binaranomaly The main stumbling block right now is that there are some APIs we use in 1Password's extension that won't get e10s compatible shims so we will have to use WebExtensions to get e10s compatibility. And the mechanism where the extension connects to 1Password has some limitations on WebExtensions and we'll need to move to a new mechanism in order to move to WebExtensions. It's a rough transition time right now, but we hope to be on the other side in the near future. I can't offer a timeline but it's something I'm actively working toward.

--
Jamie Phelps
Code Wrangler @ AgileBits

@binaranomaly: Likewise, thanks for your patience and willingness to share your experience with us!

@stevefal: Thanks so much for those details! That's helpful. I'm glad to hear it's working for you after updating, but be sure to reach out if you encounter any further trouble! :)

@MagerValp I believe the 1Click bookmarks is the only outstanding item, but I should caution that the way things work right now, this also is the same path used by open and fill from the 1Password main application. As for WebExtensions, we are making some progress, but it requires a new mechanism for its communication, which requires some alignment of resources across our extensions and platform apps teams.

We are slowly making progress on this new mechanism. The good news about it is that Chrome, Opera, and Firefox will all be able to benefit from this work. After that, moving to WebExtensions would be up next. I can't give anything firm on the timeframe because we've been bitten by that in the past, but I can say it's not coming before the new year.

I'm sorry I can't be more definitive about this right now, but please do know it's something we're actively working on and can't wait to get out to all our users in the new year.

--
Jamie Phelps
Code Wrangler @ AgileBits

Thanks for that ground truth, @MagerValp!

I definitely understand your frustration, @binaranomaly. Unfortunately I don't have more to offer at this time than what I mentioned above. I'm really working on it and working with our developers on the Mac and Windows teams to move it forward.

@damo: Likewise, happy new year to you too! I hope your holidays were a finely-crafted mix of excitement and relaxation. hehe

Honestly, I think it's more a matter of AgileBits developers not being prohibited from communicating. We all love you and the rest of our awesome customers, and I think everyone benefits from a dialogue, rather than operating in a vacuum and hoping for the best. ;)

No news at this time, but the reason I'm writing this and not Jamie is that he and the rest of our extension team is hard at work on this (among other things). WebExtentions are definitely exciting. If only it wasn't so much work! But it'll be worth it in the end. Thanks for your encouragement! :chuffed:

Hi @ttim03,

The extension in many ways is separate from the 1Password application. So any changes like this which are internal to the browser should have no impact on using it with the existing applications. They will still converse using the same mode of communication and 1Password specific filling messages. It's why even now 1Password 4 for Mac still uses the same extension as 1Password 6 for Mac and the same is true on Windows. If we need to make a jarring change we will ensure there is still a valid version of the extension available for those that can't run the newer 1Password just like how the ageing 1Password 3 browser extension is still available.

Did that answer your question?

:smile:

An ETA for full support of e10s is not available at the moment. It will require significant changes to the extension and we need to ensure the pieces are in place before we can do so. As noted by MagerValp, if you desire you can force e10s on as long as you don't mind the loss of open and fill (which is behind 1Click bookmarks and why they too are affected). I apologise that I cannot offer anything more concrete yet.

@BitBat We are indeed looking at WebExtensions as a replacement for our current Add-on SDK based add-on. Our contacts at Mozilla have been very helpful in this regard as well. Unfortunately, there are a few items we have to do with the native apps before we can make that switch, so we can't plow ahead just yet. We're making some progress, but it will be a little while before the switch can be released.

Hi @favadi,

I doubt that would help. Compatibility with e10s is a setting that has to be defined at build time. I believe only a version of the extension with open and fill completely removed would have the desired impact. While it does require altering Firefox's settings by hand the Force Enable option is probably the best bet for now.

Thanks, @favadi! Glad it's working for you.

@bl4ke: Nothing new to share within the past two weeks. ;)