Migrate SnippetsLauncher from GcmNetworkManager to BackgroundTaskScheduler |
||||||
Issue descriptionIn order to make code consistent across all components scheduling in the background, please migrate the SnippetsLauncher to BackgroundTaskScheduler. Good examples are already available in offline pages and prefetch. Bonus points: Snippets Launcher will also work on O after doing so.
,
Sep 20 2017
Thanks Filip. Are you suggesting it does not work on O right now?
,
Sep 20 2017
I am suggesting that at the time the component was created it was not working and there were chances it won't. It works now, based on what Tommy says. I still encourage moving things to BackgroundTaskScheduler, so that we can minimize the custom code.
,
Sep 21 2017
,
Sep 21 2017
Aha ok. Jan, would you be the correct owner for this one?
,
Sep 25 2017
Yes, I am the correct owner. We are currently running experiments on Stable to determine whether we remove SnippetsLauncher completely or whether we need to keep it and migrate it to BackgroundTaskScheduler.
,
Nov 28 2017
Snippets Launcher should get removed in later stages of project Jardin (sometime in 2018). If not, this should definitely get fixed. Filip / Tim, feel free to re-prioritize.
,
Nov 28
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 28
Assigning to self in the light of current GNM developments. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by fgor...@chromium.org
, Sep 19 2017