Closed Bug 1073817 Opened 12 years ago Closed 10 years ago

[e10s] "Karma Blocker" add-on does not work

Categories

(Firefox :: Extension Compatibility, defect)

Product:
Firefox
Component:
Extension Compatibility
Platform:
x86_64
Windows 8.1
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
e10s + ---

People

(Reporter: nissan4321, Unassigned)

References

(
URL
)

Details

(Keywords: addon-compat)

"Karma Blocker" add-on doesn't doing anything when enabled under e10, i.e. there are no monitoring of requests.
Blocks: e10s-addons
URL: https://addons.mozilla.org/he/firefox...
tracking-e10s: --- → ?
Keywords: addon-compat
Version: unspecified → Trunk
hi Anthony, are you the author of the Karma Blocker add-on? Your add-on seems to be broken with multiprocess Firefox (e10s). If you have any questions about e10s support, just drop by the #e10s IRC channel on irc.mozilla.org. MDN also has a good introduction: https://developer.mozilla.org/en-US/Add-ons/Working_with_multiprocess_Firefox
tracking-e10s: ? → +
Yes, I am.
IRC isn't terribly convenient for me. I've also been distracted working on Greasemonkey before this, with its much larger user base. I'm pretty sure this is all down to a problem I faced there: nsIContentPolicy. It appears to be scoped separately, i.e. the existing component runs in the parent process, and sees none of the network activity/requests happening in the child processes. Is there documentation somewhere on how to make nsIContentPolicy work under e10s?
I don't know if there are any docs available for this specifically, but maybe you could start by looking into what AdBlock Plus does, since it looks like they have solved this problem somehow.
FWIW, there's now an e10s-compatible version of nsIContentPolicy. It's mentioned in this blog post, near the end: https://blog.mozilla.org/addons/2015/03/17/compatibility-for-firefox-38/
Done: https://github.com/arantius/karma-blocker/commit/04fe814b468a025a1e8fa4fa4457b74a568e27df (But I still think bug 580850 should be fixed; it would have been much less painful if I didn't have to try random message manager instantiations until things worked.)
This appears to be working for me, is it still broken for anyone else?
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.