On Thu, Oct 24, 2013 at 2:19 AM, Nikhil Marathe nsm.nik...@gmail.com wrote:
The easiest solution for implementors and authors is to make the
requestPermission() call in a HTML page before spawning a worker or
registering a service worker. Inside the Worker scope we then have two
options:
1)
Agreed with Anne - I don't see the value in exposing a non-functional
requestPermission().
Certainly on Chrome (which only allows invoking requestPermission in the
context of user input to prevent abuse) we would be unlikely to support
requestPermission() from workers, at least unless we decide
On Thursday, October 24, 2013 at 11:05 AM, Anne van Kesteren wrote:
On Thu, Oct 24, 2013 at 2:19 AM, Nikhil Marathe nsm.nik...@gmail.com
(mailto:nsm.nik...@gmail.com) wrote:
The easiest solution for implementors and authors is to make the
requestPermission() call in a HTML page before
On Thu, Oct 24, 2013 at 12:46 PM, Tobie Langel tobie.lan...@gmail.com wrote:
On Thursday, October 24, 2013 at 11:05 AM, Anne van Kesteren wrote:
Given that Notificaiton.permission exists, I'm not sure what the
additional value of Notification.requestPermission() in a worker
context would be.
Hello,
There has been considerable interest in exposing the Notification API on
workers, and especially service workers. The behaviour of
Notification.requestPermission() requires some consensus. The problem of
requestPermission() on workers is that the user agent may not always be in
a position
