The Notification specification defines a static Notification.permission
accessor, which returns one of {granted, denied, default}. This requires
the browser to synchronously determine whether the page has permission to
show notifications, whereas checking this may be an asynchronous operation.
This
I thought I had replied to this. Seems I did not.
On Tue, Apr 29, 2014 at 7:24 PM, Peter Beverloo wrote:
> The Notification specification defines a static Notification.permission
> accessor, which returns one of {granted, denied, default}. This requires
> the browser to synchronously determine wh
Just out of curiosity, what are we hoping that the use counter will show?
I'm presuming that every single app that uses the notification API will
make at least some use of Notification.permission, so it mostly seems like
it's going to show us how often the Notification APIs *in general* are used
in
On Tue, May 13, 2014 at 1:59 PM, Andrew Wilson wrote:
> Just out of curiosity, what are we hoping that the use counter will show?
> I'm presuming that every single app that uses the notification API will make
> at least some use of Notification.permission, so it mostly seems like it's
> going to s
