Closed Bug 1209627 Opened 4 years ago Closed 4 years ago

Remove cruft for initial landing

Categories

(Firefox :: New Tab Page, defect)

43 Branch
defect
Not set

Tracking

()

RESOLVED FIXED
Iteration:
44.1 - Oct 5

People

(Reporter: oyiptong, Assigned: oyiptong)

References

(Blocks 1 open bug, )

Details

For our initial landing, we want to keep tile decisioning in the privileged context.

However, most of the other messages, like pinning, blocking can go away.

This bug is to track the removal of all of our unused messages in the RemoteAboutNewTab module, and many of those changes will also manifest in RemoteNewTabUtils.
An example of work that needs to be done is removing the pinning logic in RemoteNewTabUtils, especially in getLinks.

The messages have already been removed from RemoteAboutNewTab.
Actually, upon closer inspection, we may want to keep pinning.

Here's a list of things we want to remove/keep. We should also remove any related code in RemoteNewTabUtils.jsm

There should be no caching in privileged context if possible.

In RemoteAboutNewTab.jsm:

Removing:
* BlockLink
* UnblockLink
* UndoAll
* IntroShown
* ReportSitesAction
* UpdatePages
* InitializeGrid
* Customize
* SpeculativeConnect

Things we keep:
* ReportSiteClicked
* ReplacePinLink
* PageThumbs
* CaptureBackgroundPageThumbs
* UpdateGrid
* GetInit
Assignee: nobody → oyiptong
Summary: Remove message handling in RemoteAboutNewTab.jsm for initial landing → Remove cruft for initial landing
Also removing an erroneous preload rule
Had to keep InitializeGrid because the current page expects it
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.