Opened 6 years ago

Last modified 5 years ago

#1663 closed defect

First-run page is broken with e10s enabled — at Version 5

Reported by: trev Assignee:
Priority: P1 Milestone:
Module: User-Interface Keywords:
Cc: tschuster, greiner, saroyanm Blocked By:
Blocking: Platform: Firefox
Ready: yes Confidential: no
Tester: Verified working: no
Review URL(s):

http://codereview.adblockplus.org/4875452820750336/
http://codereview.adblockplus.org/6427347985104896/
http://codereview.adblockplus.org/6180766664884224/
http://codereview.adblockplus.org/4731979438227456/
http://codereview.adblockplus.org/6432313504169984/

Description (last modified by trev)

Environment

Firefox 37.0a1 nightly build with e10s enabled (browser.tabs.remote.autostart.1 preference set to true).

How to reproduce

  1. Open chrome://adblockplus/content/ui/firstRun.html in the browser.

Observed behaviour

Links don't work, all "features" are shown as being "on" and clicking the buttons has no effect. The issue is apparently that require() returns undefined - observer notifications aren't a good way to reach the core code any more, it is running in a different process now.

Expected behaviour

Links should work correctly, same as the feature toggles.

Implementation notes

We need to make the first-run page communicate asynchronously with the core code. This means implementing ext.backgroundPage.sendMessage() and ext.onMessage.addListener() for Firefox. At this occasion, it would make sense to create an adblockplusui repository and move the first-run page (including translations) there. The actual messages being exchanged there should be in line with the plans for #1524.

Change History (5)

comment:1 Changed 6 years ago by trev

  • Description modified (diff)

comment:2 Changed 6 years ago by trev

  • Cc greiner added

I guess that asynchronous communication with the core code would the best solution here, along the same lines as what @greiner is implementing for the preferences UI. It shouldn't be too much effort either here.

comment:3 follow-up: Changed 6 years ago by greiner

Since #1524 looks like it could take a while still, we could introduce the messaging interface for the Firefox first-run page first. Some of that code could then be reused for the Platform options page.
Would the idea then be to already move the first-run page into the upcoming adblockplusui repository?

comment:4 in reply to: ↑ 3 Changed 6 years ago by trev

Replying to greiner:

Would the idea then be to already move the first-run page into the upcoming adblockplusui repository?

I think that will make most sense.

Note that #1524 isn't about Firefox anyway, so the first-run page will definitely become the test balloon here.

comment:5 Changed 6 years ago by trev

  • Description modified (diff)
Note: See TracTickets for help on using tickets.