Issue 889077 talks about introducing a generic scheduled task API (equivalent of chrome.alarms) which allows performing arbitrary work at some point in the future. A useful subset that dodges some of the permission issues is a notification-specific API that always shows a notification. Sharing the same internal doc for now, but will probably fork it: https://docs.google.com/document/d/1XVkYiMjj6NTGvVm76pWiNIWVGEVIhGg7FMUUiF0sS3I/edit?ts=5baa7202
Looking forward to this! (Asked for here: https://groups.google.com/a/chromium.org/forum/#!topic/chromium-discuss/tW3avK3gfl0)
Any estimate for when work will start here?
We have an API sketch and prototype, so hopefully the first CLs will start landing next week :)
Will you share the API sketch Peter?
Of course, we'll publish an explainer and share it here.
Intent to implement went out yesterday: https://groups.google.com/a/chromium.org/d/msg/blink-dev/sFb2H2pwEug/rKue2Dy_DwAJ Together with the explainer (with an API sketch): https://github.com/beverloo/notification-triggers And the draft of the design doc: https://docs.google.com/document/d/1GtsjRwnY8y0bapsVsRaPxYAcszNb0hMNWzfw3eeZYto/edit
Sign in to add a comment