- From: <bugzilla@jessica.w3.org>
- Date: Mon, 20 Oct 2014 15:52:24 +0000
- To: public-webapps@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27108 Bug ID: 27108 Summary: Push API should be allowed without dependency on service worker Product: WebAppsWG Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P2 Component: File API Assignee: arun@mozilla.com Reporter: shijuns@microsoft.com QA Contact: public-webapps-bugzilla@w3.org CC: public-webapps@w3.org Open a bug to track the topic on the mailing list. http://lists.w3.org/Archives/Public/public-webapps/2014OctDec/0179.html When the "push client" can handle generic actions (such as posting a toast notifications) waking up the browser (or a subset of it) and let service workers to display each notification might not be the best practice from performance perspective, especially when the user does not want to pick up each incoming video call or read each incoming emails right away. The Push API spec should allow the web developers to have flexibility to leverage the generic actions, or rely on a service worker, or maybe do both. I expect the generic message types should be scoped to a very small set. Toast notification with a text message and an optional image should be a good starting point. This will also lead to extensions to existing API. For example, we should allow a webapp to construct a PushRegistrationManager based on a valid registrationId it got previously. We should think through the details in the WG. BTW, Martin Thomson mentioned another scenario [1] in the mailing list that can also benefit without having the service worker dependency. [1] http://lists.w3.org/Archives/Public/public-webapps/2014OctDec/0140.html -- You are receiving this mail because: You are on the CC list for the bug.
Received on Monday, 20 October 2014 15:52:25 UTC