Closed Bug 1067615 Opened 10 years ago Closed 8 years ago

[e10s] "KeeFox" binary add-on isn't compatible with e10s

Categories

(Firefox :: Extension Compatibility, defect)

x86_64
Windows 8.1
defect
Not set
normal

Tracking

()

RESOLVED FIXED
Tracking Status
e10s + ---
firefox36 --- fixed

People

(Reporter: lagu, Unassigned)

References

Details

(Keywords: addon-compat)

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0
Build ID: 20140915030204

Steps to reproduce:

Keefox in generell is running.
The Database connect works.
The pre-filling on an webpage doesn't works here.
The selection in the keefox menu in the nav-bar doesn't open the selected site.



Expected results:

Keefox should pre-fill the pages with entries in the database like it does it without e10s.
The selection in the Keefox-Menu in the nav-bar should open the page again.
Blocks: e10s-addons
Component: Untriaged → Extension Compatibility
Version: 35 Branch → Trunk
Here is a link to the KeeFox add-on:

https://addons.mozilla.org/en-US/firefox/addon/keefox/

Note that this is a binary add-on that installs "KeePass Password Safe 2" on your computer, which requires the Microsoft .NET framework.
tracking-e10s: --- → +
Keywords: addon-compat
Summary: [e10s] keefox isn't full compatible → [e10s] "KeeFox" binary add-on isn't compatible with e10s
I testet Keefox Version 1.4.4b2 and it is working with e10s.
https://addons.mozilla.org/en-US/firefox/addon/keefox/versions/?page=1#version-1.4.4b2
Awesome. Thanks for testing, Lars!
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Keefox is not running with E10S here.

No auto fill, no star in keefox icon if a entry for a page should be available. 
No page in the icon menu if you click to the icon.

And tis error in console:
TypeError: doc.defaultView.QueryInterface(...).getInterface(...).QueryInterface(...).rootTreeItem is null KFILM_Fill.js:198:21
Which version are you using?
Flags: needinfo?(micha.postbox)
Keefox 1.4.4B2 & actual nightly.
Flags: needinfo?(micha.postbox)
There's a newer 1.4.4 version on AMO. Please try with that one and report back if you still see problems.
Still same problem with 1.4.4. Setup also a new profile with KF standalone.

Found a second failure in console:
TypeError: win.content is null KF.js:1186:12
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: WORKSFORME → ---
The developer has been contacted through AMO.
Thanks for making me aware of this problem.

I've been trying to understand e10s and what it means for KeeFox for a while now but have no idea how to fix individual error messages without making large scale changes to the addon's architecture. So I'll start looking into the latter soon and perhaps come across some quick wins that will allow me to make some targeted changes to enable e10s support despite the incompatible architecture. Unfortunately, I have very little spare time at the moment so a full re-architecture is likely to take many months.

In the mean time, we can hope that some of Mozilla's work on improved add-on shims will make all the problems magically go away!
How is it working now?
Flags: needinfo?(luckyrat)
The development channel version on AMO works with e10s now. Unless anything major breaks during the next few weeks of beta testing I expect to be submitting it for full AMO review in about a month, so assuming current AMO queue review times remain unchanged end users should get a stable release by December.
Flags: needinfo?(luckyrat)
The e10s compatible version has been on the stable/release AMO channel for a couple of months now and I've not heard of any issues relating to e10s so I think we can safely say this is fixed.
I test E10s only from time to time, but it seems all to work with the actual version.
Given the above.
Status: REOPENED → RESOLVED
Closed: 10 years ago8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.