Open Bug 1550100 Opened 5 years ago Updated 2 years ago

Slight shuffling of content as snippets load in DS


(Firefox :: New Tab Page, defect, P2)





(Reporter: thecount, Unassigned)


When the page is loading, snippets could load later, which would cause loaded content below it, like stories and topsites, to shift down a bit.

Iteration: --- → 69.1 - May 13 - 26
Priority: -- → P1
No longer blocks: pocket-newtab-68
Assignee: nobody → pdahiya

Hi Scott,
Is this specific to snippet loading on top, will help if you can add some more steps to help replicate this issue. Thanks

Flags: needinfo?(sdowne)

It's not happening right now, because a snippet isn't being shown, not sure why, I dunno how to enable it atm. We should figure out how to enable some sort of dev snippet to test reliably.

But basically the rest of the content "topsites, stories, anything else in the layout" can load before or after the snippet loads.

The snippet now loads at the top of the layout, but below search. This causes content to shuffle down if the layout finishes before the snippet loads.

Flags: needinfo?(sdowne)

Maybe we could know that we will render the below-search-snippet sooner to reserve space to avoid shifting the page? I guess the snippets asrouter code runs slightly later currently

NI Tawanda to help clarify if simple_below_search_snippet is going away from new tab in near future. Syncing up with Kate hinted that snippet below search was planned to be short term.

This will help to decide if its worth doing refactoring to make SNIPPETS_REQUEST sooner to find out if we need to reserve space. This refactoring is not trivial and possible to have some increase in above the fold performance numbers as we will be moving request to find snippets to load earlier on opening new tab.

Flags: needinfo?(tkanhema)
Iteration: 69.1 - May 13 - 26 → 69.2 - May 27 - Jun 9

Punan, my understanding is that we will have the snippet through the end of the year at least so it's probably a good idea to continue support.

Flags: needinfo?(tkanhema)

Options are:

  1. We can either always show a snippet for some layout
  2. or we take slight regression in performance in order to wait for snippet.

Snippet loaded would be considered blocker for performance final paint anyway.

In the common case for most users and for most tabs, I don't think there would be the special below-search snippet shown, so it doesn't seem to make sense to optimize for it nor include it as part of performance measurements.

Pending test results, will make this P1 when we know the plan for under the search bar snippet.

Assignee: pdahiya → nobody
Priority: P1 → P2
No longer blocks: pocket-newtab-69
Iteration: 69.2 - May 27 - Jun 9 → ---
Component: Activity Streams: Newtab → New Tab Page
Priority: P2 → P1
Priority: P1 → P2
No longer blocks: pocket-newtab
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.