Closed Bug 1183206 Opened 5 years ago Closed 4 years ago
Make about:newtab independent of Firefox
42.3 - Aug 10
This includes (but isn't limited to) the following: 1) Removing #ifdef or other pre-processor directives 2) Using window.postMessage instead of RemotePageManager for message passing. 3) Add message passing or find alternatives for Firefox-specific APIs used such as Services.jsm
Newtab code that will be hosted can be found here: https://github.com/emtwo/remote-newtab
There's a lot of e10s work (i.e. bug 1021654) going on with about:newtab, you folks should coordinate.
(In reply to Tim Taubert [:ttaubert] from comment #4) > There's a lot of e10s work (i.e. bug 1021654) going on with about:newtab, > you folks should coordinate. We are co-ordinating with Ursula and Mike who are currently involved in bug 1021654 and I'm personally following that bug closely. Everything in this bug is being built on top of bug 1021654.
Depends on: 1021654
(In reply to Marina Samuel [:emtwo] from comment #5) > We are co-ordinating with Ursula and Mike who are currently involved in bug > 1021654 and I'm personally following that bug closely. > > Everything in this bug is being built on top of bug 1021654. That's great to hear, sorry for assuming otherwise. Didn't see a lot of e10s folks CC'ed here :)
Let's include converting to promise messages and re-organizing js files as part of this bug. We agreed on 3 subdirs of js: ./js/page (UI) ./js/backend (Service worker) ./js/lib (external libraries, tools, helper functions)
This bug is resolved with the following commits: https://github.com/mozilla/newtab-dev/commit/c8c6a496742e2a31c917a47b35e449a7fbbf7b9 https://github.com/mozilla/remote-newtab/compare/9ecf0d7...019cb8aa
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
typo in second commit, should be: https://github.com/mozilla/remote-newtab/compare/9ecf0d7...019cb8a
You need to log in before you can comment on or make changes to this bug.