Closed Bug 1535749 Opened 5 years ago Closed 5 years ago

Load new tab pocket article images closer to when they might be shown


(Firefox :: New Tab Page, enhancement, P1)




68.2 - Apr 1 - 14


(Reporter: gsuntop, Assigned: gsuntop)



Don't load assets that are outside of the immediate viewport until scroll position gets within a certain threshold TBD.

Severity: normal → enhancement
No longer blocks: 1512725
See Also: → 1535693 and together could implement this.

I'm not sure that it's worth taking more dependencies for this (though it's not necessarily out of the question), but even if not, they may be helpful as inspirations.

Also worth noting is that it looks like at least some of react-image functionality will be provided via React itself mid-2019:

Summary: Add lazy loading → Add lazy loading for images
Iteration: 68.1 - Mar 18 - 31 → 68.2 - Apr 1 - 14

Has anyone thought about the privacy implications of this yet, especially for e.g. 3rd party content? Or the negative economic impact for webmasters in the case of ads (e.g. being marked as a non-load while the page was loaded). I mean, it's cool if you can save a few KB of bandwidth, but I see plenty of potential abuse here too.

Heads up, users and press are mistaking this bug as being related to Chrome's proposed <img loading="lazy" /> attribute.

I've reached out to the ZDNet author to clarify that this bug is about using normal front-end development techniques to speed up Firefox's new tab page.

Summary: Add lazy loading for images → Load new tab pocket article images closer to when they might be shown

Mark, would you mind unpacking your comment a bit? I'd like to be sure we completely understand your concerns.


Flags: needinfo?(mark)

Gavin, since this bug has been transformed into something I did not think it was about (which would indeed be the loading="lazy" attribute, for lazy-loading images and iframes) I'm not sure if my concerns apply here. This bug was brought up on our forum in tandem with:

which, as I understand it now, is incorrect.

My main concerns with this are:

  • The more detailed signals to web servers, allowing more detailed tracking of user interaction with the page without JavaScript (has the user scrolled down? if so: how far? etc.)
  • Lack of actual loading of monetization elements if they aren't in view. Many ad services use impressions as a main statistic to pay revenue. This will be severely cut if lazy loading prevents server hits. I don't think that's healthy for the already damaged display ad industry and will push website owners to more intrusive methods of advertising.

As said I'm not sure to what extent this applies to your sponsored content on your new tab page, but even if using normal front-end methods I'd gather similar concerns should be kept in mind.

Flags: needinfo?(mark)
Closed: 5 years ago
Resolution: --- → DUPLICATE
Component: Activity Streams: Newtab → New Tab Page
You need to log in before you can comment on or make changes to this bug.