See https://bugzilla.mozilla.org/show_bug.cgi?id=1008768#c88.

Maybe the first thing here is to check whether we actually need to use the shims for this module. You can do that by setting extensions.interposition.enabled to false in about:config and then testing an extension that uses hotkeys in e10s.

(In reply to Bill McCloskey (:billm) from comment #1) > Maybe the first thing here is to check whether we actually need to use the > shims for this module. You can do that by setting > extensions.interposition.enabled to false in about:config and then testing > an extension that uses hotkeys in e10s. What does the extensions.interposition.enabled do?

It turns off the shims globally. So if the hotkeys code still works when extensions.interposition.enabled is false, then we know that the shims aren't needed for hotkeys to work. The shims can also be disabled for a particular add-on by setting multiprocessCompatible to true in the install manifest: https://developer.mozilla.org/en-US/Add-ons/Install_Manifests That would be another way to go.

LastPass causes the slow/halting of filling in text. I added this to LP's install.rdf: <em:multiprocessCompatible>true</em:multiprocessCompatible> It worked the first time I filled in some text but after that the problem appeared. Is the parameter correct? Did I add it in the right place? Thanks.

LastPass slow text fill in has been fixed by the latest dev e10s build.

I've just tested this while I was looking for an SDK module that uses shims. This module seemed to work just fine with extensions.interposition.enabled set to false, so I'm closing this for now.

Well, the bug here is to stop the module from using shims even if the add-on has shims enabled. So sort of bug 1167802 I guess.

hi gabor, is this still on your radar?

This should be fixed by bug 1196975.