Closed Bug 1287659 Opened 7 years ago Closed 5 years ago

[e10s] from certain webNavigation listeners is too early to have an effect


(WebExtensions :: Untriaged, defect, P3)



(e10s+, firefox50 affected)

Tracking Status
e10s + ---
firefox50 --- affected


(Reporter: robwu, Unassigned)



(Whiteboard: triaged)

1. Enable e10s.
2. Visit
3. Load at about:debugging (from
4. Refresh

Expected (without e10s):
- The page action should be shown.

Actual (with e10s):
- The page action does not show up.

Extra info:
- This seems like a race condition / timing issue. When I open the browser toolbox and put a breakpoint at [1] before step 4, then the page action is shown when I resume execution.

Summary: [e10s] does not show buttons in tabs that existed prior the installation of the addon → [e10s] from certain webNavigation listeners is too early to have an effect
This issue has a connection to what I described in Bug 1287649:

the pageAction API clears the pageAction on every location change, the webNavigation.onCommitted event happens before the location change,
and so the pageAction API implementation hides the pageAction after that the callback registered to webNavigation.onCommitted calls

(And by setting a breakpoint in the callback registered to the webNavigation API events, as a side-effect we are executing after the pageAction API has already reacted to the location change)
Priority: -- → P3
Whiteboard: triaged
With Firefox 57 only WebExtensions are permitted and are, by default, e10s compatible.
Closed: 5 years ago
Resolution: --- → INCOMPLETE
Product: Toolkit → WebExtensions
You need to log in before you can comment on or make changes to this bug.