Closed Bug 1662797 Opened 1 year ago Closed 1 year ago

Implement live update for top site remote settings

Categories

(Firefox :: Top Sites, enhancement, P3)

enhancement
Points:
2

Tracking

()

RESOLVED FIXED
82 Branch
Iteration:
82.2 - Sep 7 - Sep 20
Tracking Status
firefox81 --- fixed
firefox82 --- fixed

People

(Reporter: dao, Assigned: dao)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Currently when getting new data from remote settings, we'd update the default top sites after a restart. This is fine for the initial release but eventually we'd like to do live updates on idle. Should be pretty easy to implement.

Assignee: nobody → dao+bmo
Status: NEW → ASSIGNED
Iteration: --- → 82.2 - Sep 7 - Sep 20
Pushed by dgottwald@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/687d93f2217e
Implement live update for top site remote settings. r=mikedeboer

Comment on attachment 9174923 [details]
Bug 1662797 - Implement live update for top site remote settings. r=mikedeboer

Beta/Release Uplift Approval Request

  • User impact if declined: Some users may not restart their browser for days and weeks, and during that time they wouldn't get new default top sites if we updated them from remote settings.
  • Is this code covered by automated tests?: No
  • Has the fix been verified in Nightly?: No
  • Needs manual test from QE?: No
  • If yes, steps to reproduce:
  • List of other uplifts needed: None
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): Simple fix, and the feature is currently disabled by default.
  • String changes made/needed:
Attachment #9174923 - Flags: approval-mozilla-beta?

Comment on attachment 9174923 [details]
Bug 1662797 - Implement live update for top site remote settings. r=mikedeboer

Approved for 81.0b9.

Attachment #9174923 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
Regressions: 1664288
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 82 Branch
You need to log in before you can comment on or make changes to this bug.