- From: Philip Jägenstedt <notifications@github.com>
- Date: Mon, 17 Apr 2017 22:15:50 -0700
- To: w3ctag/spec-reviews <spec-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 18 April 2017 05:16:23 UTC
On the [Intent to Ship: The Budget API’s reserve() method ](https://groups.google.com/a/chromium.org/d/msg/blink-dev/yBtmc-4xl_o/GE0vneAVDQAJ) on blink-dev I said that "By shipping `navigator.budget.reserve("silent-push")`, we are anticipating that we will eventually want to ship `navigator.budget.reserve("something-else")` and `navigator.budget.somethingElse()`, or the shape of the API would be different." So, while `reserve()` is the bit of immediate interest, I believe the bit that is most in need of pondering is the dependency on https://wicg.github.io/budget-api/#user-engagement, and the implication that all background tasks would drawn from this shared budget. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/spec-reviews/issues/169#issuecomment-294682915
Received on Tuesday, 18 April 2017 05:16:23 UTC