Chris AtLee [:catlee] Reporter
	Description • 10 years ago

The Check4Change addon is really handy to automatically check if there are content changes on a tab.

With e10s, one of the things that's broken in this addon is that the tab's title is always set to "loading...". Normally the title would have a countdown timer indicating how long until the next check.

The addon does seem to be reloading the tabs at the correct interval. I'm not sure if it's actually detecting changes properly though.

	Chris Peterson [:cpeterson]
	Comment 1 • 10 years ago

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

	Chris Peterson [:cpeterson]
	Comment 2 • 10 years ago

hi Ronen, if you have any questions about e10s support for multiprocess Firefox, 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

	Jorge Villalobos [:jorgev] (he/him)
	Comment 3 • 10 years ago

The developer has been contacted through AMO.

	Jerod Lycett
	Comment 4 • 9 years ago

This is still broken, re-notified through AMO.

	Ronen Zilberman
	Comment 5 • 9 years ago

Hi,
Thanks for reaching out and sorry for the long delay in responding.

This seems like a lot of work that I won't be able to do at the moment. When is e10s compatibility planned to be a requirement?

	Jerod Lycett
	Comment 6 • 9 years ago

(In reply to Ronen Zilberman from comment #5)
> Hi,
> Thanks for reaching out and sorry for the long delay in responding.
> 
> This seems like a lot of work that I won't be able to do at the moment. When
> is e10s compatibility planned to be a requirement?

You can find a schedule at https://wiki.mozilla.org/Electrolysis#Schedule

	Jerod Lycett
	Comment 7 • 9 years ago

(In reply to Ronen Zilberman from comment #5)
> Hi,
> Thanks for reaching out and sorry for the long delay in responding.
> 
> This seems like a lot of work that I won't be able to do at the moment. When
> is e10s compatibility planned to be a requirement?

Hi, just wondering if you were able to find time to do any work. e10s enters A/B testing in Beta Monday.

	:shell escalante
	Comment 8 • 8 years ago

Hi Ronen - we've got a timeline, now that e10s has started going out in Fx48 (excluding add-ons).  We are adding in add-on populations slowly over releases, to measure the impact so we maintain quality.

https://docs.google.com/spreadsheets/d/1OFYrrvAFg8y1mZOEbuIR1axxtV8eul_be6ad9fe8JB0/edit#gid=1952061950

so you can safely go until Jan 23rd (51 release), possible 52 or 53... and the benefit there is webextensions will continue to be developed aggressively - so more will be available that might meet your needs.  Past 51 (likely 52 may or 53 June) we will consider only allowing e10s compatible only.

Until then if a user had a non-e10s friendly add-on installed, they are just selectively excluded from getting e10s activated.

but we are fully on track and engaged that e10s is coming in the next couple of releases.

	:shell escalante
	Comment 9 • 8 years ago

Hi Ronen - we've got a timeline, now that e10s has started going out in Fx48 (excluding add-ons).  We are adding in add-on populations slowly over releases, to measure the impact so we maintain quality.

https://docs.google.com/spreadsheets/d/1OFYrrvAFg8y1mZOEbuIR1axxtV8eul_be6ad9fe8JB0/edit#gid=1952061950

so you can safely go until Jan 23rd (51 release), possible 52 or 53... and the benefit there is webextensions will continue to be developed aggressively - so more will be available that might meet your needs.  Past 51 (likely 52 may or 53 June) we will consider only allowing e10s compatible only.

Until then if a user had a non-e10s friendly add-on installed, they are just selectively excluded from getting e10s activated.

but we are fully on track and engaged that e10s is coming in the next couple of releases.

	Firefox Bug Husbandry Bot
	Comment 10 • 7 years ago

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