But if MostVisitedSites becomes a KeyedService, then it's fine for PopularSites to stay as it is (and be owned by MVS). No need to make another KeyedService that'll be used in only a single place.

Not time critical

Adjusting priority as this is now marked as a blocker for the M57 full launch of popular sites on iOS

Let me know if you'd like me to do progress on https://codereview.chromium.org/2619993002/

sfiera@: could you give a quick status update? thx!

Gentle ping for sfiera@.

More specifically, fhorschig@ and I had the impression that Chrome Home is already using Popular Sites (indirectly) as a long-lived object. Is that an issue? If not, should we close this bug?

The future state of this on various platforms is:
 * Android: long-lived via Chrome Home (I believe)
 * iOS: short-lived, per NTP
 * Desktop: long-lived via local NTP

#7 says "marked as a blocker for the M57 full launch of popular sites on iOS" but clearly it wasn't, since we launched and it's still not fixed there.

Desktop: long-lived via InstantService. That's independent of local/remote NTP. (It's not yet fully launched though - going out with M60.)

Any objection to closing the bug?

Dropping priority and obsolete target milestone based on comment #13.

With Chrome Home and Local NTP on hold, this is back to square one. Not clear how desired it is anymore.