For bug 808770, we would like to use NewTabUtils.jsm in Metro Firefox. I think the simplest way to do this is to move it into /toolkit/content. Any objections, comments, alternatives? See also the discussion in similar bug 811548.
Created attachment 712798 [details] [diff] [review] patch
(In reply to Matt Brubeck (:mbrubeck) from comment #0) > Any objections None from me - there's nothing explicitly specific to desktop Firefox in there. Without having thought about it too deeply, I'd say its probably worth looking into whether it should init itself on first use, like what's being done in bug 811548.
(In reply to Blair McBride [:Unfocused] from comment #2) > Without having thought about it too deeply, I'd say its probably worth > looking into whether it should init itself on first use, like what's being > done in bug 811548. NewTabUtils.init adds some telemetry probes, and an expiration filter. We probably want both to happen at startup; otherwise we risk missing some Telemetry and expiring useful thumbnails, for users who don't open the new tab page in time. Should we keep the explicit init() as a reminder of this, or is it enough to just Cu.import() the module at startup and have it init itself?
I think we should generally avoid implicit initialization (i.e. side effects to import()) for JS modules.
Can you move this to toolkit/modules instead? See bug 828116.
Created attachment 714522 [details] [diff] [review] patch v2 (In reply to :Gavin Sharp (use email@example.com for email) from comment #5) > Can you move this to toolkit/modules instead? See bug 828116. Sure! (And thanks, I was wondering how to decide which subdirectory was more appropriate.)