1108491 - IPvFox add-on does not work with e10s

Status: RESOLVED INCOMPLETE

(Firefox :: Extension Compatibility, defect)

Description

[Gian-Carlo Pascutto [:gcp]]

Always shows just a question mark instead of resource addresses.

https://github.com/Dagger0/IPvFox
https://addons.mozilla.org/en-US/firefox/addon/ipvfox

Comment 1

[Chris Peterson [:cpeterson]]

Dagger, are you the developer of the "IPvFox" add-on? The 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 or ask Ally on this bug. MDN also has a good introduction:

https://developer.mozilla.org/en-US/Add-ons/Working_with_multiprocess_Firefox

Comment 2

[dagger.bugzilla]

Yes, I am. I was hoping it'd be fixed by shims (e.g. bug 1108827). If not, then I'd like to fix it, but a) I'd need to deal with Australis, b) e10s doesn't work for me. So it's gonna be tricky.

Comment 3

[Jerod Lycett]

This still does not appear to be fixed, is there any way we can assist?

Comment 4

[dagger.bugzilla]

I guess my main blocker is now bug 1098008 that prevents me from using e10s long enough to even get started (since e10s relies on OMTC, but I'm not turning OMTC on due to graphical glitches). There's also been no activity on bug 1108827, although there's no guarantee that'll magically fix everything.

Also it would help if you don't deprecate chrome access in extensions, so that I actually have /some/ motivation left.

Comment 5

[Jerod Lycett]

(In reply to dagger.bugzilla from comment #4)
> I guess my main blocker is now bug 1098008 that prevents me from using e10s
> long enough to even get started (since e10s relies on OMTC, but I'm not
> turning OMTC on due to graphical glitches). There's also been no activity on
> bug 1108827, although there's no guarantee that'll magically fix everything.
> 
> Also it would help if you don't deprecate chrome access in extensions, so
> that I actually have /some/ motivation left.

I'm assuming you're referring to the deprecation of XUL based addons? If so then know that the blog where they announced that specified it'd be in 12-18 months, which as you can see with the signing thing, and the fact that e10s was supposed to have been released by now when first announced, is a rather conservative guess.

I'm pinging jorgev to see if he can help get some movement on that bug so you can try to fix this.

There are also plenty of helpful devs around at https://discourse.mozilla-community.org/c/add-ons and #extdev on irc.mozilla.org that may be able to find you a work-around without using e10s yourself. I'm always willing to help test.

Comment 6

[Jorge Villalobos [:jorgev] (he/him)]

Looks like it's being looked at.

Comment 7

[dagger.bugzilla]

It's not just XUL-based addons; even Javascript-based addons won't have access to chrome -- which might possibly be something IPvFox can get away without, but most of my other extensions can't. 

(And it's not really the exact timeframe that's the problem, but the fact that it's happening at all.)

Comment 8

[Firefox Bug Husbandry Bot]

With Firefox 57 only WebExtensions are permitted and are, by default, e10s compatible.