Peter and I discussed these requirements last week in London and believe this would likely be a good project for the London team.

I understand he is planning on putting together a document proposing the pieces we believe we would need there for the purposes of sharing with Mozilla, Edge etc to start building consensus, so assigning to Peter.

(Added ServiceWorker folks FYI)

In terms of use cases,   Issue 676036  is related.

FYI, I'm working on a proposal to pause (or heavily throttle) background tabs, but to give developer opt-out. That way we can get the benefit for 90+% of content now and drive down rest over time by given them the APIs they need. I think we'd still plan to eventually get rid of the opt-out entirely, but it will likely be a 2-4 year effort (assuming we start working on the replacement APIs now).

Please consider throttling--but not shutting off--tabs which have been
permitted to display notifications.  Then the app can use a range of techniques
(to wit, long polling), many of which are highly desirable or even mandatory
on private or heavily firewalled networks.  The user's more or less blessing
a background aspect to the page, and users don't seem to grant notifications to
random pages.

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