[e10s] Check4Change addon always shows tab titles as "loading..." when e10s is enabled

RESOLVED INCOMPLETE

Status

()

RESOLVED INCOMPLETE
4 years ago
10 months ago

People

(Reporter: catlee, Unassigned, NeedInfo)

Tracking

({addon-compat})

Trunk
x86_64
Linux
addon-compat
Points:
---

Firefox Tracking Flags

(e10s+, firefox34 affected)

Details

(Whiteboard: triaged)

(Reporter)

Description

4 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.
https://addons.mozilla.org/en-US/firefox/addon/check4change
Blocks: 905436
No longer blocks: 516752
tracking-e10s: --- → +
Component: General → Extension Compatibility
Summary: [e10s] Check4Change addon always shows tab as "loading..." → [e10s] Check4Change addon always shows tab titles as "loading..."
status-firefox34: --- → affected
Summary: [e10s] Check4Change addon always shows tab titles as "loading..." → [e10s] Check4Change addon always shows tab titles as "loading..." when e10s is enabled
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
Keywords: addon-compat
The developer has been contacted through AMO.

Comment 4

3 years ago
This is still broken, re-notified through AMO.

Comment 5

3 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?

Comment 6

3 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

Comment 7

3 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.
Flags: needinfo?(ronen.zilberman)

Comment 8

2 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.

Comment 9

2 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.
Whiteboard: triaged
With Firefox 57 only WebExtensions are permitted and are, by default, e10s compatible.
Status: NEW → RESOLVED
Last Resolved: 10 months ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.